Gixo Lumen · deck structure
Project Management Presentation
A status deck exists to get blockers unblocked. Lead with the honest status and what you need — the detail of what the team did is the least useful part for the people in the room.
Last reviewed: August 2026
The slide sequence
Each step names the Lumen slide layout to use, so you can build this deck by adding layouts to a blank deck in order. Manual building is free and unlimited, and it does not consume the AI meter.
What makes this deck fail
- Green status with a red blocker. Status inflation destroys the value of every future report.
- Decisions on the last slide. They get squeezed by overrun; put them in the first half.
- An activity log. Sponsors need exceptions and decisions, not everything the team did.
- Blockers with no owner or ask. Naming a blocker without saying what would fix it changes nothing.
- Rebuilding the deck each time. A fixed structure lets people find what they care about instantly.
Adapting the length
| You have | Keep | Cut |
|---|---|---|
| 10 minutes | Status, blockers, decisions, next milestone | Budget, scope detail |
| 30 minutes | The full sequence as listed | Nothing |
| Written update | Everything, plus links to the tracker | Nothing |
Weekly status vs monthly steering
The same structure serves both, at different depths. A weekly status is four slides and twenty minutes: status in one word, what moved, blockers with owners and asks, decisions needed. Nobody in a weekly meeting can act on the budget position or the scope log, and including them is how the decisions slide gets squeezed by the overrun.
A monthly steering meeting is where budget, resourcing, scope changes and the risk trend belong, because a sponsor can act on those at that interval. Keep the first four slides identical to the weekly so people find them in the same place, then add the rest behind them. Reordering between the two is the most common reason a steering group starts asking for a written update instead.
Frequently asked questions
What should a project status presentation include?
Status in one word, progress against plan, what changed, blockers with owners and asks, decisions needed, risks, and the next milestone with a date.
How often should project updates be presented?
Fortnightly for active delivery and monthly for steering groups. Consistency of structure matters more than frequency, because people learn where to look.
What is the most common mistake in status decks?
Reporting green while a real blocker is unresolved. Status inflation costs you credibility permanently and makes every later report harder to trust.
Should status decks include a detailed plan?
No. Link to the tracker and keep the deck to exceptions and decisions, or the meeting turns into a plan review rather than a decision forum.
What is the difference between a project management presentation and a status report?
The report is a record and can be read at any time. The presentation exists to get something decided while people are in the room, which is why it leads with status in one word, puts decisions in the first half, and links to the tracker instead of reproducing it. If nothing needs deciding, send the report and give the hour back.
Can I build a project status deck for free?
Yes. Building manually from a blank deck in Gixo Lumen is free and unlimited on every plan, with no export paywall.
Related deck structures
Build this deck without paying for it
Start from a blank deck, add these layouts, and export a real PPTX — manual decks are free and unlimited on every plan, with no export paywall. Use the AI path when you would rather hand over source material and edit the result.