How to collect feature requests without losing the conversation

1. Capture the problem, not just the proposed feature

Early feedback arrives in support tickets, demos, messages and conversations. Ask what the user was trying to accomplish, what failed and how they work around it today. Keep private details in your support system. Put a short, non-sensitive problem statement on the board only when public discussion is appropriate.

2. Introduce a board when repeated requests become hard to track

Email is good for context; chat is good for conversation. Neither naturally maintains a canonical request and a visible decision. Add a board when you repeatedly search old threads or write the same status answer. Link people to the existing idea, but do not make them re-enter everything they already told you.

3. Merge duplicates and invite votes

Look for the underlying problem before merging: two requests that mention exports might need different outcomes. Consolidate genuine duplicates and invite users to vote on the shared request. Keep meaningful context. Do not use a vote count as a substitute for customer interviews, severity or strategic judgment.

4. Review a small queue consistently

A workable weekly routine is to review new submissions, ask one clarifying question where needed, group duplicates and identify the next decision. Review-before-publication is useful when privacy or spam is a concern. Publish automatically only if you can respond to issues promptly.

• Record the problem and an example of the desired outcome.
• Separate bugs from enhancement requests without dismissing either.
• Consider impact, reach, confidence and implementation cost.
• Assign a status only when it communicates something real.

5. Close the loop without promising every request

Reply with what you learned, explain why a request is planned or deferred, and update its status when work changes. In Simple Feature Board, request threads and the roadmap make that progress visible. There are no automatic status emails today: use your own customer communication channel for proactive announcements.

Keep one-on-one research

A board collects volunteered feedback from people motivated to participate. It does not reveal every silent user’s needs. Continue interviews and usability checks, especially before expensive decisions. Measure whether your process produces clearer decisions and fewer lost conversations, not just a bigger backlog.