stakeholder-updatelisted

# Stakeholder Update A stakeholder update is not a list of everything you did. It's a deliberate act of communication: tell the right person the one thing they need to know, the decision you need from them, and how worried they should be. The fastest way to lose a stakeholder's trust is to make them dig for the status, bury a risk on line nine, or send an exec a wall of engineering detail. This skill turns raw progress into a clean update, sized and toned for whoever is reading it. **Grounded in:** *Working Backwards* — Bryar & Carr: the narrative memo: headline first, status, the ask. **Go deeper (The Product Channel):** [9 Ways to Influence Without Authority](https://sidsaladi.substack.com/p/week-12-9-ways-to-influence-people) ## When to use this - Recurring weekly or monthly status to leadership or a steering committee. - Announcing a launch, milestone, or GA to a broad internal or external audience. - Escalating a risk or blocker that needs a decision, resource, or unblock. - Re-cutting the same update for a different audience (exec vs. engineering vs. customer). - Translating a messy Slack thread or tracker dump into something a busy reader can scan in 20 seconds. ## Before you start (gather these) - **Audience** — exec / engineering / customer / cross-functional. This drives depth and jargon more than anything else. - **Cadence** — one-off announcement vs. recurring weekly/monthly (affects what "since last time" means). - **What happened since the last update** — sh