RevelicaRevelica

Menu


Playbook

Rank ideas

Run Rank ideas

Evaluate and rank ideas against your desired outcome using evidence

Use when

  • Quarterly planning and the team cannot agree on what to build next
  • The backlog has grown and everything feels equally important
  • You want to move beyond gut-feel prioritization and stakeholder politics
  • After a brainstorm cycle, to determine which ideas deserve validation investment

What You Get

  • Idea

    Structured idea entities with scores and rationale for each strategic lens, so the team can see exactly why each idea ranked where it did.

  • Hypothesis

    A hypothesis entity for each top-ranked idea, with the if/then structure explicit and ready for validation experiments.

  • Assumption

    The key assumptions underlying each top-ranked hypothesis, classified by risk type and ready for pre-mortem or data-mining experiments.

How It Works

Why most idea prioritization processes are theater

Most prioritization frameworks — RICE, ICE, MoSCoW — produce rankings that confirm what the most senior person in the room already wanted to build. The criteria are applied after the conclusion is known. Evidence-based idea ranking works differently: it applies strategic lenses before looking at existing rankings, surfaces the assumptions underlying each idea, and produces a structured rationale for each score that can be challenged and revised as new evidence comes in. The result is a backlog where every position is defensible — not just asserted.

Who it's for

Most valuable when the backlog has five or more ideas competing for the same discovery or build slot, and when the team has enough customer and competitive context to ground the scoring in evidence rather than opinion.

Product Manager
Founder
Head of Product
Product Strategist

Frequently asked questions

What is the best framework for prioritizing product ideas?
The most reliable frameworks evaluate ideas on dimensions that are independent of each other — customer desirability, strategic fit, business viability, and technical feasibility — and require explicit rationale for each score. The key is evaluating criteria before knowing the conclusion, not using scores to justify a decision already made.
How do you prioritize ideas without letting the loudest stakeholder win?
By grounding each score in evidence rather than opinion. Each strategic lens has a specific test — is there customer evidence of this pain? — not do I believe customers have this pain. Evidence-backed scoring makes it harder for any single voice to override the group assessment without addressing the evidence directly.
What should I do after ranking my ideas?
Take the top three to five ideas into hypothesis formation and pre-mortem analysis. Do not start building from a ranked list — use the ranking to decide which ideas deserve validation investment first, not which ones to ship.

Community Examples

Works better with

LinearLinear