How to Announce a New Feature (So People Actually Use It)
August 9, 2026
Most feature announcements are written from the builder's perspective: what changed, in the vocabulary of the team that changed it. They get opened, skimmed and forgotten.
Adoption is a separate project from shipping, and it usually gets a fraction of the effort despite deciding whether the work mattered.
Why release notes do not drive adoption
Release notes are a changelog, and a changelog is a reference document. People consult references when they already have a question.
A customer who does not know a capability exists has no question to bring. Announcements have to create the question, which is a different job from recording the answer.
Lead with the job, not the feature
"We added bulk actions" describes the implementation. "Archive a hundred records without clicking each one" describes what changes for them.
The test: could a customer read the first sentence and know whether it affects their week? If it needs a paragraph of setup, rewrite it.
Show it in three steps
A short demo embedded in the announcement dramatically outperforms describing it, and it is cheap because you already built the thing.
Three to five steps is enough. The goal is removing the imagination step -- "would this work for my situation" is much easier to answer when you can see it.
Announce more than once
One email reaches whoever happened to be in their inbox that morning. That is a small share of the people who would use it.
Sequence it: an in-app notice for active users, an email for everyone, a mention in the next onboarding sequence, and a contextual prompt at the moment the feature would help. The last of these is by far the most effective and the most often skipped.
Measure adoption, not opens
- Percentage of eligible accounts that used it within 30 days -- the number that matters.
- Time from announcement to first use, which tells you whether the announcement or something else drove it.
- Repeat use. One-time use after an announcement is curiosity, not adoption.
- Open and click rates are inputs, not outcomes. A 60% open rate with 2% adoption is a failed launch.
Frequently asked questions
- How do I announce a new feature to existing customers?
- Lead with the job it does rather than the feature name, show it in a three to five step demo instead of describing it, and announce more than once across in-app notices, email, onboarding and a contextual prompt at the moment the feature would help.
- Why do release notes not drive feature adoption?
- Release notes are a reference document, and people consult references when they already have a question. A customer who does not know the capability exists has no question to bring, so the announcement has to create the interest rather than record the change.
- How should I measure a feature launch?
- Measure the percentage of eligible accounts that used the feature within 30 days, time from announcement to first use, and whether use repeated. Open and click rates are inputs, not outcomes: a 60 percent open rate with 2 percent adoption is a failed launch.
Keep reading
This is what Demorta does
Click through it — the same kind of demo you can record of your own product.
Try it on your own product
Record your first interactive demo free.
Five demos on the free plan, forever. No credit card, no trial countdown, no sales call. Install the Chrome extension, click through your product once, and you have a shareable link in about ten minutes.
Start free →