Stakeholder and executive updates without the spin
Weekly updates and exec summaries are repetitive, high-stakes writing: the same scattered progress notes reshaped for engineers, leadership, and the exec team. PMs use AI to turn a pile of notes into a clean narrative in minutes. The risk is tone drift into vague optimism, so the prompt bars spin and forbids inventing numbers you didn't supply.
You are helping a product manager write a status update. Reshape my raw notes into a clear update for a specific audience. Audience and what they care about: {{audience}} Raw progress notes from this period: {{progress_notes}} Metrics to include (with targets): {{metrics}} Decisions or resources I need from this audience: {{asks}} Structure: - TL;DR in two sentences: are we on track, and the single most important thing to know - What shipped / what progressed - Metrics vs. target, stated plainly - Risks, blockers, and what would change the plan - Decisions or resources needed, as a short numbered list - What's next Rules: - Use only the facts and numbers I gave you. If a metric or date is missing, insert "[METRIC]" or "[DATE]" — never estimate one. - No spin: if something slipped or a metric is down, say so directly. Don't soften a red status into "some challenges". - Match the altitude to the audience: strategy and outcomes for execs, specifics for the working team. - Keep it under 250 words.
Fill in your details and the prompt updates live — then copy.
TL;DR: On track but not there yet — the guided source picker is lifting day-1 activation, and I need two more weeks of test data before a full rollout. Progress: Guided picker live to 50% of new users; A/B test running. Sample-dashboard concept reviewed with design. Metrics vs. target: Day-1 activation 39% in the test cohort vs. 34% baseline (target 50%). Trial-to-paid flat at 12%. Risks: A connector bug pushed the mobile fix out a week. Decision needed: approve holding the test two more weeks before rolling to 100%.
The full workflow
- Dump your raw notes and pull the exact metric values before prompting
- Generate the update, then fill any [METRIC] or [DATE] placeholder from the source, not from memory
- Read it once for honesty: would you say the same thing out loud in the room?
- Paste into your own channel or email and send under your name
Watch out for
Financial figures, usage numbers, and unreleased plans in an update are confidential business data. Use an enterprise AI tool your company approved with training disabled; don't route internal metrics through a personal free account.
AI defaults to a confident, upbeat register. Left unchecked it will paper over a slipped date or a flat metric — the reader is trusting your judgment, not the model's tone.
Never let a placeholder ship. A '[METRIC]' that reaches an exec reads as carelessness; an invented number that reaches one is worse.
Where this comes from
Every use case on this site is grounded in real reports from working product managers — not invented by us.