How many slides should a steering committee deck have?
Ten to fifteen slides in the main pack, with an appendix of any length behind it. That covers status, decisions, risks, financials, milestones and forward look at one idea per slide. The main section is what gets presented; the appendix is attached for reference and never depended on by a slide in front of it.
The core pack
A monthly committee has sixty to ninety minutes, of which perhaps twenty are spent on the pack itself. At a realistic pace of a minute or two per slide, ten to fifteen slides is not an aesthetic preference — it is what fits.
| Slide | Contents |
|---|---|
| 1. Cover and agenda | Programme, period, attendees, agenda |
| 2. Executive summary | Overall RAG, three or four sentences, what the committee is being asked for |
| 3. Decisions required | The list, each with an owner and a due date. Detail follows. |
| 4-6. Decision slides | One per decision: question, options, cost, recommendation, consequence of deferral |
| 7. Status by workstream | RAG per workstream with direction of travel |
| 8. Milestones | Baseline against forecast, next quarter |
| 9. Risks | Top items needing committee attention, with owner and mitigation |
| 10. Issues | Open issues by severity with age and resolution date |
| 11. Financials | Spend to date, forecast at completion, variance and cause |
| 12. Dependencies | Cross-team and external commitments at risk |
| 13. Forward look | Next period's milestones and what returns to this committee |
| 14. Actions | Open actions from previous meetings with owners and dates |
Fourteen slides, of which three are decisions. A month with one decision produces a twelve-slide pack; a month with a gate decision produces something longer and differently shaped.
One idea per slide
Slide count is a proxy for something more useful: whether each slide makes one point. A pack of eight slides carrying three points each is harder to present and harder to read than fourteen carrying one. Splitting a crowded slide usually improves the pack even though it makes the number go up.
The related discipline is that the headline of each slide states the point rather than naming the category. "Financials" tells the reader where they are. "Forecast at completion is 8% above approved budget, driven by the extended UAT window" tells them what to think about. A committee reading only the headlines should arrive at the same conclusions as one reading everything.
The appendix
The appendix can be any length. It exists so the presented section can be short. It carries the full risk log extract, the detailed financial breakdown, the plan on a page, test progress, resourcing, vendor status — whatever the committee has asked for before and might ask for again.
One rule keeps it honest: nothing in the main section may depend on the appendix. If understanding slide 4 requires slide 27, the pack is twenty-seven slides long and the structure is decorative. In practice that means the main slide carries the number and the conclusion, and the appendix carries the working.
Why decks grow
- A committee member asks a question once, and the answer becomes a permanent slide.
- Each workstream contributes a slide, and the pack becomes the sum of the contributions rather than a view of the programme.
- A previous pack was challenged, so detail is added defensively.
- Nothing is ever removed, because removal invites the question of why it was there.
- The pack is doing double duty as an audit record.
The countermeasure is a quarterly pass over the standing slides, asking which of them changed a decision. Most packs lose three or four slides to that question without anybody noticing.
What changes the count
Gate meetings run longer, because the committee is approving a phase transition and needs the evidence in front of it — a go/no-go pack is typically ten to twenty slides of readiness evidence, and it usually replaces the normal agenda rather than sitting alongside it. Multi-programme committees run shorter per programme, often one summary slide each plus shared decision slides. Agile programmes report differently again: the same governance questions answered with flow and increment data rather than milestone dates, which is what the Agile Governance Deck is built around.
Building the pack
Most of the pack should be assembly rather than authorship. If the RAID log, the plan and the budget tracker are current, the risk, milestone and financial slides are extracts, and the only writing required is the executive summary and the decision slides. Where the pack is being written from scratch each month, that is usually a sign the underlying artefacts are not being maintained — and the pack becomes the only current record of the programme, which is a fragile place for it to live.
The SteerCo Deck (PowerPoint) runs to 15 slides in this order, with the decisions ahead of the detail. The Program Governance Deck Bundle adds the risk register, decision log and dependency matrix packs that most appendices end up needing. What goes into the pack in the first place is covered in the steering committee report guide, and the way the pack maps onto the meeting itself in programme governance.
Questions
Is a one-page steering report enough?
For a small project reporting into a wider committee, often yes. A full programme usually needs decision slides with options and costs, which do not compress onto one page.
Should every workstream get a slide?
Only if the committee acts on workstream-level detail. Most packs work better with one status slide covering all workstreams and workstream detail in the appendix.
How long should the appendix be?
Any length, provided nothing in the main section depends on it. Fifty slides of appendix behind twelve presented slides is a normal and workable pack.
Does the pack need to be PowerPoint?
No, but it needs to be readable on a screen in a room. A dense spreadsheet projected at the front of a meeting room is the most common cause of a committee asking for the numbers to be read aloud.