Define “closed” operationally
A request is not closed when eng merges a PR. It is closed when the roadmap says Shipped, the changelog is public, and voters were notified.
The closed-loop stages
Treat each stage as a checklist item owned by PM or the releasing engineer — not a nice-to-have.
| Stage | Owner | Customer-visible output |
|---|---|---|
| Collect + merge | PM / CS | Canonical post with votes |
| Prioritize | PM | Planned on public roadmap |
| Build | Eng | In progress status |
| Announce | PM / marketing | Changelog entry |
| Notify | Automation | Email to voters / followers |
Write the changelog from the request
Reuse the problem statement customers wrote. Benefit-led titles beat internal epic names. Link back to the original feedback post when useful.
Automate voter notification
Manual BCC lists do not scale. Use a tool that ties the feedback post to the changelog and emails followers when status hits Done.
Decline with the same respect
Closing the loop includes “no.” A short public decline reason keeps trust and stops zombie upvotes on ideas you will not build.
Ready to put this into practice?
Close the loop on Upwip