prioritization-advisor

Prioritization Advisor - Consultant for Selecting a Product Requirements Prioritization Framework

Skill Overview

Prioritization Advisor is an interactive decision-making consultant. Through four adaptive questions about your product stage, team background, decision-making challenges, and data availability, it recommends the most suitable approach for your current situation from mainstream prioritization frameworks such as RICE, ICE, and the Value/Effort Matrix. It also provides scoring templates and implementation steps.

Use Cases

Establishing a prioritization process for the first time — The team is still operating on a “whoever speaks loudest gets their way” basis and wants to introduce a structured product requirements prioritization method, but does not know which framework to start with.

The current framework is ineffective or frequently changing — The team switches frameworks every quarter, and the resulting priorities lack team buy-in. It needs to determine whether the framework was chosen incorrectly or applied poorly, avoiding “framework churn”—the confusion caused by constantly switching prioritization methods.

Misaligned stakeholder opinions — Sales wants customer customizations, executives want strategic investments, and engineering wants to address technical debt. Roadmap planning remains stalled, creating a need for a transparent requirements review process that can build consensus.

Core Features

Adaptive situational Q&A — Asks only four questions: product stage (pre-PMF / growth / mature / multi-product), team and stakeholder environment, core decision-making challenge to address, and data availability. Each question offers 3–4 options, while also allowing custom descriptions. The process takes just over ten minutes to complete.

Framework-matching recommendations — Covers more than ten frameworks, including RICE, ICE, the Value/Effort Matrix, Weighted Scoring, the Kano Model, Opportunity Scoring, MoSCoW, and Cost of Delay. It provides a primary recommendation and alternatives, while clearly stating the boundaries of when each framework should not be used.

Implementation guidance — Provides definitions for scoring dimensions, calculation formulas (such as RICE = Reach × Impact × Confidence / Effort), reusable requirements-scoring templates, and reminders about the most common pitfalls of each framework, such as over-relying on scores or having the PM score everything alone and thereby failing to gain team buy-in.

Frequently Asked Questions

What is the difference between RICE and ICE? How should I choose?

Both evaluate Impact and Confidence. The difference lies in the other two dimensions: RICE uses Reach—how many users will be affected—and divides by Effort, requiring actual usage data; ICE scores Ease, or implementation difficulty, based entirely on subjective estimates. Choose RICE when you have baseline data and want to compare requirements with different levels of reach horizontally. Choose ICE when the product is still in its early stages without sufficient data and you want to quickly prioritize 20 ideas within 30 minutes. The consultant will make a direct recommendation based on your data availability.

Can I use it if the product has not reached PMF and I have no user data?

Yes. This is exactly the kind of mismatch it is designed to address: forcing a data-driven framework such as RICE on a pre-PMF product can undermine speed simply because estimating Reach becomes burdensome. In this situation, the consultant will recommend lightweight methods such as ICE or the Value/Effort Matrix, which are better suited to rapid experimentation. Once the product enters the growth stage and baseline data becomes available, you can switch to RICE.

Can it replace product judgment and tell me directly what to build first?

No. It does not score specific requirements for you; instead, it helps you choose “which measuring stick to use.” Its output consists of a framework recommendation and implementation steps. The final decision about whether to build a particular requirement, and whether strategic judgment should override its score, remains up to you. The skill itself also emphasizes that a prioritization framework is an input to decision-making, not decision automation, and cannot replace product strategy.