A plain roadmap poll tells you what your community picked and nothing about why. This template asks both: members choose what to build next, then Subo asks the reason, and the follow-up changes based on how they voted, so the conversation always reads naturally.
Run it whenever you have a shortlist and want the community to prioritize it: the next game mode, the next feature, the next event, the next big fix. It forces a single clean choice, then captures the reasoning behind it, which is the signal that actually drives a roadmap.
The reason matters as much as the vote
When a member votes for a listed feature, Subo echoes their pick back and asks what it would unlock for them. When they choose the write-in option, they’re asked what they’d build instead. Same survey, two conversations, and no voter hits a dead end.
The example runs as a studio’s next-update vote. Rename the options and the branches and it fits any team or community.
Variants
- Product feature vote: list candidate features and ask paying users what each would unlock for their workflow.
- Community activity vote: let members choose the next event and tell you what would make them show up.
- Prioritization with urgency: the built-in urgency scale already separates nice-to-have from blocking. Reword its points to your own release language if “soon” means something specific to your team.
- Quarterly check-in: run it on a schedule to keep the roadmap grounded in what people actually want.