The customer feedback loop consists of many moving parts. You collect feedback, discuss, prioritize, and arrange it all into a roadmap.
The feedback cycle should always end with communicating what’s finished. Brownie points for also explaining where to find it, and how to use it.
Plus, new features deserve more celebration than throwing them in the “complete” column in your roadmap.
You’ve spent weeks, months, or even years building something. Announcing it should be fun and exciting. This is where Canny Changelog comes in.
We built it to close the feedback loop, notify customers about changes, and encourage engagement. All in one place!
Why do you need a Changelog?
You might be thinking that if you have a public roadmap, why do you need Changelog?
There are a few big benefits to having a one.
Keep existing customers in the loop
Not everyone is constantly keeping an eye on what you’re up to. This means that many customers might be missing out on awesome new features.
Some products are easy to get used to and not engage with anymore. The comfort zone is real.
One of the main benefits of Changelog is increasing new feature awareness and adoption.
By communicating new features, you’ll encourage your customers (old and new) to come back and play.
They might even find completely new use cases and things they can do to increase your value with them.
There’s also the aspect of not leaving people hanging. Customers who have requested features will be notified when you move a project status to “complete”.
From there, they can head straight to Changelog to check out the details.
Keep your team in the loop
Changelog isn’t only for your customers. It’s also an amazing asset to have for internal purposes. We’ve talked about how having cross-team access to the product roadmap increases productivity.
Using your Changelog internally is no different. Having one official place for new features helps non-product teams stay in sync.
They’ll be able to and organize their work without constantly asking about updates.
Ease of communication
If you don’t have an official Changelog, communicating changes to customers can be a hassle.
If you don’t have a centralized place for your releases, you have to use many channels to make sure everyone is notified.
With one, official, consolidated place for updates, all of this goes away. There’s no wondering which channels to use—updates can be shared anywhere via your Changelog.
An official changelog is easy for support, marketing, and anyone else to just link to when needed. The interface is easy to use for anyone regardless of whether they’re a developer or not.
Attracting potential customers
The Changelog isn’t only for existing customers. If you have a public Changelog, you can also use it for low-key marketing efforts.
Which customer wouldn’t like a company that actively builds what their users want?
By communicating your progress to the world, potential customers will also see it. If they’re doing research about which solution to pick, your transparency and velocity will stand out.
- Learn more about our Changelog feature
- Check out our own Changelog
- Have a peek at our Changelog entry about the Changelog (hehe)
- Read the help article about Changelog
- Contact us with any questions or concerns
Ready to announce your feature launches?