Organize · Roadmap

Let demand rank your roadmap

More good ideas than you can build? Members sort every candidate into Must have, Should have, Could have or Won't have this time, cast one forced 'ship this first' vote, and tell you what's missing, so you sequence the roadmap on evidence rather than the loudest voice.

Organize BusinessesProduct teamsCommunities MoSCoW frameworkScoringScore pipingForced-choice vote
What it showcases

Features most survey bots don't have

📊

Intensity, not just a yes

Every candidate lands in one of the four MoSCoW levels, so you see how badly people want each one rather than a thumbs up or down.

🥇

The forced 'ship one' vote

A single pick-one question surfaces the feature people want most when they can't have everything, the sharpest priority signal there is.

🔢

Live appetite score

Each respondent sees their own 'feature appetite' tallied from their picks and piped into the closing message, 12 out of 12 if every one of the four example candidates is a Must. A small payoff that puts Subo's scoring on display.

📝

A what's-missing box

An open request captures the idea that isn't on your list yet. That's the request-board half, so the roadmap grows from real demand.

Worked example This template comes with a a product roadmap or a community 'what should we add?' board example so you can see exactly how it plays. Edit the questions and content to make it your own.

When you have more good ideas than you can build, the hard part is sequencing them, and a single “which feature do you want?” poll hides more than it reveals. This template runs every candidate through the four MoSCoW levels, so you see the intensity of demand, then adds one forced “ship this first” vote to surface the sharpest priority.

You leave with a demand matrix, not a single winner: what’s broadly loved, what’s narrowly adored, and what people want most when they can’t have everything. A what’s-missing box captures the ideas outside your list, so the roadmap keeps growing from real demand.

The four levels

The template uses MoSCoW as its authors defined it, and the intro block teaches the levels to respondents before they answer, which is what makes the answers comparable across people.

LevelWeightWhat it means
🔴 Must have3The release fails for you without it.
🟠 Should have2Painful to miss, but there’s a workaround.
🟡 Could have1Nice, and the first thing you’d drop if time ran out.
⚪ Won’t have this time0Fine to leave for a later release.

Two things about that last level are easy to get wrong, and both are written into the copy on purpose. “Won’t have” is scoped to this release, not forever, so nobody reads it as a rejection and refuses to pick it. And the framework only works if Musts are scarce: a survey where every candidate comes back red has told you nothing.

Demand, quantified

Sorting each candidate turns vague enthusiasm into a number you can rank. Each respondent even sees their own “feature appetite” tallied live, a small payoff that puts Subo’s scoring on display, one of the features the data shows almost nobody discovers.

Variants

  • More candidates or categories: add candidate questions and group them under section headers.
  • Weighted by segment: ask role or plan first and weight power-user demand differently.
  • Public request board: make write-in requests visible to build a lightweight Canny-style board.
  • Value vs. effort: clone twice to build a value/frequency matrix.
How to run it

Live in a few minutes

  1. 1

    Swap in your candidates

    Replace the example features with your own roadmap candidates. Add as many as you like, and keep the four MoSCoW levels on each one.

  2. 2

    Keep or tune the weights

    Must have scores 3, Should have 2, Could have 1, and Won't have this time 0. Leave the defaults or reweight them to how your team sequences work.

  3. 3

    Publish it to your users

    Point a #roadmap channel or a web link at it. Members rate, vote, and add requests in under two minutes.

  4. 4

    Read the demand matrix

    Rank features by how broadly and how intensely they're wanted, and let the forced-choice vote break ties.

FAQ

Common questions

What is MoSCoW prioritization?

A method for sorting candidate work into four levels of necessity: Must have (the release fails without it), Should have (painful to miss, but there is a workaround), Could have (nice, and the first thing you drop if time runs out), and Won't have this time (fine to leave for a later release). It comes from DSDM, and the point of the fourth level is that it is scoped to this release rather than forever. It only works if Musts stay scarce: if everything is a Must, nothing is.

How is this different from a single feature poll?

A one-pick poll hides the second-place feature that most people also wanted. Sorting every candidate into a MoSCoW level gives you the intensity of demand, broadly loved versus narrowly adored, and the forced 'ship one' vote adds the priority signal on top.

What's the 'feature appetite' score?

It's each respondent's total across the four candidates, weighted 3 / 2 / 1 / 0 by MoSCoW level and shown back to them at the end as a score out of 12. It's the engagement hook; your real output is the per-feature demand distribution.

Can members request features that aren't listed?

Yes. The what's-missing box captures ideas outside your candidate list, so the survey doubles as a request board.

Does it work for a community, not just a product?

Yes. Reframe the candidates as community additions (events, channels, activities) for a 'what should we add?' board.

Use this template

Clone it into your community, swap in your content, and share it. No building from scratch.