# Stakeholder Communication

> Use when writing exec updates, status reports, or communicating product decisions to non-technical stakeholders

- Skill: `kienbui1995/stakeholder-communication` (Agent Skill)
- Install (CLI): `npx skillmds@latest add kienbui1995/stakeholder-communication`
- Raw SKILL.md: https://api.skillmd.com/api/skills/kienbui1995/stakeholder-communication/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: kienbui1995 (https://skillmd.com/u/kienbui1995)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/kienbui1995/stakeholder-communication

---


# Stakeholder Communication

## When to Use
When you need to inform, align, or get decisions from stakeholders who aren't in the day-to-day work.

## Core Jobs

### 1. Status Updates (Weekly/Bi-weekly)
Structure: BLUF (Bottom Line Up Front)
- **Status**: Green / Yellow / Red + one sentence why
- **This week**: 2–3 bullets of what shipped or progressed
- **Next week**: 2–3 bullets of what's planned
- **Blockers**: What you need from them (be explicit)
Keep it under 200 words. Executives skim.

### 2. Escalations
When to escalate: timeline risk, budget overrun, scope change, or dependency blocked.
Format:
- Situation: what happened
- Impact: what's at risk (timeline / revenue / quality)
- Options: 2–3 choices with trade-offs
- Recommendation: your preferred option with reasoning
- Decision needed by: [date]

### 3. Exec Presentations
- Slide 1: The ask (what decision do you need?)
- Slide 2: Context (why this matters now)
- Slide 3: Options considered
- Slide 4: Recommendation + metrics
- Appendix: Details for questions
Lead with the decision, not the story.

### 4. Product Decision Announcements
When changing direction or cutting scope:
- Acknowledge the change directly
- Explain what data/signals drove it
- State what stays the same
- Give teams time to adjust (avoid surprises)

## Key Outputs
- Weekly status update (BLUF format)
- Escalation memo
- Decision announcement

## Anti-Patterns
- Burying bad news in paragraph 3
- Sending updates without a clear ask
- Using jargon with non-technical stakeholders
- Over-communicating detail, under-communicating impact