Blog
Guides for software teams on hearing what users ask for, deciding what to build and telling people when it ships. Facts about other products and standards link to their sources.
UpVoiced is in development and not open for sign-ups yet. Subscribe withthe RSS feed.
Product feedback: how to collect it, sort it and act on it
Product feedback arrives through support, sales, email and your app. This guide shows how to bring it into one place, turn requests into problems you can solve, decide on a rhythm and tell people what happened.
How to close the customer feedback loop, step by step
A feedback loop is only closed when the person who asked hears what happened. Here is the loop step by step, who to tell at each status change, what to write and how to email people without annoying them.
How to write release notes people read (with a template)
Good release notes tell users what changed for them, not what changed in the code. This guide covers what to include, how to group changes, where notes are published and their limits, with a template you can copy.
How to manage feature requests: a process and a template
Feature requests are useful when they describe a problem and land in one place. This guide gives you a request template, a triage routine, the statuses to use and wording for "not now" and "no".
Public roadmap tool: what to show, what to hide, how to run it
A public roadmap answers "is this coming?" before anyone asks, if it stays honest. Here is what to publish, what to leave out, how GitHub runs its own public roadmap and a checklist for choosing a tool.
Changelog tool checklist: what it should do for you
A changelog file in your repository is enough for some products. When your users are not developers, a changelog tool should also tell the right people. Here is a checklist and how three feedback tools package their changelogs.