A CFO reads a readout differently than a COO, CTO, or Chief Strategy Officer. Financial executives process information through a specific lens: what does this cost, and what do you need from me. A readout that doesn’t match this processing style will be skimmed or ignored regardless of how well the program is going. Most readout decks are designed for the program team or executive sponsor, then repurposed for the CFO by adding a budget slide somewhere in the middle; that approach asks a financial executive to work through operational narrative to find the information they need. They’ll flip to the slide with numbers, evaluate it without context, and form a judgment that may not align with the program team’s intent: exactly how readouts that read like book reports fail their audience.
Financial Executives Look for the Financial Frame First
Before a CFO engages with strategy or milestones, they want two numbers and a scenario: what does this cost, and what happens if we delay. Those data points establish whether the program is worth their attention. They evaluate tradeoffs in financial terms: “We recommend accelerating the pilot” does not register until it’s translated into “Accelerating the pilot costs an additional $400K in contractor spend and pulls the revenue impact forward by one quarter, meaning $2.1M in incremental margin hits FY26 instead of FY27.” They want the decision point stated explicitly: what do you need from me? Budget approval or timeline extension. If the ask is unclear, the CFO treats the readout as informational and doesn’t engage with it as a decision.
Build the Readout on Three Slides
A readout designed for a CFO can be built on three slides; everything else is appendix. The principle is the same as deciding content before slides: determine what the audience needs to know before designing how to present it. Slide 1: The financial frame. Present the program’s cost structure and financial impact of delay. Use the units the CFO works in:
- Fully loaded cost including internal labor
- Revenue impact by fiscal year
- Budget variance: is the program on budget, and if not, what caused the deviation and is it a trend?
Slide 2: The tradeoff. Most programs that need a CFO’s attention are at a decision point involving a financial tradeoff: more investment for faster results or scope reduction to stay within budget. Lay out options with financial implications side by side: Option A costs X, produces Y, carries risk Z; Option B costs less, produces less, takes longer. Slide 3: The ask. State the specific decision the CFO needs to make in terms they have authority over (e.g., “We are requesting approval to add $200K to the Q3 budget to staff two additional integration engineers, which keeps the October launch date. The alternative is to defer the launch to January with no additional spend”). That’s an ask a CFO can act on in the room; one readout that changed an executive’s mind used exactly this structure.
What to Cut from a Program-Focused Readout
Cut the milestone-by-milestone status update; the CFO needs to know whether the program is on track and whether there’s a decision to make. Cut the organizational narrative: how the team arrived at a recommendation, the workshops that were run. That’s important context for the program sponsor and background for the CFO; if they ask, it’s in the appendix along with the full risk register. Show only the risks with financial implications above the threshold that warrants their attention, stated in dollar terms with mitigation plans attached. The three-slide structure puts financial information first, the tradeoff second, and the ask third. Design the readout for how the audience reads, because the way the closing hits land depends on whether the audience was with you from slide one; the readout is one part of a larger transfer of ownership.
