Capture the problem behind the requested solution
“Add Excel export” is a proposed solution. Ask what the customer needs to do, how they do it today and what stops them. Different requests may describe the same reporting problem, while two identical titles may solve very different needs.
Keep the original request and its context. A useful entry includes the affected workflow, the desired result and a concrete example. Do not publish private account details or internal conversations on the public board.
Request: export to Excel Problem: finance teams need to combine a monthly report with their own workbook. Current workaround: copying rows by hand. Desired result: download the report as an .xlsx file.
Group related requests without losing their supporters
Before creating a roadmap item, look for an existing request that covers the same problem. Keep one clear entry and preserve the people who expressed interest. A duplicate count is useful context; it is not a separate commitment for every wording variation.
Votes are one input to prioritisation. Combine them with the affected workflow, strategic fit, support burden and the effort to make a reliable change. A popular idea can still need clarification before it is ready for a plan.
Give each status a plain meaning
A public roadmap helps customers understand what is being considered and what is moving. Canny’s documented public roadmap presents status columns and updates a post’s placement when its status changes; customisation depends on the plan.
For your own roadmap, write a short definition for every status. “Under review” means consideration; “planned” means selected work; “in progress” means active delivery. Avoid dates until you have a reason to stand behind them.
- Under review: the problem is being assessed.
- Planned: the team has chosen the work.
- In progress: the team is actively building it.
- Shipped: customers can use the change.
Explain status changes and notify the people who asked
A changed badge is easy to miss. Add a short reason for a meaningful move, and tell interested users what changed. Canny documents status notifications and an option to email users when an idea’s status changes; those settings and workflows should be checked for the account in use.
When work ships, link to instructions or release notes. Say where the new capability lives and whether customers need to enable it. This closes the feedback loop with something they can act on.
Shipped: Excel export You can now download any report as an Excel file from the Export menu. Thanks to everyone who shared how they use these reports.
Let the roadmap keep itself current
The hard part is not the first roadmap, it is keeping it true. Statuses drift, duplicates pile up and voters never hear back.
Lodariq groups similar requests, counts votes, follows the status from Linear or Jira, and tells every voter the moment it ships.