How to prioritize feature requests
A practical way to decide which feature requests to build: group by need, count who asks, weigh effort, and tell people what you decided.
Short answer: group requests by need, then score each need on how many people ask, how much those people matter to you, and how much work it is. Build the needs with the most demand for the least effort, and tell the people who asked.
A simple scoring method
| Question | Score 1 to 3 |
|---|---|
| How many people asked? | 1 = a few, 3 = many |
| Are they the customers you want more of? | 1 = rarely, 3 = mostly |
| Does it stop people from doing their main task? | 1 = nice to have, 3 = blocking |
| How much work is it? | 1 = large, 3 = small |
Add the scores and start from the top. Revisit monthly as new requests arrive.
Mistakes to avoid
- Counting raw votes: a public board over-represents your loudest users.
- Losing context: a request without the screen it came from is hard to judge.
- Silence: people who never hear back stop asking.
How Bopmigo helps
Requests arrive from inside your product with the screen they came from. Related requests are grouped, so the count is in front of you. Mark them in progress or resolved, and reply to tell people it shipped.
