prioritization-advisor

Choosing the right prioritization framework depends on your product stage, team context, decision-making needs, and data availability. Adaptive questioning across these four dimensions identifies whether RICE, ICE, Value/Effort, or Kano best fits your specific context to prevent roadmap misalignment.

RICE prioritization scores reach, impact, confidence, and effort, while ICE simplifies to impact, confidence, and ease. RICE suits data-rich environments needing detailed justification, whereas ICE works better for faster, early-stage decisions where data availability is limited and speed matters more than precision.

Use the Value/Effort matrix when you need a quick visual map of high-value, low-effort wins for roadmap planning. Choose Kano when prioritizing features based on customer satisfaction categories like basic needs, performance, and delight, which requires deeper user research and sentiment data to execute effectively.

Run data-driven prioritization by applying adaptive questions to evaluate product stage, team context, decision needs, and data availability, then apply the recommended framework. Use the provided scoring template to quantify stakeholder inputs, ensuring objective alignment and preventing framework whiplash across planning cycles.

Common prioritization pitfalls include forcing a one-size-fits-all framework regardless of product stage, ignoring actual data availability, and failing to align stakeholders on scoring criteria. The guide provides tailored implementation steps and highlights specific traps to avoid based on your detected product context and team setup.

Prioritization frameworks can be adapted for early-stage products with limited data by selecting lightweight approaches like ICE or Value/Effort. The adaptive questionnaire detects your data availability and product stage to recommend a framework that matches your current constraints while still providing structured decision-making guidance.