prioritization-advisor
Match prioritization frameworks to your product stage, team context, and decision-making needs.
- Guides you through four adaptive questions about product maturity, team structure, stakeholder alignment, and data availability to recommend the right framework (RICE, ICE, Value/Effort, Kano, or others)
- Explains when each framework excels and when it fails, with implementation steps and scoring templates
- Helps avoid "framework whiplash" by matching approach to context rather than applying one-size-fits-all solutions
- Includes common pitfalls (overweighting effort, inflating confidence, solo PM scoring) and reassessment triggers for when to switch frameworks
Purpose
Guide product managers in choosing the right prioritization framework by asking adaptive questions about product stage, team context, decision-making needs, and stakeholder dynamics. Use this to avoid "framework whiplash" (switching frameworks constantly) or applying the wrong framework (e.g., using RICE for strategic bets or ICE for data-driven decisions). Outputs a recommended framework with implementation guidance tailored to your context.
This is not a scoring calculator—it's a decision guide that matches prioritization frameworks to your specific situation.
Key Concepts
The Prioritization Framework Landscape
Common frameworks and when to use them:
Scoring frameworks:
- RICE (Reach, Impact, Confidence, Effort) — Data-driven, requires metrics
- ICE (Impact, Confidence, Ease) — Lightweight, gut-check scoring
- Value vs. Effort (2x2 matrix) — Quick wins vs. strategic bets
- Weighted Scoring — Custom criteria with stakeholder input
Strategic frameworks:
- Kano Model — Classify features by customer delight (basic, performance, delight)
More from deanpeters/product-manager-skills
prd-development
Build a structured PRD that connects problem, users, solution, and success criteria. Use when turning discovery notes into an engineering-ready document for a major initiative.
1.7Kuser-story
Create user stories with Mike Cohn format and Gherkin acceptance criteria. Use when turning user needs into development-ready work with clear outcomes and testable conditions.
1.7Kroadmap-planning
Plan a strategic roadmap across prioritization, epic definition, stakeholder alignment, and sequencing. Use when turning strategy into a release plan that teams can execute.
1.5Kcompany-research
Create a company research brief with executive quotes, product strategy, and org context. Use when preparing for interviews, competitive analysis, partnerships, or market-entry work.
1.3Kproduct-strategy-session
Run an end-to-end product strategy session across positioning, discovery, and roadmap planning. Use when a team needs validated direction before committing to execution.
1.2Kuser-story-mapping
Create a user story map that lays out activities, steps, tasks, and release slices. Use when planning a workflow, backlog, or MVP around the user journey.
1.1K