prioritization-advisor

Choosing a prioritization framework requires evaluating your product stage, team context, and data availability. This Skill uses adaptive questioning to map your specific scenario and recommend a tailored framework like RICE, ICE, or Kano for your needs.

The difference between RICE and ICE for roadmap planning lies in data requirements and evaluation depth. RICE uses reach, impact, confidence, and effort metrics for detailed analysis, while ICE provides a simpler, faster scoring approach for teams with limited data.

Use the Kano model versus a value/effort matrix when prioritizing customer satisfaction over resource allocation. Kano evaluates features based on user delight and basic expectations, while a value/effort matrix directly scores backlog items on implementation cost versus business return.

To implement prioritization with limited data, select lightweight frameworks like ICE or a value/effort matrix. This Skill provides specific implementation steps and guardrails to help you apply these methods effectively to your roadmap planning without requiring extensive metrics.

Limitations of using RICE for backlog prioritization include its reliance on precise numerical estimates for reach, impact, and effort, which can introduce false precision. This Skill outlines specific guardrails and scenarios detailing when not to use RICE to prevent skewed decisions.