Every other Wednesday, the PMO disappears into PowerPoint
Your firm runs the programme management office for a client's transformation. Every fortnight, the steering committee meets, and the pack is the firm's most visible output. Building it means updating the milestone chart, the RAG status for each workstream, the top risks and issues, the decisions log, the budget position and the benefits tracker, all from their spreadsheets, into slides.
Workstream leads send updates late and in different formats. Numbers in the pack do not match the trackers because someone changed a tracker after copying. The team finishes at midnight and the pack still needs partner review.
Why packs take so long
- Data lives in several trackers, spreadsheets and tools.
- Every slide is updated by copying and pasting.
- Workstream updates arrive in inconsistent formats.
- Last-minute tracker changes are not reflected in the slides.
- The format is the same each cycle, but the work is repeated from scratch.
Consistency matters more than it seems. Steering committee members compare this pack with the last one. If a milestone moved or a risk disappeared without explanation, they notice, and a PMO that cannot explain its own numbers quickly loses authority in the room.
What that costs
| Issue | Effect |
|---|---|
| Days of consultant time per cycle | Less time on the programme itself |
| Inconsistent numbers | Sponsor loses confidence in the PMO |
| Rushed commentary | Committee discussions less useful |
| Late packs | Members cannot prepare |
A steering committee pack is supposed to support decisions. When most effort goes into assembling it, the thinking gets squeezed.
It also crowds out the PMO's real value. The most useful thing a PMO can do before a steering committee is spot the workstream that is quietly slipping and get the right decision on the agenda. That analysis is what gets dropped when the team is busy copying numbers into slides.
How we build a pack generator
- We connect to your trackers, whether Excel files in SharePoint, Smartsheet, Jira, Microsoft Planner or a custom tool, and read milestones, status, risks, issues, decisions and budget.
- Workstream leads submit updates through a short form with consistent fields: RAG, key progress, next steps, escalations.
- The generator builds the standard slides in your PowerPoint template: milestone chart, workstream status, top risks, decisions required, budget and benefits.
- Numbers on the slides are drawn directly from the trackers, so they match.
- The team adds commentary and the executive summary, which is where their judgement goes.
- A language model can draft a summary of changes since the last pack for the team to edit.
- Packs are saved with a snapshot of the data behind them, so any figure can be traced later.
We usually start by rebuilding one recent pack from the trackers, with the team, to agree which slides can be generated and which need human writing. The first live cycle runs alongside the manual process so everyone can compare the results.
What PMO fortnights look like after
The pack's standard slides are ready within minutes of the update deadline. The team spends its time on the executive summary, the decisions the committee needs to make, and chasing the workstream that is slipping.
The sponsor gets a consistent, accurate pack on time, which is the PMO's reputation in a single document.
Is this your PMO?
- Steering committee packs take days to build.
- Numbers in the pack sometimes disagree with trackers.
- Workstream updates arrive late and inconsistent.
- Commentary is written in a rush.
- The same slides are rebuilt every cycle.