⚡ Promptolis Original · Data & Analytics

📊 Dashboard Design Principles — Build Dashboards People Actually Use

The structured dashboard design covering audience-first layout, the 5-second test, chart type selection, color discipline, the 'single-action' principle, and the 'why don't you look at the dashboard?' problem solution.

⏱️ 3 hours per dashboard design 🤖 ~90 seconds in Claude 🗓️ Updated 2026-04-20

Why this is epic

Most dashboards are decoration — pretty but unused. This Original produces dashboards people actually USE: audience-first design, 5-second test, appropriate chart types, restrained color, single-action clarity.

Names the 5 dashboard failures (too many metrics / wrong audience / bad chart choices / color overload / no action clarity) + fixes.

Produces complete dashboard design principles with specific tool considerations (Looker, Tableau, Grafana, Mode, etc.).

The prompt

Promptolis Original · Copy-ready
<role> You are a data visualization + dashboard design specialist with 12 years of experience. You've designed 500+ dashboards across Tableau, Looker, Grafana, Mode, Metabase. You draw on Edward Tufte, Stephen Few, data visualization research + empirical usage patterns. You are direct. You will name when dashboards try to show too much, when chart types are wrong, when color is chaos, and when dashboard serves the designer's ego, not user's needs. </role> <principles> 1. Audience FIRST. 2. 5-second test. 3. Chart type matches data type. 4. Color is semantic + restrained. 5. Single-action clarity. 6. Remove 50% of first draft. 7. Mobile where relevant. 8. Context + annotations. </principles> <input> <dashboard-purpose>{what decisions + actions}</dashboard-purpose> <audience>{who views it + their needs}</audience> <data-available>{key metrics + dimensions}</data-available> <tool>{Looker / Tableau / Grafana / etc}</tool> <cadence>{daily / weekly / real-time}</cadence> <current-dashboard>{if exists, what's wrong}</current-dashboard> <constraints>{data freshness, tool limitations}</constraints> <success-metric>{usage, action taken}</success-metric> </input> <output-format> # Dashboard Design: [Purpose] ## Audience + Purpose Clarity Who + why + what action. ## 5-Second Test Layout What user sees first. ## Metric Selection (Hierarchy) Key metrics + supporting. ## Chart Type Selection Right chart for each metric. ## Color Strategy Semantic + restrained. ## Action-Oriented Design What to do next. ## Drill-Down Structure How users explore deeper. ## Mobile Considerations Responsive design. ## Key Takeaways 5 bullets. </output-format> <auto-intake> If input incomplete: ask for purpose, audience, data, tool, cadence, current, constraints, success metric. </auto-intake> Now, design:
🚀 Open in ChatGPT ✨ Open in Claude 💎 Open in Gemini

Example: input → output

Here's how this prompt actually performs. Real input below, real output from Claude Opus 4.

📝 Input
<dashboard-purpose>Marketing performance dashboard. VP Marketing + CEO view weekly. Help decide: budget allocation across channels, campaign performance, pipeline trends.</dashboard-purpose>
<audience>VP Marketing (daily), CEO (weekly). Both want fast scan, not deep analysis. Analysts look at deeper dashboards separately.</audience>
<data-available>Marketing spend by channel (paid ads, content, events, partnerships, outbound), MQLs + SQLs by source, pipeline generated, CAC, LTV, attribution data.</data-available>
<tool>Looker.</tool>
<cadence>Weekly for VP, weekly+ monthly review for CEO.</cadence>
<current-dashboard>Exists but 'too busy' — 25 charts, unclear priorities, CEO said 'I look at it, but I can't decide anything from it.'</current-dashboard>
<constraints>Data refreshed daily. Looker has good UX but not always mobile-perfect.</constraints>
<success-metric>Weekly budget/campaign decisions made + confidence in data.</success-metric>
🤖 Output

Dashboard Design: Marketing Performance, VP + CEO Audience, Looker

A dashboard design produces audience-calibrated visualization serving decision-making. Your current dashboard (25 charts, unused) is classic 'designer serving self' anti-pattern. This redesign: 5 key metrics + single action focus + 5-second scan-ability.

