Skip to content
Briefs · product

Product Roadmap Prioritisation

Decide what to build next quarter and what to deliberately not build.

You walk away with

A ranked, justified roadmap with the one big bet and what gets cut.

Decidi convenes
Recommended level: StandardProven pro models — the everyday default.
What the council debates
Help us prioritise our product roadmap and have a real debate about it — do not just agree on everything.

CONTEXT:
[product, stage, current strategy, and the audience]
CANDIDATE ITEMS (with any data you have — usage, requests, revenue impact, effort):
[list the features / initiatives competing for the next quarter]
CONSTRAINTS: [team size, time, key dependencies]

Debate:
1. Which items actually move the strategy versus which are noise or loud-customer requests.
2. Effort vs impact for each — and where the estimates are probably wrong.
3. The one big bet worth concentrating force on, versus spreading thin.
4. What should be explicitly cut or deferred, and the cost of saying no.
5. Sequencing and dependencies — what unlocks what.

FINAL SYNTHESIS:
- A ranked roadmap for the period with a one-line rationale per item.
- The single highest-leverage bet and why.
- An explicit "not now / not ever" list.
- The metric that will tell us in 30 days if we chose right.