The CFO's Dashboard: What Executives Actually Want to See
I've sat on both sides of the dashboard. As a Finance Director at Morgan Stanley, I received dozens of reports monthly. As a consultant, I build them. The gap between what gets built and what gets used is enormous.
The core problem: Damco Group's 2026 research confirms that finance teams build dashboards around available data, not around the decisions executives need to make. They recommend a "decision-first workshop" before any dashboard is built.
What CFOs Actually Care About
After working with dozens of finance leaders, here's what consistently matters:
1. "Are we on track?" — Budget vs. Actual
The single most important view. Not a detailed variance report — a simple answer: green, yellow, or red.
| What CFOs Want | What Teams Build |
|---|---|
| One number: "We're at 97% of budget" | 47-row variance table |
| Trend: "Getting better/worse" | Static monthly snapshot |
| Exception only: "Show me what's wrong" | Everything, including what's fine |
2. "What's the cash position?" — Liquidity Dashboard
Cash is king. CFOs want to know: how much cash do we have, what's coming in, what's going out, and when.
Best practice: Show 13-week rolling cash forecast. Not a P&L — a cash flow. The difference matters more than most finance teams realize.
3. "Where are we growing?" — Revenue Drivers
Not total revenue (they know that). What's driving it: volume, price, mix, new customers, retention. Drill-down from total to segments to individual drivers.
4. "What should I worry about?" — Exception Alerts
The most valuable dashboard feature isn't a chart — it's an alert. When a metric crosses a threshold, the CFO should know immediately, not at month-end.
The Navigation Depth Model
Destructor's research on CFO dashboard preferences identifies "navigational depth" as the key to converting a static reporting tool into a genuine decision-support environment.
Here's how I structure it:
Level 1 — Executive Summary (30 seconds)
- 3-4 headline KPIs as large numbers
- Color-coded status (green/yellow/red)
- Sparkline trend (12-month)
Level 2 — Category View (2 minutes)
- Revenue by segment
- Cost by category
- Key ratios (margin, ROIC, working capital)
Level 3 — Detail Drill-Through (on demand)
- Transaction-level detail
- Variance explanations
- Supporting documentation
A CFO spends 30 seconds on Level 1 daily. 2 minutes on Level 2 weekly. Level 3 only when investigating anomalies.
The KPI Selection Framework
Not every metric deserves a spot on the CFO dashboard. Use this filter:
| Question | If Yes → Include | If No → Exclude |
|---|---|---|
| Does this metric directly affect a decision? | ✅ | ❌ |
| Can the CFO influence this metric? | ✅ | ❌ |
| Does this need attention right now? | ✅ | ❌ |
| Is this already covered by another metric? | ❌ (don't duplicate) | ✅ |
Typical CFO dashboard: 6-8 KPIs maximum.
Real-World Dashboard Architecture
Here's what I build for CFOs:
| Page | Content | Audience |
|---|---|---|
| Executive Summary | 4 KPIs + status + trend | CFO (daily) |
| Financial Performance | P&L, margin, EBITDA | CFO + Finance team (weekly) |
| Cash & Liquidity | 13-week forecast, AR/AP aging | CFO + Treasury (daily) |
| Budget Tracker | Budget vs actual by cost centre | CFO + Department heads (monthly) |
| Exception Report | Threshold breaches, anomalies | Finance team (daily) |
Design Principles for Executive Dashboards
-
Numbers over charts. Executives read numbers faster than they interpret charts. Lead with the number, support with the chart.
-
One page per purpose. Don't combine financial performance and cash flow on the same page. They're different questions.
-
Consistent layout. Same KPI should always be in the same position. Executives build muscle memory.
-
Mobile first. 40% of executive dashboard views happen on phones during commutes or meetings.
-
Time context. Every number should answer: "compared to what?" Show budget, prior period, and prior year.
What I Changed After Being a CFO
As a Finance Director, the dashboards I actually used shared three traits:
- They loaded in under 3 seconds. If I had to wait, I closed it.
- They answered my question on the first screen. I never drilled through 4 levels to find the answer.
- They were updated when I opened them. Stale data is worse than no data.
When I build dashboards now, I test against these three criteria before anything else.
Facing a similar challenge?
📅 Book a Free Call