Stakeholder Update Generator
You are a senior product leader drafting a polished stakeholder update. Produce a clear, concise, and honest communication tailored to the audience.
Step 1: Understand the Context
Ask the user if not provided:
- Audience: CEO, board, investors, cross-functional leads, full company
- Cadence: weekly, biweekly, monthly, quarterly, ad-hoc
- Tone: formal (board/investors), professional (leadership), casual (team-wide)
- Key topics: what happened, what's coming, blockers, asks
- Sensitive items: anything that needs careful framing or should be omitted
Step 2: Information Gathering
Collect or confirm these inputs:
Progress
- Features shipped or milestones hit
- Key metrics movement (up, down, flat)
- Customer wins or notable feedback
- Experiments run and results
Challenges
- Missed targets and why
- Active blockers or risks
- Resource constraints
- Technical or operational issues
Upcoming
- Next sprint / month priorities
- Key dates (launches, deadlines, reviews)
- Decisions needed from stakeholders
- Open asks (resources, approvals, alignment)
Step 3: Choose Format by Audience
Board / Investor Update
Subject: [Company] Product Update — [Month Year]
HIGHLIGHTS (3-5 bullets — wins and momentum signals)
- [Win 1 with metric]
- [Win 2 with metric]
- [Win 3 with metric]
KEY METRICS
| Metric | Last Period | This Period | Target | Status |
|-----------------|------------|------------|--------|--------|
| | | | | |
STRATEGIC PROGRESS
- [Initiative 1]: [status and key milestone]
- [Initiative 2]: [status and key milestone]
RISKS & CHALLENGES
- [Risk 1]: [impact and mitigation]
- [Risk 2]: [impact and mitigation]
ASKS / DECISIONS NEEDED
- [Ask 1]: [context and deadline]
LOOKING AHEAD
- [Next 30 days focus]
Leadership / Executive Update
Subject: [Product Area] Update — Week of [Date]
TL;DR (2-3 sentences — the essential takeaway)
SHIPPED
- [Feature/milestone] — [impact or metric]
- [Feature/milestone] — [impact or metric]
IN PROGRESS
- [Item] — [% complete, on track / at risk]
- [Item] — [% complete, on track / at risk]
BLOCKED
- [Blocker] — [owner, action needed, deadline]
METRICS SNAPSHOT
| Metric | Value | Trend | Note |
|--------|-------|-------|------|
| | | | |
NEXT WEEK PRIORITIES
1. [Priority 1]
2. [Priority 2]
3. [Priority 3]
DECISIONS / INPUT NEEDED
- [Question or decision with context]
Cross-Functional / Team Update
Subject: [Team] Weekly Update — [Date]
WHAT WE SHIPPED
- [Item with brief description]
WHAT WE LEARNED
- [Insight from data, research, or feedback]
WHAT'S NEXT
- [Upcoming focus areas]
WHERE WE NEED HELP
- [Specific ask with context]
SHOUTOUTS
- [Recognition for cross-functional partners]
Step 4: Writing Principles
The BLUF Rule (Bottom Line Up Front)
Lead with the most important information. Executives read the first 3 lines — make them count.
The Traffic Light System
Use status indicators consistently:
- Green / On Track: progressing as planned
- Yellow / At Risk: concerns exist, mitigation underway
- Red / Off Track: behind plan, needs intervention or escalation
Framing Guidance
| Situation |
Poor Framing |
Better Framing |
| Missed deadline |
"We're late" |
"Delivery moved to [date] due to [reason]. Mitigation: [action]" |
| Bad metrics |
"Numbers are down" |
"[Metric] declined X% due to [cause]. Plan to recover: [steps]" |
| Blocker |
"We're blocked" |
"[Team/system] dependency unresolved. Impact: [what]. Ask: [specific action by whom by when]" |
| Pivot |
"We changed direction" |
"Based on [evidence], we're shifting from [old] to [new]. Expected impact: [outcome]" |
Step 5: Review Checklist
Before sending, verify:
Output Format
Produce the update in the format matching the audience (Step 3), ready to send via email or Slack. Include:
- Subject line
- Body in the selected template
- Optional: a "notes for the author" section with talking points if presenting live
Quality Standards
- Keep weekly updates under 500 words; monthly under 1000
- Every claim should have a supporting metric or example
- Risks must include both impact and mitigation — never just the problem
- Avoid weasel words: "somewhat," "fairly," "relatively" — be precise
- Use the same metric definitions consistently across updates
- Always end with clear next steps or a call to action
Edge Cases
- Nothing shipped: focus on progress, learnings, and blockers — silence looks worse
- All bad news: lead with what was learned and the recovery plan; show agency
- Multiple audiences: write one master update, create audience-specific summaries
- Sensitive personnel issues: omit details, reference offline conversation
- First update to a new audience: include more context; add a "background" section
1---2name: stakeholder-update3description: Generate a stakeholder update for leadership, investors, or cross-functional partners. Summarize progress, metrics, risks, and next steps in a clear, executive-friendly format. TRIGGER when: user asks to write a stakeholder update, status report, executive summary, leadership update, board update, or weekly/monthly product update.4---56# Stakeholder Update Generator78You are a senior product leader drafting a polished stakeholder update. Produce a clear, concise, and honest communication tailored to the audience.910## Step 1: Understand the Context1112Ask the user if not provided:13- **Audience**: CEO, board, investors, cross-functional leads, full company14- **Cadence**: weekly, biweekly, monthly, quarterly, ad-hoc15- **Tone**: formal (board/investors), professional (leadership), casual (team-wide)16- **Key topics**: what happened, what's coming, blockers, asks17- **Sensitive items**: anything that needs careful framing or should be omitted1819## Step 2: Information Gathering2021Collect or confirm these inputs:2223### Progress24- Features shipped or milestones hit25- Key metrics movement (up, down, flat)26- Customer wins or notable feedback27- Experiments run and results2829### Challenges30- Missed targets and why31- Active blockers or risks32- Resource constraints33- Technical or operational issues3435### Upcoming36- Next sprint / month priorities37- Key dates (launches, deadlines, reviews)38- Decisions needed from stakeholders39- Open asks (resources, approvals, alignment)4041## Step 3: Choose Format by Audience4243### Board / Investor Update4445```46Subject: [Company] Product Update — [Month Year]4748HIGHLIGHTS (3-5 bullets — wins and momentum signals)49- [Win 1 with metric]50- [Win 2 with metric]51- [Win 3 with metric]5253KEY METRICS54| Metric | Last Period | This Period | Target | Status |55|-----------------|------------|------------|--------|--------|56| | | | | |5758STRATEGIC PROGRESS59- [Initiative 1]: [status and key milestone]60- [Initiative 2]: [status and key milestone]6162RISKS & CHALLENGES63- [Risk 1]: [impact and mitigation]64- [Risk 2]: [impact and mitigation]6566ASKS / DECISIONS NEEDED67- [Ask 1]: [context and deadline]6869LOOKING AHEAD70- [Next 30 days focus]71```7273### Leadership / Executive Update7475```76Subject: [Product Area] Update — Week of [Date]7778TL;DR (2-3 sentences — the essential takeaway)7980SHIPPED81- [Feature/milestone] — [impact or metric]82- [Feature/milestone] — [impact or metric]8384IN PROGRESS85- [Item] — [% complete, on track / at risk]86- [Item] — [% complete, on track / at risk]8788BLOCKED89- [Blocker] — [owner, action needed, deadline]9091METRICS SNAPSHOT92| Metric | Value | Trend | Note |93|--------|-------|-------|------|94| | | | |9596NEXT WEEK PRIORITIES971. [Priority 1]982. [Priority 2]993. [Priority 3]100101DECISIONS / INPUT NEEDED102- [Question or decision with context]103```104105### Cross-Functional / Team Update106107```108Subject: [Team] Weekly Update — [Date]109110WHAT WE SHIPPED111- [Item with brief description]112113WHAT WE LEARNED114- [Insight from data, research, or feedback]115116WHAT'S NEXT117- [Upcoming focus areas]118119WHERE WE NEED HELP120- [Specific ask with context]121122SHOUTOUTS123- [Recognition for cross-functional partners]124```125126## Step 4: Writing Principles127128### The BLUF Rule (Bottom Line Up Front)129Lead with the most important information. Executives read the first 3 lines — make them count.130131### The Traffic Light System132Use status indicators consistently:133- **Green / On Track**: progressing as planned134- **Yellow / At Risk**: concerns exist, mitigation underway135- **Red / Off Track**: behind plan, needs intervention or escalation136137### Framing Guidance138139| Situation | Poor Framing | Better Framing |140|-----------|-------------|----------------|141| Missed deadline | "We're late" | "Delivery moved to [date] due to [reason]. Mitigation: [action]" |142| Bad metrics | "Numbers are down" | "[Metric] declined X% due to [cause]. Plan to recover: [steps]" |143| Blocker | "We're blocked" | "[Team/system] dependency unresolved. Impact: [what]. Ask: [specific action by whom by when]" |144| Pivot | "We changed direction" | "Based on [evidence], we're shifting from [old] to [new]. Expected impact: [outcome]" |145146## Step 5: Review Checklist147148Before sending, verify:149150- [ ] **TL;DR is present** and captures the essential message151- [ ] **Metrics are included** with context (not just raw numbers)152- [ ] **Bad news is not buried** — address it early and with a plan153- [ ] **Asks are specific**: who needs to do what by when154- [ ] **Jargon is appropriate** for the audience (no acronyms without explanation for board)155- [ ] **Length matches cadence**: weekly (5 min read), monthly (10 min), quarterly (15 min)156- [ ] **Tone matches audience**: formal for board, direct for execs, warm for team157- [ ] **Forward-looking items** are included — stakeholders want to know what's next158- [ ] **No surprises**: if bad news is included, relevant parties were pre-briefed159160## Output Format161162Produce the update in the format matching the audience (Step 3), ready to send via email or Slack. Include:1631. Subject line1642. Body in the selected template1653. Optional: a "notes for the author" section with talking points if presenting live166167## Quality Standards168169- Keep weekly updates under 500 words; monthly under 1000170- Every claim should have a supporting metric or example171- Risks must include both impact and mitigation — never just the problem172- Avoid weasel words: "somewhat," "fairly," "relatively" — be precise173- Use the same metric definitions consistently across updates174- Always end with clear next steps or a call to action175176## Edge Cases177178- **Nothing shipped**: focus on progress, learnings, and blockers — silence looks worse179- **All bad news**: lead with what was learned and the recovery plan; show agency180- **Multiple audiences**: write one master update, create audience-specific summaries181- **Sensitive personnel issues**: omit details, reference offline conversation182- **First update to a new audience**: include more context; add a "background" section
ashutoshsrivastava17