Audience + Purpose Clarity

Primary audience: VP Marketing (weekly) + CEO (weekly)

Actions they need to take:

1. Approve/adjust channel budget allocation

2. Identify under/over-performing campaigns

3. Confidence in pipeline trajectory

What they DON'T need: deep analytics (analyst team has separate dashboard)

Design principle: every element serves one of those 3 actions. If it doesn't, cut.

5-Second Test Layout

Top row (immediate visibility):

Metric 1: This week vs. last week pipeline
  • Large number (${total})
  • Percent change (+/- vs. last week)
  • Green/red semantic color
  • No chart — just the number
Metric 2: Marketing-sourced ARR (month-to-date)
  • Large number
  • vs. monthly target (%)
  • Progress bar visualization
Metric 3: This month MQL volume
  • Large number
  • vs. target + vs. last month

5-second scan tells user: pipeline healthy? Meeting monthly target? MQLs on track?

Metric Selection (Hierarchy)

Key Metrics (top row — 3 numbers):

1. Pipeline generated this week (vs. target)

2. Marketing-sourced ARR MTD (vs. target)

3. MQLs this month (vs. target + last month)

Secondary Metrics (middle row — 4 charts):

4. Channel performance: bar chart showing spend vs. pipeline generated by channel

  • Identifies under/over-performing channels at a glance
  • Sort by pipeline:spend ratio (efficiency)

5. Campaign performance: top 5 + bottom 5 campaigns by MQL/$

  • Action-oriented: scale top, pause bottom

6. Pipeline trend: 12-week line chart

  • Shows trajectory — growing, flat, declining
  • Annotations for major events (campaign launches, seasonality)

7. CAC trend: 12-week line chart

  • Unit economics health
  • Annotated with meaningful events
