Using Sequence Flow for Feature Prioritization and Roadmap Research¶

Ask customers to rate the importance of twelve candidate features on a 1-to-5 scale, and you'll reliably get back twelve scores clustered somewhere between 3.5 and 4.5. It's not that anyone's being dishonest - rating something "important" costs nothing, so almost everything ends up rated as at least somewhat important. Bring that data into a planning meeting and it tells you almost nothing about which three features to actually build this quarter.

A roadmap decision is a forced tradeoff by nature - you can only build so much - and the research behind it should force the same tradeoff, not dodge it with a scale where everything wins.

Why Sequence Flow Fits This Better Than a Rating Scale¶

Sequence Flow doesn't let a respondent rate every feature highly; it makes them place each one in a specific position relative to every other feature they were offered. That's a materially harder, more honest task than independent scoring, and it's the same underlying logic behind forced-choice methods generally - our MaxDiff and TURF guide covers a closely related approach if you're choosing between a ranked sequence and a best/worst format for a similar decision.

Setting It Up for a Roadmap Decision¶

Use partial ranking, almost always. A roadmap conversation rarely needs a fully ranked opinion on every single candidate - it needs to know what rises to the top. Cap the sequence to however many features you can realistically ship in the timeframe you're actually planning for (your top 3, your top 5), and let respondents stop there rather than forcing a full ranking of everything on the list.

Frame the intro message around the real constraint. "If your team could only build three of these this year, which three, and in what order?" produces a more honest result than "please rank these features," because it makes the actual tradeoff explicit rather than leaving respondents to guess whether you're asking for a wish list or a real constraint.

Keep the list to genuinely distinct candidates. Two features that address nearly the same underlying need split their own placement across both options rather than either one clearly rising - see our guide on common mistakes for more on why near-duplicate items muddy a sequence's results.

Reading the Result as a Planning Input¶

Route Flow gives you the group's dominant priority order directly - not an averaged importance score, but the specific sequence respondents actually converged on. The per-step agreement reading matters as much as the order itself here: a roadmap decision built on a dominant order with strong agreement across every step is a genuinely different level of confidence than one built on an order where the group was split on which feature actually deserves the second slot. If that split shows up, Route Network will show you whether it's a close two-way disagreement or something messier - worth knowing before you present a single ranked list to stakeholders as if it were unanimous.

FAQ¶

Should I run this with customers, with my own team, or both?
Both, run as separate sections or separate studies - customer prioritization tells you what your audience actually wants; internal prioritization (product, sales, support) tells you what your own team believes matters, and the two frequently diverge in informative ways.

How is this different from just asking customers to vote on their top pick?
A single top pick tells you what's most popular in isolation. Sequence Flow's forced ordering tells you the full priority structure - not just what wins, but what comes second, third, and so on - which is what an actual roadmap needs, since you're rarely building only the single most popular item and nothing else.

Can I combine this with a rating question to get both signals?
Yes - nothing stops you from asking a rating question on the same features elsewhere in the same survey. Just don't expect the rating question to do the forced-tradeoff job Sequence Flow does; they're answering different questions, and that's worth keeping straight when you interpret both.

For the setup mechanics, see How to Set Up a Sequence Flow Section (Full vs. Partial Ranking).