Convert my raw bullets below into a weekly stakeholder update. Use exactly three sections:
1. Shipped: each item with a one-line outcome, not a feature name. 'Filter persistence rolled out, 18% reduction in time-to-first-result' - not 'Shipped filter persistence.'
2. Stalled: each item with the specific blocker named (person or thing) and an ETA if one exists. Do not include items that are just 'in progress' - those don't belong here.
3. Asking for help: each item with the specific decision or action needed and the named decision-maker. If there are no asks, write 'No asks this week' explicitly.
Banned phrases: synergy, leverage, circle back, touch base, on track, in flight.
My raw bullets:
{{raw_bullets}}
Stakeholder weekly update
Add to PromptPaste
Download PromptPaste for MacDownload PromptPaste for iPhoneDownload PromptPaste for iPadDownload PromptPaste for Mac & iPhone
the prompt
Example output
Week of 2026-04-26:
Shipped:
- Filter persistence rolled out to 100% of power users. Median time-to-first-result down 18% (target was 20%).
- Bug fix for empty-state crash on iPad - reduces crash rate by ~3% based on Crashlytics.
Stalled:
- Cross-device sync design review - blocked on iCloud capacity confirmation from infra. Expected Tuesday.
- Pricing page rewrite - blocked on legal review of new tier copy. Owner: Maya, ETA Friday.
Asking for help:
- Need a decision by Wednesday: ship cross-device sync as opt-in (lower risk, slower adoption) or opt-out (higher adoption, more support load). I lean opt-in. Decision-maker: Sarah.
- One open eng req for the persistence team backfill. Status?
Common mistakes
Don't include a 'shipped' line that's just a feature name without an outcome - 'shipped filter persistence' is useless; '18% reduction in time-to-first-result' is a status report. Don't write 'in progress' or 'on track' in the stalled section - if it's not stalled, it doesn't belong there. Also: never mix the asking-for-help section with the shipped section. The whole point of separating them is so stakeholders see the asks instead of skimming past them. If you have no asks, write 'No asks this week' explicitly - silence reads as 'nothing to do here' and leaves you unblocked-but-stuck.
More from AI Prompts for Product Managers
PRD draft from a one-line problem
Act as a senior product manager. I'm going to give you a one-line problem statement. Before drafting any PRD, do this: 1. State the…
Customer interview synthesis
Read the raw customer interview transcripts below. Produce: 1. The top 5 themes ranked by frequency (number of interviews where the theme…
Decision memo (one-pager)
Convert the messy debate input below into a structured one-page decision memo. Use exactly these sections: 1. Decision: stated in one…
Why it works
Stakeholder updates are the third-most-cited PM AI use case (74% report value, 18.5% top value). Most PMs write these on Sunday night and they're either too long or too vague. This prompt enforces three sections: shipped (with one-line outcome, not features), stalled (with specific blocker, not 'in progress'), and asking for help (with the explicit decision or unblocking action needed). The structure does two things: it forces you to acknowledge what's stuck (which is what stakeholders actually want to know), and it ends with the ask, which is the difference between an update people skim and one they act on. Banned phrases prevent the model from defaulting to corporate filler that signals you didn't really think about the week. Tested cleanest on Claude Opus 4.7.