The community for forward‑thinking finance leaders in North Texas.
Ask a CEO what they actually looked at in last month’s reporting pack and the honest answer is often two numbers. The rest was produced, reviewed, formatted, and skipped.
That is not a failure of the people building it. Reporting packs grow by accretion. A director asks a question in March, a metric gets added, and it stays for four years because nobody has standing to remove it. Twelve tabs later, a decision tool has quietly become an archive.
A finance KPI dashboard is worth building only if it reverses that drift. Six metrics that get read beat forty that get scrolled past.
The useful first question is not which CFO dashboard metrics to include. It is which decisions the CEO makes on a monthly cycle, and what needs to be in front of them for each one.
In a mid-market company that is usually hiring approvals, spending commitments, pricing calls, and reserve levels. Each has a small number of real inputs. Working backward from the decision produces a shorter list than working forward from available data, which is the entire point.
That framing also settles arguments about inclusion. A metric that does not change a decision is reference material, and reference material belongs one click down rather than on the front screen.
Headcount by department is the clearest example. It sits on most executive dashboards and almost never changes anything, because the CEO already knows the number from the approvals they signed. It is a status line wearing the costume of a metric.
Everything else is secondary to whether the company can operate. Cash goes first and gets the most space.
A cash panel that informs a decision shows three linked figures rather than one balance:
Runway on its own invites false confidence. Read alongside collection and payment timing, it tells the CEO whether a hiring decision is affordable against real cash movement rather than a projected average. Two companies with identical balances and different DSO are not in the same position, and a single balance figure hides that completely.
Once the metrics are settled, order determines whether they land. Under time pressure people read the top of a screen carefully and skim the rest. A dashboard that puts cash third has already lost.
A sequence that holds attention:
The last item is the one most packs omit and the one CEOs respond to fastest. Three named decisions with the finance recommendation attached to each turns a review into a working session. A dashboard that closes with an appendix gets filed.
Executive reporting runs on pattern recognition. A CEO who sees the same layout every month stops reading the dashboard and starts reading the changes, which takes seconds instead of twenty minutes.
That argues against redesigning the format to accommodate each month’s interesting development. Interesting developments go in the commentary. The structure stays put.
It also rules out incremental monthly additions. Every new panel costs attention somewhere else on the screen, so adding one is a decision to remove another. Treating it that way is what keeps a dashboard from drifting back into a pack.
Three failure modes account for most of it.
The first is stale data. A dashboard fed by manual exports is accurate on the day it is built and unreliable within a week. Worse, the numbers start shifting depending on who compiled them, and once a CEO catches one discrepancy the whole view loses standing. Connected sources solve this, and the cost of connecting them is almost always lower than the cost of that credibility loss.
The second is scope creep back toward the pack. The dashboard launches at six metrics and eighteen months later carries fourteen. A scheduled review where the default is removal rather than addition is the only remedy that holds.
The third is less obvious than either. Nobody owns it. When accuracy is a shared responsibility, discrepancies get found by the CEO in the meeting rather than fixed before it. One name against the dashboard, with the standing to refuse additions, prevents more damage than any design decision.
Monthly suits most mid-market reporting cycles. It matches the close and gives the numbers time to mean something.
Cash is the exception. Weekly cash visibility is worth the effort in most companies and close to essential in any business with lumpy collections or seasonal working capital swings. Splitting the cadence, weekly on cash and monthly on everything else, works better than forcing both onto one rhythm.
McKinsey put a number on this in 2019, drawing on a survey of more than 1,200 managers. Sixty one percent said at least half the time they spend making decisions is wasted, and fewer than half said decisions get made on time.
There is one reliable test of whether a dashboard is fixing any of that, and it is not adoption rates or refresh frequency. It is whether the CEO brings it into conversations you are not in.
Executive reporting comes up constantly in our programming, usually because someone has just rebuilt theirs and has opinions about it. Join us at an upcoming session to compare notes with finance leaders across North Texas: https://feidallas.org/events-calendar/
Leave a Reply