“The weekly status deck eats three hours — and nobody reads slide 4.”

The struggle

Wednesday night, and you’re on slide 11. Six of them are screenshots of dashboards your VP has access to. Two exist because a stakeholder asked for them in March. Slide 4 is the detailed engineering status you rebuild every week and have never once been asked about. Thursday morning you present, and within ninety seconds someone jumps to a question that isn’t on any slide — because what they actually wanted was the decision you need from them, and it’s buried on slide 9 under a heading that says “Next steps.”

The obvious fix is a template, and it fails for a specific reason: a template standardizes the slides, not the thinking, so you still spend the three hours hunting status across Slack threads, Jira, and a week of meetings you half-remember, then pouring it into boxes. The real cost isn’t design — it’s reconstruction. And here’s the uncomfortable part this playbook is built around: for most exec audiences the memo alone is the better artifact, and the deck is cargo cult. Slides are a presentation format that got mistaken for a reporting format. This playbook removes the reconstruction, forces the update into one page, and treats slides as an optional last step you should usually skip.

The chain

Step 1 — Let the week write itself down · Fireflies

Connect Fireflies to your calendar once (setup docs) and stop taking status notes. By Thursday you have summaries and action items for every meeting you attended — the raw material for the update, captured while you were busy being in the meeting. Pull the week’s summaries into one document; that’s your input, and it takes about five minutes.

The point of a bot notetaker here isn’t better notes than yours. It’s complete notes across 6–10 meetings, which is the thing you cannot do while participating. Configure it to record only the meetings that matter — Fireflies’ meeting controls let you exclude 1:1s and personal calls, and you should, both for signal and for the consent reasons below.

When to swap it out: if you need capture without a visible bot in the room, Granola records from system audio instead. If your bottleneck is CRM logging rather than PM updates, Fathom leans that way. Any of the three feeds step 2 identically.

Step 2 — Compress to one page, in a format that never changes · ChatGPT

Any frontier model runs this step. Claude and Gemini do this job as well as ChatGPT does; the prompt is plain text in, text out. We name ChatGPT because it’s the one most PMs already have (see last field-tested above) — not because it’s required. Use whichever you already pay for.

One prompt, one page, four sections, same order every week. The consistency is doing real work: an exec who has read your memo three times knows exactly where the ask is, which means they read the ask.

You are writing my weekly update to an executive audience. The source material
below is my meeting notes and summaries from this week. That is the only
material you have.

Write ONE page, maximum 400 words, in exactly these four sections:

SHIPPED — what actually landed this week. Past tense, verifiable, one line each.
SLIPPED — what didn't land, and why, in one clause. Name the cause. No hedging
  verbs: not "we're working to align on scope" but "scope grew after legal review".
DECISIONS NEEDED FROM YOU — maximum 3. Each one: the decision, the realistic
  options, my recommendation, and the date after which waiting gets expensive.
RISKS — maximum 3. Each one: the risk in a sentence, and the single piece of
  evidence that would change my mind about it.

Hard rules:
- Use ONLY what is in the notes. Do not infer status, invent percentages or
  dates, or convert "we discussed X" into "X is decided" or "X is done".
- Anything you cannot attribute to a specific note goes at the bottom under
  "Unconfirmed — needs check", with one line on why it's uncertain. Leave it
  there. Do not promote it into the four sections above.
- When someone committed to something, quote them verbatim and name them.
- No progress adjectives — no "great", "strong", "on track", "solid" — unless
  those words appear in the notes.
- If a section has nothing in it, write "Nothing this week." Do not fill it.

Notes:
"""
<paste this week's meeting summaries>
"""

The “Unconfirmed — needs check” quarantine is the load-bearing rule. Status updates fail in one direction: a hallway remark becomes “aligned”, an intention becomes a commitment, and three weeks later an exec is annoyed because they were told something was decided. Quarantining the unattributable turns that failure into a visible list of five things you have to go ask about — which is a useful to-do list, not a risk. For the standalone version of this prompt, see stakeholder update memo; for the discipline of writing the argument before any slides exist, write the exec summary before the slides.

Step 3 — Slides only if the audience genuinely needs them · Gamma

Read this before you open a deck tool. Slides are worth building when there’s a live room to walk through the material, when the audience includes people who won’t read a doc, or when you’re arguing for something and need a visual — a roadmap shift, an architecture, a chart that carries the argument. Board and steering-committee formats sometimes simply require a deck, and that’s a legitimate reason. Otherwise: send the memo.

If you do need slides, paste the finished memo into Gamma and let it generate the deck from your one page. That ordering matters — the memo is the source of truth and the deck is a rendering of it, so the argument can’t quietly drift while you’re picking layouts. Ten minutes, no restyling.

When to skip entirely: if your last three decks produced no questions and no decisions, they weren’t read. Stop making them and see whether anyone asks. Nobody ever has.

Step 4 — The human check: verify every decision you’re asking for

Before you send, go through the DECISIONS NEEDED section line by line yourself. For each one: is this actually a decision they own, or one you’re deferring? Are the options real, or is one of them a straw man? Is the recommendation the one you’d defend out loud? Is the deadline true?

This is the part that cannot be delegated to a model, because it’s the only part that costs your audience anything. Everything else in the memo is information; these three lines are a request. Wes Kao’s framing is the right test — be specific about what’s blocking you and what you need, and weight the update toward what happens next rather than what already happened. A wrong or lazy decision ask is worse than no memo: it burns the attention you’ll need for the real one. Clear the “Unconfirmed” list in the same pass — resolve what you can, delete the rest, and never ship the section itself.

Where it breaks

• The fixed format needs one-time buy-in. Sending a differently-shaped update unannounced reads as unilateral, and someone will ask where their table went. Spend fifteen minutes once: show your VP the four sections, ask what’s missing, adjust, then never change it again. That conversation is the actual unlock — the prompt is downstream of it.
• You cannot summarize your way out of an unclear strategy. If your memo is honest and still reads as thin, the problem isn’t the format. A one-page update makes a directionless quarter more visible, not less, because there’s nowhere for filler to hide. That’s a feature, and it means the fix is a strategy conversation, not a better prompt.
• Meeting-recording consent. A bot joining every call records your colleagues, and sometimes customers, in jurisdictions with real two-party consent laws. Announce it, let people opt out without friction, exclude 1:1s and anything sensitive, and check your company’s policy before pointing a notetaker at external calls. Read the Security section of the Fireflies docs rather than assuming defaults are compliant.
• “Nobody reads slide 4” sometimes means “send five lines in Slack”. For a healthy project with no decisions pending, the correct weekly update is: shipped X, next is Y, no asks. Three lines, in a channel, done. Running this whole chain to produce a one-page memo that says nothing is a smaller version of the same waste. Match the artifact to the week you actually had.
• The model launders uncertainty into confidence. Even with the guardrails, a summarizer will smooth “Priya seemed uneasy about the timeline” into “timeline confirmed with Priya.” Read the SHIPPED and SLIPPED lines against your own memory of the week, not just against the notes. If a line surprises you, it’s wrong — and you’re the only reader who can tell.