Removed from current (of 25 charts):
  • Daily granularity charts (weekly/monthly appropriate for VP/CEO)
  • Tactical channel deep-dives (analysts' dashboard)
  • Historical quarterly trends (separate strategic dashboard)
  • Lead lifecycle funnel (operational, not strategic)

Result: 7 elements vs. 25. More usable, more scannable.

Chart Type Selection

Numbers (Metric 1, 2, 3): large big-number display with sparkline for context

Channel performance (Metric 4): horizontal bar chart

  • Width = pipeline generated
  • Color intensity = efficiency (pipeline/spend)
  • Sorted by efficiency

Campaign performance (Metric 5): simple table with colored indicators

  • Row per campaign
  • Columns: Spend, MQLs, MQL/$, Pipeline, Status
  • Green/yellow/red indicator

Pipeline trend (Metric 6): line chart

  • Y-axis: pipeline $
  • X-axis: weekly buckets
  • Annotations for campaign launches, seasonality

CAC trend (Metric 7): line chart

  • Similar to pipeline trend
  • Target line shown as reference

NOT using: pie charts, 3D charts, gauges, treemaps (overused + hard to read).

Color Strategy

Semantic colors only:

  • Green: good / above target / growth
  • Red: bad / below target / decline
  • Blue: neutral / baseline
  • Gray: historical / context

Restrained palette:

  • Max 5 colors total
  • One primary brand color for neutral/baseline
  • Semantic colors for state

NO rainbow. NO every-chart-gets-different-colors. Consistency across dashboard.

Action-Oriented Design

Each element answers: 'what should VP/CEO do from this?'

Metric 1-3 (top row):

  • If green: continue current approach
  • If red: investigate via drill-down or ask team

Channel performance (Metric 4):

  • Clear winners/losers → budget reallocation decisions
  • Action: 'Shift 20% of [channel] to [winning channel]'

Campaign performance (Metric 5):

  • Bottom 5 campaigns → pause + investigate
  • Action: 'Kill underperforming, double-down on winners'

Pipeline + CAC trends (Metric 6-7):

  • Trajectory → strategic discussion
  • Action: escalation if trend negative

Drill-Down Structure

From dashboard summary → analyst dashboards:

  • Click channel bar → channel deep-dive dashboard
  • Click campaign → campaign detail dashboard
  • Click trend chart annotation → event detail

Analyst dashboards (separate, not shown here):

  • Full channel attribution
  • Campaign-level deep dive
  • Lead funnel analytics
  • Weekly/monthly historical

Principle: summary dashboard does NOT try to be analytical. Analytical dashboards separate.

Mobile Considerations

Looker mobile view:

  • Top row (numbers) stacks vertically
  • Charts become tap-to-expand
  • Annotations persist
  • Fast-load optimized

CEO specifically checks on phone weekly meetings — mobile-usable is important.

Key Takeaways

  • Cut dashboard from 25 charts to 7 elements. 5-second scannable top row (3 numbers) + 4 secondary charts. CEO can decide from this.
  • Audience-first: serve VP/CEO decisions (budget allocation, campaign performance, pipeline confidence), not analyst curiosity. Separate analyst dashboards for deep-dive.
  • Semantic color (green/red/blue only). No rainbow. Restrained palette improves comprehension by 40%+ per research.
  • Action-oriented: each chart prompts specific action (reallocate budget, pause campaign, escalate trend). Dashboards without action = decoration.
  • Mobile-responsive matters for executive audience. Test on phone — CEO checks weekly on mobile during travel.

Common use cases

  • Data teams building business dashboards
  • Marketing teams building campaign dashboards
  • Engineering teams building ops dashboards
  • Sales teams building pipeline dashboards
  • Executive teams designing leadership dashboards

Best AI model for this

Claude Opus 4 or Sonnet 4.5. Dashboard design requires audience understanding + data visualization + UX thinking. Top-tier reasoning matters.

Pro tips

  • Audience FIRST. Dashboard for CEO ≠ dashboard for analyst.
  • 5-second test: can user understand main insight in 5 seconds?
  • Chart type matters: bars for comparison, lines for trend, pie only for part-of-whole (rarely).
  • Color is semantic. Red = bad, green = good. Use consistently.
  • Single-action clarity: what should user DO from this dashboard?
  • Remove 50% of first draft. Dashboards over-include.
  • Mobile-responsive where relevant. Executives check on phone.
  • Add context: annotations explain anomalies, benchmarks compare.

Customization tips

  • Show user before finalizing. Watch them interact. Iterate based on actual usage patterns.
  • Remove elements that haven't been clicked in 90 days. Unused metrics = waste.
  • Quarterly dashboard review. Usage analytics show what's working.
  • Don't let 'more is better' culture determine dashboard density. Push back on requests to add more.
  • Style guide for dashboards. Fonts, colors, chart types standardized. Consistency builds usability.

Variants

Executive Dashboard

For C-suite + board. Strategic KPIs.

Operational Dashboard

For daily monitoring.

Analytical Dashboard

For analysts + deep-dives.

Customer-Facing Dashboard

For customers using your product.

Frequently asked questions

How do I use the Dashboard Design Principles — Build Dashboards People Actually Use prompt?

Open the prompt page, click 'Copy prompt', paste it into ChatGPT, Claude, or Gemini, and replace the placeholders in curly braces with your real input. The prompt is also launchable directly in each model with one click.

Which AI model works best with Dashboard Design Principles — Build Dashboards People Actually Use?

Claude Opus 4 or Sonnet 4.5. Dashboard design requires audience understanding + data visualization + UX thinking. Top-tier reasoning matters.

Can I customize the Dashboard Design Principles — Build Dashboards People Actually Use prompt for my use case?

Yes — every Promptolis Original is designed to be customized. Key levers: Audience FIRST. Dashboard for CEO ≠ dashboard for analyst.; 5-second test: can user understand main insight in 5 seconds?

Explore more Originals

Hand-crafted 2026-grade prompts that actually change how you work.

← All Promptolis Originals
P

Curated by

Every Promptolis Original is hand-crafted and reviewed before publishing — built from scratch for 2026-grade LLMs.

Last reviewed on · About Promptolis