The skill: Two related artifacts. Internal updates keep leadership and cross-functional teams aligned on what shipped, what's blocked, and what changed. External release notes communicate value to users and drive adoption. Both require leading with outcomes, not output.
Internal updates that actually get read
Use this format. One screen, scannable in 60 seconds:
- Shipped — what moved this week
- Metrics moved — what changed because of it
- Blocked — what needs help (flag this Monday, not Friday — a blocker surfaced on Monday saves the week, one mentioned Friday wastes it)
- Next week — what's coming
Apply the "so what" test to every line. "Shipped new API endpoint" fails. "Teams can now sync data in real-time, reducing manual exports by ~2 hours/week" passes. If the "so what" isn't obvious, rewrite it until it is.
Cadence matters more than polish. A consistent weekly update builds trust. A beautifully designed monthly update gets ignored because people stop expecting it.
Release notes that drive adoption
Lead with what the user can now do, not what you built:
- Headline benefit — not the feature name. "Share reports with your team in one click," not "New sharing permissions system."
- What changed — brief, specific
- How to use it — the exact steps
- What's next — builds anticipation
Screenshots and GIFs beat paragraphs. A 5-second GIF showing the new flow communicates more than 200 words describing it. Show the thing.
One CTA per release note. Don't overwhelm users with five things to try. Pick the one action that delivers the most value and make it the obvious next step.
Templates
Do's and Don'ts
Written with ❤️ by a human (still)