Work and teams
Prioritize a product roadmap
Compare product initiatives using customer value, evidence, effort, strategic fit, risk, and sequencing dependencies.
The basic idea
Roadmap debates often mix desirability, feasibility, urgency, and executive preference. Separate those dimensions and give models the same evidence so disagreements are about reasoning rather than hidden inputs.
Compare reliability work, a new collaboration feature, a benchmark library, and a visual analytics feature under a fixed engineering budget.
How to do it
- 1
List candidate initiatives and define the decision horizon.
- 2
Provide customer evidence, expected value, effort ranges, dependencies, and risks.
- 3
Ask independent models to rank options before letting them see one another’s answers.
- 4
Use a later turn to challenge the ranking and propose a sequence rather than a single winner.
What to watch for
- Numerical scores can create false precision when inputs are guesses.
- Separate mandatory security or compliance work from discretionary features.
- Revisit the roadmap when evidence changes instead of treating the council result as permanent.
What a useful result looks like
The result should expose why an initiative ranks highly and which dependency or uncertainty could reorder the roadmap.