Any phase · Ways of working
Send regular stakeholder updates
Short, regular updates keep stakeholders informed and save meetings. Tell them what changed, what is next and what you need.
About 30-60 minutesEvergreenLast reviewed 5 November 2026
Who this applies to
- Skills it builds
- Communication and influence
- PM types
- All
- Product types
- All
- Starting points
- All
- Ways of working
- All
- Experience
- All
- Size of organisation
- All
Steps, by experience
Beginner (under 1 year)
- Agree who gets updates and how often, for example every two weeks.
- Use the same short format each time: what we did, what we learned, what is next, what we need.
- Include one number that shows progress towards the outcome.
- Flag risks early, with what you are doing about them.
- Keep it short enough to read in two minutes.
Intermediate (1 to 4 years)
- Use a consistent, short format.
- Include outcomes and risks.
- Tailor for each audience.
Experienced (5+ years)
- Use updates to shape opinion before big decisions.
- Share learning and failures openly.
- Make updates self-service with live dashboards.
Who can do this
Owner: Product manager
Can be delegated to
- Delivery Manager or Scrum Master: Draft the update
- Content Designer: Edit for clarity
Reviewed by: Delivery Manager
Tool examples
- Confluence
- Use a blog post or page per update so there is a history.
- Notion
- Keep an update template and archive.
- Claude
- Paste your notes and ask for a two-minute update in your template, then edit it.
Definition of done
- Audience and rhythm agreed
- Consistent short format used
- Risks and needs flagged
Common pitfalls
- Long updates nobody reads
- Only good news
- Irregular updates