Prioritization Advisor

What Is This?

Overview

The Prioritization Advisor is a structured decision-support skill designed to help product managers select the most appropriate prioritization framework for their specific context. Rather than defaulting to a single scoring method or switching between frameworks without clear reasoning, this skill guides you through a series of adaptive questions about your product stage, team dynamics, and stakeholder requirements. The result is a deliberate, defensible framework choice that aligns with your actual situation.

Product teams frequently encounter what practitioners call "framework whiplash," the pattern of adopting RICE one quarter, switching to ICE the next, and then abandoning both in favor of a simple value/effort matrix when stakeholders push back. This inconsistency erodes trust and makes prioritization feel arbitrary. The Prioritization Advisor addresses this by establishing clear criteria for framework selection before any scoring begins.

The skill draws on established product management methodologies and applies them contextually. It considers variables such as team size, data availability, decision-making authority, and the maturity of the product to recommend a framework that will hold up under scrutiny and remain usable across multiple planning cycles.

Who Should Use This

• Product managers at any experience level who need to justify prioritization decisions to engineering, design, or executive stakeholders
• Product leads and directors responsible for aligning multiple teams around a shared backlog or roadmap
• Startup founders acting as their own product managers who need lightweight frameworks appropriate for early-stage products

Why Use It?

Problems It Solves

• Eliminates arbitrary framework selection by grounding the choice in team context and product stage
• Reduces stakeholder friction by producing a prioritization approach that maps to their decision-making language
• Prevents over-engineering prioritization for early-stage products where data is scarce and speed matters more than precision
• Stops under-engineering prioritization for mature products where gut-feel scoring leads to poor resource allocation
• Resolves disagreements between team members who advocate for different frameworks without a shared evaluation criteria

Core Highlights

• Adaptive questioning approach that adjusts recommendations based on your specific inputs
• Coverage of major frameworks including RICE, ICE, value/effort matrix, MoSCoW, and weighted scoring models
• Guidance on when qualitative judgment should override quantitative scoring
• Consideration of stakeholder communication needs alongside internal team needs
• Support for both feature-level and initiative-level prioritization decisions
• Framework comparison output that explains trade-offs rather than just naming a winner
• Practical templates and scoring structures ready for immediate use

How to Use It?

Basic Usage

Start by answering a core set of diagnostic questions. You can structure these as a simple prompt or work through them in a product planning document.

Context: B2B SaaS, 18-month-old product, team of 6, quarterly planning cycle
Data available: Usage analytics, NPS scores, sales pipeline data
Stakeholders: Engineering lead, CEO, 3 enterprise customers with active contracts
Decision type: Feature prioritization for next quarter

Feeding this context into the advisor produces a framework recommendation with rationale. For this example, RICE scoring would be appropriate because you have sufficient data for reach and impact estimates, and the stakeholder group expects quantitative justification.

Specific Scenarios

Scenario 1: Early-stage product with limited data. When your product is under six months old and you lack reliable usage data, the advisor will steer you away from RICE toward an ICE score or a simple value/effort matrix. These frameworks require less historical data and move faster.

Scenario 2: Executive stakeholder alignment. When your primary audience is a CEO or board, the advisor may recommend a strategic alignment matrix that maps features to business objectives rather than a raw scoring table.

Real-World Examples

A growth-stage fintech team used the advisor to move from ad hoc prioritization to a weighted scoring model that incorporated regulatory risk as an explicit factor, something standard frameworks omit.

A two-person startup applied the advisor's recommendation to use a simple effort/impact grid, avoiding the overhead of RICE scoring that would have consumed more time than the decisions themselves.

Important Notes

Requirements

• A defined product context including stage, team size, and planning horizon
• At least a basic understanding of what data is available to support scoring
• Clarity on who the primary decision-making stakeholders are
• Willingness to apply the recommended framework consistently for at least one full planning cycle