A steering committee readout fails when it replays the engagement timeline instead of driving decisions. The consulting team did twelve weeks of work, and the instinct is to show all of it: every workstream gets a section and every milestone gets a slide. But a chronological recap treats every piece of work as equally important, which means nothing gets treated as important at all. The steering committee does not need to know what happened in Week 3; they need to know what was decided and what decisions remain.
Readouts organized by decisions hold the room’s attention
The chronological structure is the tell. When a readout is organized by time (i.e., “here is what we did in Phase 1, here is what we did in Phase 2”), the organizing principle is the engagement’s schedule rather than the audience’s needs. Replaying the full timeline adds nothing the room can act on. A readout for a steering committee serves two purposes:
- Confirm what was decided and surface what still needs the room’s input. The leadership team approved decisions throughout the engagement, often in separate meetings or through different channels. The readout consolidates those decisions into a single view so the room can confirm alignment, while also presenting the open items, unresolved dependencies, and deferred decisions that require executive authority. If the readout doesn’t present them clearly, the meeting ends without advancing them.
- Articulate what happens next. The audience leaves with a clear understanding of the next phase, the next milestones, and who owns what.
These purposes (i.e., what we decided and what the room needs to weigh in on, plus what’s next) should drive the structure of every readout. When they do, the deck is twelve to fifteen slides and drives three to four specific decisions; when they don’t, the deck is forty slides and drives nothing.
Organizing by decision produces a tighter, more actionable deck
The fix is to organize by decision rather than by time. The principle of content before slides applies here: decide what decisions the readout must drive before opening the slide editor. Lead with the decisions, supported by evidence. The first substantive section presents the key decisions made during the engagement. Each decision is stated clearly: what was decided and what it means for the program. This gives the room a foundation of shared understanding. The analysis, sessions, and artifacts are supporting evidence for the decisions; they don’t need their own sections. They appear in context, as the rationale behind a specific decision or the data that informed a specific recommendation. A workstream’s twelve weeks of work might be represented as two slides that support a single program-level decision. The work was done to enable the decision, and the readout should show that. End with the asks. The final section presents open items, unresolved decisions, and next steps requiring the room’s attention. Each ask is specific: here is the decision, here are the options, here is our recommendation, and here is the timeline. The room leaves with clarity about what they need to do, not a general sense that the program is on track.
Practical observations
A readout that follows this structure consistently runs fifteen slides instead of forty, finishes with time remaining for discussion, and produces actual decisions in the room rather than nods of acknowledgment. A readout a CFO will actually read follows this pattern, as does the readout that changed an executive’s mind. When the readout is the final one, the same discipline shapes the transfer of ownership that closes the engagement. The core practice is straightforward: before building a single slide, write down the three to five decisions the readout needs to drive, then build only the slides that support them.
