Quick answers
- What is a stakeholder update?
- A status report to leaders or other teams on progress, risks, and needs.
- What do you include in a stakeholder update?
- Status, key wins, risks/blockers, and clear asks.
- How do I deliver bad news in an update?
- Be direct: state the risk, cause, what you're doing, and what you need.
What it is
Stakeholder updates keep decision-makers informed. They're often written (email, Slack, doc) or delivered in a meeting. The format is usually: status, key wins, risks/blockers, and asks. Tone is concise and business-focused.
Why it matters
Stakeholders make resourcing and priority decisions. Clear updates build trust and get you support. Vague or overly technical updates can lead to misunderstanding or lack of support.
Instead of → Say
| Instead of | Say |
|---|---|
| We're making progress | We've completed 3 of 5 milestones. The API is done; we're in QA for the dashboard. |
| There might be a delay | We're at risk of slipping the March 15 deadline. The blocker is [X]. We need [Y] by Friday to stay on track. |
| Everything is fine | On track for launch. One risk: we're waiting on legal for the compliance review. I've escalated. |
| We need help | To hit the deadline, we need one more engineer for two weeks. Can we get support from [team]? |
| It's complicated | The short version: we're on track. The migration took longer than expected, but we've adjusted the timeline. |
Example dialogue
Stakeholder: Where are we on the launch?
You: We're 80% there. Backend and API are done. We're in final QA for the frontend. One risk: the compliance review is still pending. I've chased legal—we should have it by Thursday.
Stakeholder: What if we don't get it by then?
You: We'd need to slip the launch by a week. I'd recommend we keep the current date and reassess on Friday.
Stakeholder: Keep me posted.
You: I'll send an update by EOD Thursday.
Common mistakes
- Being too technical—stakeholders need outcomes, not implementation details
- Burying risks or bad news
- No clear ask—what do you need from them?
- Too long—busy people scan; lead with status and risks
- Overpromising to avoid conflict
Frequently asked questions
- How often should I update stakeholders?
- It depends on the project. Weekly is common. For critical projects, twice a week or more.
- How do I deliver bad news?
- Be direct: "We're at risk of [outcome] because of [reason]. Here's what we're doing. We need [ask]."
- What if they ask for more detail than I have?
- "I don't have that yet. I'll get back to you by [date]."
- Should I use bullet points or paragraphs?
- Bullet points are easier to scan. Lead with status, then wins, risks, and asks.
- How do I ask for help or resources?
- Be specific: "To hit [deadline], we need [resource] for [duration]. Can we get support from [team]?"
Ready to practice?
Start practicing with our available scenarios and get instant feedback.
Start practicing