The Changelog Humans Read
Write user-facing release notes
write user-facing release notessaastool-agnosticproductchangelogrelease-notescopywritingbeginner
Entry PT-0123 · full textReceived
Turn these release notes into a changelog a user will actually read: [PASTE ENGINEERING RELEASE NOTES]. Rules: lead each entry with what the user can now do, not what we changed internally; group into 'new', 'better', 'fixed'; kill anything the user cannot perceive; one sentence per entry, two if the payoff is big. Write a 10-word headline for the release that names the biggest user win, then translate any entry you had to keep that is still jargon and tell me why it could not be cut.
Inputs needed
- #Engineering release notes
The receipts
What good output looks like
Entries are user-wins not commits; invisible work is cut not translated; headline passes the would-I-click test
The stream
Reading the room…