Not every team reads your updates. But when they do, they should actually know what’s going on—not feel like they’re squinting at a changelog crossed with a therapy session.
That’s what this template is for. It’s short, structured, and easy to send—whether you’re updating execs, cross-functional teams, or just keeping Slack quiet with something substantive.
Because when your updates are clear, people stop asking for meetings.
What this template helps you do
- Communicate progress without writing a novel
- Show momentum, blockers, and what’s next—all in one scroll
- Build trust (and reduce check-ins) with async updates
- Make your team’s work legible to the rest of the company
You don’t need fancy formatting or internal comms training. You just need a structure that keeps you honest and your stakeholders informed.
The template
Subject: Product Update – Week of [Date]
or if you’re feeling punchy:
🚀 Week [#] Update: Shipping, Blocking, Planning
What we shipped
- [Feature] is now live for [user group]
- [Fix] went out Monday—early feedback looks positive
- Cleaned up [X] flow based on feedback from [CS/Sales/etc.]
What we’re working on
- [Feature or initiative] in QA, expected to go live [day]
- Still iterating on [part]—ran into [brief reason, if useful]
- [Bug or refactor] in progress to support [upcoming work]
What’s next
- Planning kickoff for [next feature/project]
- Team is syncing with [Design/Marketing/etc.] on [cross-functional thing]
- Lining up interviews for [user research / validation]
Blockers or calls for input
- Waiting on [X] to move forward with [Y]
- Feedback needed from [stakeholder or team] on [Z]
- Let me know if [open question] is still a priority—we may need to push
Quick win of the week
[Optional: Celebrate something that worked, landed, or surprised you in a good way.]
That’s it for now—DM or reply if anything’s unclear.
—[Your name]
When to send it
Fridays work well for most teams. Mondays are fine too, but risk getting buried. Whatever rhythm you pick, stick with it—consistency earns trust, even if the update is brief.
If you’re managing multiple squads or a larger roadmap, consider splitting updates by theme or audience. Or keep one update, but flag relevant sections clearly.
Tips from teams that get replies
- Start with outcomes, not activity. “Shipped” > “Worked on.”
- Cut the filler. “We’re excited to share…” is just noise.
- Be honest about blockers. People respect clarity.
- Use plain language. If it sounds like a tweetstorm, it’s probably too clever.
- Show momentum, even when slow. Even a pause is progress if you explain why.
When this update becomes your “source of truth”
Pin it in Slack.
Link to it in your roadmap.
Forward it to execs before they ask.
Make it the thing people know to check before they tap you on the shoulder.
Because once your comms are reliable, your team can be heads-down—and everyone else still feels looped in.