Skip to main content

Feature Prioritization: How to Ask Users What They Actually Want

Asking users which features to build gets you a wish list, not a roadmap. Here are better ways to prioritize.

"What features do you want?" feels like the obvious question to ask your users. It's also one of the least useful. People happily tick every box, nobody has to make a trade-off, and you end up with a wish list where everything is a top priority.

Here are four better ways to find out what to build next.


Why “what feature do you want?” fails

Wanting something costs nothing, so a direct feature question gives you no signal about priority. Worse, users tend to propose solutions rather than describe their actual problem.

Two reasons the direct feature question fails: everyone says yes to everything, and users design solutions badly



Ask about problems, not features

Shift the question from the solution to the problem. Instead of asking which feature to build, ask what's getting in their way. You'll uncover the real need — and often a better solution than the one they'd have requested.

Don't ask which feature to build; ask what slows you down most today



Importance × satisfaction: the gap map

For each item, ask two questions: how important is it, and how satisfied are you with it today? Plot the two and a clear picture appears. The corner that's high-importance but low-satisfaction is your roadmap — that's where users hurt and you're not delivering yet.

Don't pour effort into things people already love, or things they don't care about. Build where the gap between importance and satisfaction is widest.


An importance versus satisfaction quadrant with the high-importance, low-satisfaction corner marked fix first



Kano, in plain English

The Kano model sorts features into three useful buckets. It stops you from polishing delighters while a must-have is still broken.

Kano categories in plain English: must-haves, performance features, and delighters



Ranking forces the trade-off

When you do ask directly, don't use checkboxes — use a ranking question. Making people drag options into order forces the very trade-off a checkbox lets them dodge, so you learn what they'd give up.


A ranking question where users drag product improvements into their order of priority



Combine it with usage data

Surveys tell you what people say; your product analytics tell you what they do. Prioritize where the two agree — a highly-wanted, high-gap feature that also shows up in usage data is a safe bet. Where they disagree, dig deeper before you build.



Where to start

  1. Replace “which feature?” with a problem question.

  2. Run an importance × satisfaction survey and map the gaps.

  3. Use ranking, not checkboxes, when you ask directly.

  4. Cross-check the top candidates against your usage data.


💡 A quick start

Survio's ranking and rating questions make the gap map and prioritization surveys quick to build. Pair this with "How to Run Usability Testing Surveys" in this collection.

Did this answer your question?