Why You Should Publish Release Notes

I don't always write release notes, but, when I do, they're generally for internal consumption. Not so at S!zzle. Setting a precedent early of publishing the release notes to our blog has added responsibility, but also kept me focused. We do weekly releases, so when I start every week I always have to think "What benefit will the customer see?" before prioritizing tasks for completion.

As developers we do many things behind the scenes that (hopefully) have a positive effect on customer experience. Sometimes, however, one can get too focused on pleasing those internal folks who need a new report or a better interface for monitoring customers. Having a raw interaction with customers can provide that genuine feedback loop to keep our priorities in line with their needs. After all, what is the purpose of business if not to serve customers?

This week I got an ego boost. One of our new signups mentioned reading the release notes to sales. While most of your customers aren't going to read them, knowing that they're there adds a level of transparency that inspires trust. Building a relationship with customers, like building any relationship, requires trust. At S!zzle we provide context and presentation for recruiters reaching out to potential candidates for the jobs they are trying to fill. We are literally responsible for making that first impression awesome, and recruiters don't bestow that trust on us lightly.