Write a Stakeholder Update That Leads with Decisions, RAG Status and Risk Owners

Turns your raw product notes into a short stakeholder update: decisions needed first, red/amber/green status per initiative, and every risk with an owner and next step.

You getSubject line, decisions needed and initiative status table

Prompt

Prompt
Act as a senior product manager who writes weekly updates for executives and cross-functional leads.

Your job: turn my raw notes into a stakeholder update on product progress and risks. I will paste my notes right after this prompt. If key facts are missing (dates, owners, metrics), ask me up to 4 short numbered questions in one message and wait for my answers before writing.

Rules:
1. Open with Decisions needed: each one names who decides, the options, my recommendation, and the date needed. If none, write "No decisions needed this period."
2. Give each initiative one status: Red (will miss date or goal without help), Amber (at risk, mitigation underway), Green (on track), with a one-line reason tied to a date or metric.
3. Every risk has an owner, an impact, and a next step with a due date. No ownerless risks.
4. Use only facts from my notes; label anything uncertain as "unconfirmed".
5. Keep the update under 350 words.

Output format:
- Subject line
- Decisions needed (numbered)
- Initiative status table: Initiative | Status | Reason | Next milestone and date
- Risks table: Risk | Impact | Owner | Next step | Due
- Wins this period (max 3 bullets)
- Asks and FYI

End with one line listing assumptions made or information still missing.

Example output

At a glanceSprint 14 update at a glancePennywise biweekly update across three initiatives
Decision needed
1 by 12 June
Bank Sync v2: ship with 3 banks or delay
Initiative status
1 Red, 1 Amber, 1 Green
Onboarding at Red
Risks with owners
3 risks
Each with owner, next step and due date
Users covered by 3 banks
78%
Of active users

Example for: a PM at a fictional budgeting app, Pennywise, sending a biweekly update for three initiatives.

Subject: Pennywise product update, Sprint 14: 1 decision needed by Thu 12 June, onboarding at Red

Decisions needed
  1. Delay Bank Sync v2 launch or ship with 3 of 5 banks? Decider: Dana Okafor (VP Product). Options: (a) launch 23 June with 3 banks, (b) delay to 7 July for all 5. Recommendation: (a), since the 3 banks cover 78% of active users. Needed by Thu 12 June.
Initiative status
InitiativeStatusReasonNext milestone and date
Bank Sync v2Amber2 bank APIs failing certification; 3 passedGo/no-go, 12 June
New onboarding flowRedDay-7 retention 31% vs 38% target in A/B testRevised variant live, 19 June
Spending insights widgetGreenBeta at 1,200 users, crash rate 0.2%GA release, 26 June
Risks
RiskImpactOwnerNext stepDue
Northfield Bank API cert slips again9% of users lack sync at launchRaj Mehta (Eng Lead)Escalate with bank partner contact11 June
Onboarding variant B still underperformsQ3 retention goal missedLena Ruiz (PM)Run 5 user interviews on drop-off at step 317 June
Design capacity drops when Sam goes on leave (unconfirmed dates)Widget polish delayedLena Ruiz (PM)Confirm leave dates; borrow 0.5 designer from Growth13 June
Wins this period
  • Spending insights beta: 64% of beta users opened it 3+ times in week one.
  • Support tickets about sync errors down 22% after the retry fix.
  • Bank certification passed for 3 of 5 partners.
Asks and FYI
  • Ask: Marketing to hold the Bank Sync announcement until the 12 June decision.
  • FYI: Onboarding test extended one week; results in next update.

Assumptions and gaps: assumed the 78% coverage figure is current as of May; Sam's leave dates are unconfirmed; no budget impact was mentioned in the notes.

Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • Putting decisions first with a decider and deadline means busy executives act instead of skimming.
  • Defining Red, Amber and Green in the prompt stops vague, optimistic status colors.
  • Requiring an owner, impact and dated next step for every risk turns worries into accountable actions.

Use before a weekly or monthly stakeholder email or steering meeting. Paste your messy notes, Jira summaries or standup bullets into ChatGPT, Claude or Gemini; include owners and dates if you have them.

Common edits

  • Ask for a 5-bullet Slack version alongside the full email.
  • Add a Metrics section with this period versus last period for your top 3 KPIs.

Prompt details

By
Prompts-GPT editors
Published

Did this prompt work?

Keep exploring

More in Product Management