loading words...

Jul 26, 2019 12:58:39

Release notes question

by @hum | 246 words | 🐣 | 215💌

Sarah Hum

Current day streak: 0🐣
Total posts: 215💌
Total words: 107318 (429 pages 📄)

Continuing to answer Quora questions to do my 200WaD while marketing Canny.

Here's my answer to: Should SaaS vendors provide detailed release notes whenever they make changes to their product?

If you're on Quora, your upvote would help my answers get seen. Thanks in advance!


---

First, I don't think all changes require detailed release notes. For example, minor changes like bug fixes. Following up with people who reported the bug is perfect.

However, there are several benefits to providing release notes for more major changes:

Keep customers in the loop

The most obvious reason is keeping your customers updated. Engagement with new features is a process. The bare minimum thing you should do is tell people about the new changes and why they're awesome. Publishing your release notes is huge for increasing feature awareness and adoption. 

Keep your team in the loop

If you have a large team, it's hard to keep everyone updated on product changes. 

It's especially important for customer-facing teammates to be up to date. Your release notes can be your single source of truth for product changes.

Attract new customers

If your release notes are public, they're a great motivator for potential customers. People want to see that you're actively improving your product. 

With Canny, you can communicate your latest changes with the Canny Changelog. Bonus points if you share work in progress with a public roadmap. Hope this helps!

Originally published at www.quora.com

From Sarah Hum's collection:

contact: email - twitter / Terms / Privacy