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
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
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 like this
Analyze Your Product Funnel and Find the Biggest Drop-Off to Fix First
Paste your funnel step counts and get a conversion table, the largest leak flagged with reasoning, and one testable fix per step with an expected lift range.
Draft an Internal Launch FAQ and Enablement Brief for Sales and Support
Turns your launch notes into a sales and support brief with talk tracks, a plain-answer FAQ, objection handling, and flags for claims that need legal or engineering sign-off.
Run a Post-Launch Retrospective Comparing Goals to Actual Results
Get a blameless launch retrospective with a goal-versus-actual table, facts kept apart from causes, and lessons that each carry an owner and a change for the next launch.
Draft a Now/Next/Later Quarterly Roadmap Tied to One Outcome Metric
You get a one-quarter roadmap grouped into Now, Next and Later, with every item linked to your outcome metric, a confidence level, a leading signal and parked items.
Synthesize User Interview Notes into Counted Themes and Insights
Turns raw interview notes into a ranked theme table showing how many participants raised each theme, with observations kept separate from interpretation.
Turn Engineering Changelogs into Customer Release Notes Users Read
Paste a changelog or ticket list and get customer-ready release notes grouped into New, Improved and Fixed, with internal-only changes removed and listed.