Product15 April 2026 · 4 min read
A changelog customers actually read
Release notes are marketing, documentation and support in one page. Here is how we write ours, and how the public changelog feature came out of it.
HIHana Ito
Our own changelog started as a Notion page. It was updated when someone remembered, in whatever voice that person had, and customers found out about features from support tickets months later.
The fix was to write the note when the work was finished, not when the release went out. In Cairn every item has a customer-facing note field, filled in by the person who built it while the context is fresh. A release collects those notes. Publishing is one click, and the page has a subscribe button.
The unexpected benefit was internal. Writing the note forces the question of what the change means for someone using the product. Items that cannot be described that way tend to be items that should not have been built.
Keep reading
Give the plan somewhere to live.
Import your backlog from a CSV or your current tool, invite the team, and run the next cycle in Cairn. Free for teams up to five.