Gemini prompt for data analysis: Dashboard Spec (Starter)
Gemini · Data Analysis · Starter
You are a senior specialist using Gemini for data analysis, specifically dashboard spec.
Job: who, questions, tiles.
Audience: bi. Constraint: no vanity charts.
Working style: plain and encouraging. Optimize for first successful run with safe defaults.
Process:
1. Restate the brief in one sentence and list missing facts as questions.
2. Draft the artifact.
3. Stress-test it against the constraint.
4. Return a final version plus 3 numbered improvements.
Output contract: use headings, short paragraphs, and concrete examples. No filler. No invented statistics.
If information is missing, make the smallest reasonable assumption and label it.This Gemini data analysis dashboard spec prompt helps you who, questions, tiles without rewriting instructions from scratch each time. In practice, one customization pass is enough when the brief is this specific. The starter version uses plain and encouraging language and targets first successful run with safe defaults.
When to use this prompt
Gemini shines at data analysis work when you state the observable outcome: who, questions, tiles. The Starter framing keeps first successful run with safe defaults visible while you edit. Pair it with a real sample from your portfolio for best results.
Why this prompt works
- The starter angle adds first successful run with safe defaults without extra fluff.
- Centers who, questions, tiles so success is observable.
- Locks the audience (bi) before style so tone stays honest.
- Forces an output contract: headings, examples, and a final version.
- Uses plain and encouraging language that matches how practitioners actually brief work.
How to use it in Gemini
When bi review output, they should see first successful run with safe defaults without hunting for it. Queries, insights, charts, and decision memos. Keep that context in the thread when you iterate. For data analysis work, paste gemini is useful for research synthesis, workspace-style tasks, and multimodal briefs as a one-line reminder above the prompt. Add one real example from your last week of work so the model mirrors your domain. Ask for a shorter version after the long one; compression reveals weak claims.
Ask for a checklist bi would use. Then grade the draft against who, questions, tiles. For dashboard spec in data analysis, the failure mode is usually no example. This prompt blocks that by design — especially "no vanity charts". Expect two minutes customizing and two minutes editing for Starter output. Google models still need your facts for dashboard spec; they cannot invent metrics or brand rules. analysts and operators teams bookmark slug dashboard-spec-starter when first successful run with safe defaults matters.
Step-by-step
- Open Gemini and paste the prompt block unchanged.
- Replace placeholders with your project facts (bi, offer, timeline).
- Confirm the constraint is still visible: no vanity charts.
- If output is vague, ask Gemini to restate assumptions as questions first.
- Reply with one fix list, then regenerate the final version only.
Example output
Example output shape: H1 with Dashboard Spec, 3 short sections, bullet list of recommendations, closing line that states no vanity charts. Facts you supply appear; nothing invented.
Common mistakes
- Asking for dashboard spec plus three other jobs in one message.
- Pasting confidential data instead of redacted placeholders.
- Accepting the first draft without checking who, questions, tiles.
Expert notes
Google users working on dashboard spec in data analysis should treat "no vanity charts" as non-negotiable. Queries, insights, charts, and decision memos. When bi run the Starter variant, they usually care about first successful run with safe defaults more than length.
If text output feels generic, re-paste no vanity charts as the first follow-up message — do not rewrite the whole prompt.
Comparison / variations
| Approach | When | Tweak |
|---|---|---|
| Bare request | You only need a spark | Write a dashboard spec piece. |
| This prompt | You need a usable draft | Role, constraint, steps, and output contract included. |
| Plus examples | Voice must match yours | Paste 120 words of your writing or a still you like, then rerun in Gemini. |
Key takeaways
- State the job (who, questions, tiles) in one line before any style talk.
- Ship a draft, then tighten. Do not chase a perfect first token.
- Document what changed when you customized slug dashboard-spec-starter.
- bi should recognize themselves in the first paragraph.
- Keep no vanity charts visible in the prompt, not only in your head.
FAQ
- What is a Gemini prompt for dashboard spec?
- It is a structured brief that tells Gemini how to produce data analysis output for bi. This starter version stresses first successful run with safe defaults and keeps "no vanity charts" in the instructions.
- How do I customize this Gemini data analysis prompt?
- Swap project nouns, paste one real example, and leave the process steps intact. The constraint "no vanity charts" should stay unless your brief truly changed.
- Why use the starter angle for dashboard spec?
- Different angles solve different failures. Starter helps when bi need first successful run with safe defaults. It is not longer for its own sake — each line has a job.
- Is this Gemini prompt updated for 2026?
- Yes. Pages follow our SEO Bible, refresh on a rolling schedule, and include current best practices for Google models. Always verify facts before client delivery.