Executive View

Building the executive dashboard —the 5-7 numbers the CEO, CFO, and board review weekly —that tells the story of the business without requiring the executive to drill into operational detail.

Why

Executives do not have time to drill into operational dashboards, and if they try, they get lost in the detail and miss the story. The executive view is a curated 5-7 number summary that answers 'is the business healthy and getting healthier?' in 30 seconds, with enough context to know whether to dig deeper or move on. The design is different from an operational dashboard: it shows the trend (not the current value in isolation), the comparison to plan (not just to last period), and the narrative (what changed and why). A common failure is giving the executive the same dashboard as the operator —40 widgets, no narrative, and the executive spends the weekly review asking 'what does this number mean' instead of making decisions. Another failure is showing only positive numbers —the executive view must show the misses (churn up, CAC up, payback lengthening) with equal prominence to the hits, because the misses are where the executive's attention is most valuable. The executive view should be paired with a written narrative (3-5 sentences) that explains the week: 'MRR grew 3% (on plan), but trial-to-paid dropped from 3.5% to 2.8% due to a checkout bug on Thursday that was fixed Friday; net new MRR is $48k vs $55k target.' The narrative is what the executive reads first, and the dashboard is the evidence.

When

When the CEO/board asks for a weekly business update. When the executive dashboard has more than 10 widgets. When the weekly review meeting spends more time explaining numbers than making decisions.

How

1. Ask the CEO what 3 questions they need answered each week to know the business is healthy —these define the executive view; typical answers: 'are we growing on plan?', 'is unit economics healthy?', 'are there any risks I should know about?'
2. Choose 5-7 numbers that answer those questions: MRR (growth), net new MRR (growth rate), LTV:CAC (unit economics), payback period (cash health), churn rate (retention risk), NPS (customer health), runway (survival risk)
3. For each number, show three things: the current value, the trend (8-week sparkline), and the comparison to plan (vs target, with green/yellow/red status) —the comparison to plan is what the executive cares about most
4. Write a 3-5 sentence narrative above the numbers: 'MRR grew 3% to $1.42M (on plan). Trial-to-paid dropped to 2.8% (below 3.5% target) due to a checkout bug Thursday, fixed Friday. Net new MRR $48k vs $55k target —$7k gap from the conversion drop. Churn stable at 2.1%. Runway 18 months at current burn.' —the narrative is the executive's primary read
5. Show misses with equal prominence to hits: if churn is above target, it is red and the same size as MRR —the executive's attention is most valuable on the problems, not the wins
6. Include a 'risks' section: 2-3 sentences on the risks the executive should be aware of (a key competitor launched, a regulatory change is pending, a key engineer is leaving) —these are not in the numbers but they affect the business
7. Link to the operational dashboard for drill-down: the executive view is the summary; if they want to investigate the conversion drop, they click through to the growth team's dashboard —but the default view is the summary, not the detail
8. Send the executive view as a weekly email (Monday 8am) with the narrative in the body and the dashboard as an attachment —the executive reads the narrative in 30 seconds on their phone and decides whether to open the dashboard
9. Review the executive view quarterly with the CEO: the questions that matter change as the business stage changes, and the numbers that answered 'are we growing?' at $1M ARR may not answer 'are we profitable?' at $10M ARR
10. Keep it to 5-7 numbers: if the CEO asks to add a number, ask which one to remove —focus is the point, and 12 numbers is not an executive view, it is a data dump

Example

# Executive View: Week of Sep 22, 2026
To: CEO, CFO, Board  From: Head of Data  Sent: Mon 8:00am

Narrative (3 sentences):
  MRR grew 3% to $1.42M (on plan). Trial-to-paid dropped to 2.8%
  (below 3.5% target) due to a checkout bug Thursday, fixed Friday;
  net new MRR $48k vs $55k target —$7k gap from the conversion drop.
  Churn stable at 2.1%, runway 18 months at current burn.

Dashboard (6 numbers, each with value + trend + vs plan):
  MRR:              $1.42M  [sparkline]  103% of plan  [GREEN]
  Net new MRR:      $48k    [sparkline]   87% of plan  [YELLOW]
  LTV:CAC:          3.2:1   [sparkline]  106% of plan  [GREEN]
  Payback:          4.8 mo   [sparkline]   96% of plan  [GREEN]
  Churn:            2.1%    [sparkline]  100% of plan  [GREEN]
  Runway:           18 mo   [sparkline]   90% of plan  [YELLOW]

Risks (2 sentences):
  Competitor Acme launched a free tier on Sep 20 —monitoring
  impact on trial signups (no change yet, reviewing next week).
  Lead engineer on payments team gave notice —replacement
  recruiting started, no risk to near-term roadmap.

Drill-down links:
  - Growth dashboard (investigate trial-to-paid drop)
  - Retention dashboard (churn detail by cohort)
  - Finance dashboard (runway and burn detail)

Weekly review meeting (Monday 10am):
  - 5 min: narrative read (no explanation needed)
  - 10 min: discuss the yellow numbers (net new MRR, runway)
  - 5 min: discuss risks (competitor, engineer departure)
  - 10 min: decisions (add checkout test, accelerate hiring)
  Total: 30 min (was 60 min before the executive view)

Common Problems

⚠Giving the executive the same 40-widget dashboard as the operator —the executive spends the weekly review asking 'what does this number mean' instead of making decisions; the executive view should have 5-7 numbers and a narrative, not 40 widgets.
⚠Showing only positive numbers —the executive view that shows MRR growth but hides churn increase is misleading, and the executive's attention is most valuable on the problems; misses must be shown with equal prominence to hits.
⚠No written narrative —the executive opens the dashboard, sees 6 numbers, and has to reconstruct the story themselves; the 3-5 sentence narrative is what the executive reads first, and the dashboard is the evidence that supports it.
⚠Comparing only to last period instead of to plan —'MRR grew 3% vs last week' is good but not actionable; 'MRR is 103% of plan' tells the executive whether the business is on track, which is what they need to know.
⚠Not updating the view as the business stage changes —the numbers that answered 'are we growing?' at $1M ARR (MRR, signups) do not answer 'are we profitable?' at $10M ARR (gross margin, net income); the executive view must evolve with the stage.

Best Practices

✓Build the executive view around 3 questions the CEO needs answered weekly, with 5-7 numbers and a 3-5 sentence narrative —the narrative is the primary read (30 seconds on a phone), the numbers are the evidence, and the drill-down is available but not the default.
✓Show misses with equal prominence to hits —the executive's attention is most valuable on the problems (churn up, CAC up, payback lengthening), and a view that hides misses is misleading and deprives the executive of the information they need most.
✓Compare every number to plan, not just to last period —'103% of plan' tells the executive whether the business is on track, while '3% vs last week' does not; the plan comparison is what drives the executive's confidence and decisions.
✓Include a risks section (2-3 sentences) for things that are not in the numbers but affect the business —a competitor launch, a regulatory change, a key departure; these are the strategic risks the executive needs to know about but that no dashboard captures.
✓Review and update the executive view quarterly as the business stage changes —the questions that matter at $1M ARR (growth) differ from $10M ARR (profitability) and $50M ARR (efficiency), and the view must evolve to answer the current stage's questions.