How to turn a project update into a 10-minute team presentation

A status update says: “Here is what happened.” A decision update says: “Here is what we need to do because of what happened.” Most project meetings need the second one, even when the calendar title says status.

If nothing needs a decision, the meeting may not need a deck at all. A short written note can be better. If the team needs to unblock work, choose a scope or agree on a trade-off, a deck can help keep the conversation on the same page.

1. What changed since the last update?
2. What is at risk, and what would make it worse?
3. What decision is needed now?
4. Who owns the next step and by when?
5. What should the team stop, defer or escalate?

If a slide does not help answer one of those questions, it is probably background. Move it to the notes or the read-ahead.

You do not need to write a formal brief before generating. A structured note is enough:

Goal: Ship the billing migration without missing the November close.
Changed: The export job now runs in staging; two reconciliation checks still fail.
Risk: Finance cannot sign off until the duplicate-charge test is clean.
Decision: Keep the November 14 cutover, or move it to November 21.
Recommendation: Keep the date and freeze new scope for one week.
Owners: Priya owns reconciliation; Marcus owns the customer communication.
Ask: Approve the scope freeze today.

Paste that into the slide maker and choose a short deck. The result is usually more useful than a slide that lists every ticket in the sprint.

Five slides are free and need no account. That is enough for a recurring team update: the change, the risk, the decision, the owner and the next checkpoint. If the meeting needs more context, add it to the source rather than adding decoration.

The product is designed for text. If the update depends on a chart, describe the takeaway in words: “Support volume is flat while the backlog is growing because two agents are on leave.” The deck can carry the claim; the source report can carry the chart.

Read the slide titles in order. A useful sequence sounds like:

• “The cutover still holds if scope freezes this week.”
• “Two reconciliation checks are the only remaining risk.”
• “The team recommends keeping November 14.”
• “Scope freeze starts today; communication goes out Friday.”

If the titles are “Status,” “Risks,” “Next steps,” the deck has structure but no argument. Rewrite the source headings as claims and generate again. This is faster than trying to polish a deck that has nothing to say.

Copy the deck link into the project channel and the meeting notes. If someone needs a visual in chat, share the image card instead. The image is a preview with a QR code back to the deck; the link is the current version. Neither requires the recipient to install anything or create an account.

For recurring updates, keep the source note and regenerate when the facts change. Do not keep sending a downloaded file with a version number in the name.

The most common failure is a deck that proves the team was busy. It lists every completed task, every meeting and every dependency, then asks for five minutes to discuss “next steps.” The audience cannot tell which fact matters.

A better update is smaller and more opinionated. It says what changed, what it means and what decision the team should make. That is not spin; it is the job of a presentation.

Take the update you were going to paste into Slack and put it into the slide maker. Keep the goal, changes, risk, decision, owner and ask. Generate five slides, then read the titles. For a longer report-backed update, read report to presentation. For an update you have to give in the next ten minutes, use the last-minute workflow.