Product feedback
Decide what to build from what people actually asked for
You are deciding what to build next, from memory and a spreadsheet.
A board your customers post to, votes that mean something, a roadmap fed by the same items, and a changelog that tells the people who asked when it ships.
Today
You probably recognize at least two of these
Requests are scattered across everything
Some in email, some in chat, some in a spreadsheet someone started and abandoned. The loudest customer wins by default.
Nobody knows what is planned
The roadmap lives in your head, so the same question gets asked in every renewal call.
Shipping is silent
You build the thing they asked for and never tell them, so they never notice you listened.
What changes
01One board, with real voting
Customers post, others vote, duplicates collapse. A support conversation can become a request without retyping it.
02A roadmap fed by the same items
Public, on your domain, carrying the votes that got each item there, so the board and the plan cannot disagree.
03The people who asked get told
A changelog entry, drafted from the change that shipped, sent to the people who voted once a human approves it.
This is the same loop as the fix side, pointed at features instead of bugs.