Most release notes are written for the people who shipped the release. They list tickets, mention internals and lean heavily on the passive voice. A customer opening them is looking for one thing: what does this mean for me?
Five rules we follow
- Lead with the benefit. You can now export any report as CSV, not Added CSV export endpoint.
- Write for one person. Imagine the customer who asked for it, and tell them it's done.
- Show, don't describe. A ten-second screen capture beats a paragraph.
- Say what changed, not what you did. Nobody cares that you refactored the settings page.
- Be plain about breaking changes. Put them at the top, with a date and a link to help.

The test
Before publishing, read each line aloud and ask: would someone who has never heard of this feature understand why it matters? If not, rewrite it or cut it.



