AMAN · Guides · SaaS founders

How to write release notes people actually read

5 min readUpdated 30 October 2026

The short version

  • Write for the user's job, not the diff.
  • Three lines per change: what changed, why it matters, what to do.
  • Group by impact: act / know / ignore.
  • Link to the doc, not to the ticket.
  • Ship on a rhythm; empty weeks are fine.

Who is reading, and why

Two readers: the user who wants to know whether their workflow changed, and the evaluator who wants evidence the product is alive. Both want the same thing — what is different for me — in as few words as possible.

The three-line pattern

For each change: what changed (concretely, in their words), why it matters (the job it improves), what to do (nothing, or one action with a link). If you cannot fill the second line, the change is not worth announcing.

Group by impact

  • Act — something they must do, or will notice breaking.
  • Know — improves a workflow they already use.
  • Ignore — internal, or too small to matter. Most releases are mostly this; say so by omission.

Skip the changelog voice

‘Improved performance and bug fixes’ tells the user nothing and trains them to stop reading. ‘Exports now finish 4× faster on large accounts’ is the same fact, made useful. If the only honest note is ‘we fixed a bug’, say which bug and who it affected.

Cadence over volume

Monthly is enough for most B2B products, more often for collaborative tools. An empty month is not a failure; a padded one is. Keep the format identical so returning readers can skim.

Checklist

  • Each change has what/why/what-to-do
  • Grouped as act / know / ignore
  • No ‘various improvements’ entries
  • Docs linked, tickets not
  • Same format every time
  • Cadence published

If you would rather hand this over

AMAN's scribe (Katib) drafts release notes from your merged work and support themes, in your format and your voice, with the doc links attached. You edit and ship.

Questions people actually ask

Should release notes be public?

A public page is good for evaluators and SEO; email or in-app is better for existing users. Many teams do both from the same draft.

How do I write notes with no visible changes?

Say what was fixed and who it affected, or skip the month. Silence is more professional than filler.

Do release notes help retention?

Indirectly: they signal momentum and reduce surprise. Their main job is to prevent ‘I did not know it could do that’ churn.

Hand it a task. Consider it done.

AMAN is an AI worker for Muslim founders — research, listings, support, books and contracts, returned with evidence and never published without your approval.

Get early access