stakeholder-communicationlisted

# Stakeholder Communication Get the right information to the right people at the right time, in a form they can act on. Stack-agnostic. Applies to any team operating with cross-functional stakeholders. --- ## When to use - Writing weekly or monthly status updates - Preparing for an executive review or board update - Sharing a technical decision with a non-technical audience - Communicating a delay, miss, or quality problem - Asking for help, resources, or decisions - Managing up to a manager or sponsor - Designing the communication cadence for a project - Drafting an internal announcement ## When NOT to use - Customer-facing communication (use marketing/support skills) - Public comms or press (different framework, different stakes) - Incident communication during an active incident (use `incident-response`) - Internal documentation that isn't time-sensitive (use `documentation-strategy`) - Specific delivery formats (slide deck design, email tone) - this skill is about content and structure --- ## Required inputs - The audience (who specifically, what's their context, what do they care about) - The purpose (inform, decide, escalate, ask, celebrate) - The substance (what's actually happening) - The medium (email, doc, meeting, slide, chat) - Time constraints (when do they need this) --- ## The framework: 5 questions Before any stakeholder communication, answer: ### Question 1: Who is the audience? Specifically. "Leadership" is too vague. The CFO and the VP of Engi