# Stakeholder Communication — Exercises

## Exercise 1: Pyramid Principle Rewrite

**Task:** Take this status: "We've been working on the integration. There were some issues. We're fixing them. We might be a week late." Rewrite it using the pyramid principle. Lead with the conclusion. Max 3 sentences.

**Validation:**
- [ ] First sentence is the takeaway (delay + cause or implication)
- [ ] Supporting detail follows
- [ ] Total ≤ 3 sentences
- [ ] Reader gets the point from line 1

**Hints:**
1. Lead: "We're at risk of slipping by one week due to integration issues."
2. Support: "We've identified and are addressing 3 blockers."
3. Optional: "Next update in 48 hours."

---

## Exercise 2: RAG Assignment

**Task:** Assign RAG to these: (A) On track, demo next week. (B) Key vendor delayed; we have a fallback. (C) Major bug in prod; fix in progress. (D) Scope increased 30%; no timeline change. For each, write one sentence you'd include in a status.

**Validation:**
- [ ] A = Green, B = Amber, C = Red or Amber, D = Amber or Red
- [ ] Each has a status-appropriate sentence
- [ ] No alarmist language for B; no understatement for C

**Hints:**
1. A: Green—"On track for demo next week."
2. B: Amber—"Vendor delay; fallback plan in place; monitoring."
3. C: Red or Amber—"Critical bug; fix deployed in 4h; root cause analysis underway."
4. D: Amber—"Scope +30%; reviewing timeline and resources."

---

## Exercise 3: Stakeholder Map

**Task:** For a "password reset" feature: list 4 stakeholders (e.g., Exec, Eng Lead, Support, Security). Plot on power/interest. For the highest-power, highest-interest one: what do they need in a status update?

**Validation:**
- [ ] 4 stakeholders named
- [ ] Plotted on grid
- [ ] "Manage closely" needs described
- [ ] Needs are specific (not "they need updates")

**Hints:**
1. Exec: outcomes, timeline, risks, decisions
2. Eng Lead: technical blockers, dependencies
3. Support: when it ships, what changes for users
4. Security: compliance, audit trail

---

## Exercise 4: Delay Communication

**Task:** Your "Search v2" release is slipping 2 weeks. Cause: performance issues under load. Write a 5-sentence message to the Product VP. Include: delay, cause, impact, plan, ask.

**Validation:**
- [ ] Delay and new date stated up front
- [ ] Cause is clear
- [ ] Impact (what it means) stated
- [ ] Plan (what you're doing) included
- [ ] Ask or next step present

**Hints:**
1. "Search v2 delayed 2 weeks. New target: [date]."
2. "Cause: performance issues under load in testing."
3. "Impact: Q2 demo still feasible; later phases unchanged."
4. "Plan: perf sprint this week; load tests in CI."
5. "Ask: Confirm scope for v2 by Friday."

---

## Exercise 5: Two-Version Status

**Task:** Write one status for a "Payment integration" project. Create (1) Exec summary: 4 bullets, pyramid. (2) Eng Lead version: same content + technical blockers, dependencies, and decisions needed.

**Validation:**
- [ ] Exec: ≤ 4 bullets, outcome-focused
- [ ] Eng: includes technical detail
- [ ] Both share the same RAG and core facts
- [ ] Eng version is longer but still scannable

**Hints:**
1. Exec: RAG, TL;DR, key milestone, top risk
2. Eng: + Stripe API version, test env blocker, auth handoff decision