Roadmap Prioritization Prompts: RICE, MoSCoW & Cost-of-Delay Frameworks (2025)
Master the art of roadmap prioritization with proven frameworks: RICE, MoSCoW, and Cost-of-Delay. This comprehensive guide shows you how to make data-driven decisions about what to build next, with AI prompts and templates that streamline your prioritization process.
Jump to Section:
Why Roadmap Prioritization Matters
Product managers face a constant challenge: too many good ideas, too few resources. Without a systematic approach to prioritization, teams waste time on low-impact features while high-value opportunities languish. The frameworks in this guide help you make objective, data-driven decisions about what to build next.
📊 Data-Driven Decisions
Use metrics and frameworks instead of gut feelings to prioritize features
🎯 Focus on Impact
Ensure your team works on features that deliver the most business value
⏰ Optimize Time-to-Value
Get the right features to market faster with better prioritization
When to Use Each Framework
RICE Framework
Best for: Feature-level prioritization with quantifiable metrics
MoSCoW Method
Best for: Sprint planning and stakeholder communication
Cost-of-Delay
Best for: Strategic decisions and opportunity cost analysis
RICE Framework: Reach, Impact, Confidence, Effort
RICE Scoring Formula
Higher scores = Higher priority
RICE Components Breakdown
🎯 Reach
How many people will this feature affect in a given time period?
Scoring: 1-5 scale based on user count or percentage
Example: 1 = 100 users/month, 5 = 10,000+ users/month
💥 Impact
How much will this feature impact your users when they encounter it?
Scoring: 0.25 (minimal) to 3 (massive impact)
Example: 0.25 = nice-to-have, 3 = must-have feature
🎲 Confidence
How confident are you in your Reach and Impact estimates?
Scoring: 50% (low confidence) to 100% (high confidence)
Example: 50% = gut feeling, 100% = data-backed estimate
⏱️ Effort
How much work will this feature require from your team?
Scoring: 1-5 scale based on person-months
Example: 1 = 1 week, 5 = 6+ months
RICE Framework Example
| Feature | Reach | Impact | Confidence | Effort | RICE Score |
|---|---|---|---|---|---|
| Dark Mode | 4 (5,000 users) | 2 (high impact) | 80% | 3 (2 months) | 4.3 |
| Advanced Search | 5 (10,000 users) | 3 (massive impact) | 90% | 4 (3 months) | 3.4 |
| Email Notifications | 3 (2,000 users) | 1 (medium impact) | 95% | 1 (2 weeks) | 8.6 |
Based on this scoring, Email Notifications would be the highest priority (8.6), followed by Dark Mode (4.3), then Advanced Search (3.4).
MoSCoW Method: Must-Have, Should-Have, Could-Have, Won't-Have
MoSCoW Categories
🚨 Must-Have (M)
Critical features without which the product cannot be released.
Rule: 60% of your effort should go here
⚠️ Should-Have (S)
Important features that add significant value but aren't critical for launch.
Rule: 20% of your effort should go here
💡 Could-Have (C)
Desirable features that would be nice to have if time and resources permit.
Rule: 20% of your effort should go here
❌ Won't-Have (W)
Features explicitly excluded from the current scope or future consideration.
Rule: 0% of your effort should go here
MoSCoW Prioritization Example
E-commerce Mobile App - Q1 2025
Cost-of-Delay Analysis: The Hidden Cost of Waiting
What is Cost-of-Delay?
Cost-of-Delay measures the financial impact of not delivering a feature or project on time. It helps you understand the opportunity cost of delays and prioritize work based on urgency and business value.
Cost-of-Delay Formula
Cost-of-Delay = Business Value × Urgency
Cost-of-Delay Categories
🔥 Expedite (High Cost-of-Delay)
Features that lose significant value if delayed. Start immediately.
Examples: Compliance features, seasonal features, competitive responses
⚡ Standard (Medium Cost-of-Delay)
Features that lose some value over time but can be scheduled normally.
Examples: User experience improvements, performance optimizations
🐌 Defer (Low Cost-of-Delay)
Features that maintain their value regardless of when they're delivered.
Examples: Nice-to-have features, internal tools, documentation
Cost-of-Delay Example
Feature: Holiday Shopping Cart Optimization
Decision: Expedite - Start immediately to capture holiday shopping season
AI Prompts for Roadmap Prioritization
🎯 RICE Framework Prompt
Use this prompt to calculate RICE scores for your features:
Help me calculate RICE scores for these product features:
[List your features]
For each feature, please:
1. Estimate Reach (1-5 scale: how many users affected)
2. Estimate Impact (0.25-3 scale: user impact level)
3. Estimate Confidence (50-100%: how sure you are)
4. Estimate Effort (1-5 scale: person-months required)
5. Calculate RICE Score = (R×I×C)÷E
6. Rank features by RICE score
Context: [describe your product and user base]
📋 MoSCoW Categorization Prompt
Use this prompt to categorize features using MoSCoW:
Help me categorize these product features using the MoSCoW method:
[List your features]
For each feature, categorize as:
M (Must-Have): Critical for product launch
S (Should-Have): Important but not critical
C (Could-Have): Nice to have if resources allow
W (Won't-Have): Excluded from current scope
Ensure M features represent ~60% of effort, S+C features ~40%
Context: [describe your launch timeline and constraints]
💰 Cost-of-Delay Analysis Prompt
Use this prompt to analyze cost-of-delay for your features:
Help me analyze the cost-of-delay for these product features:
[List your features]
For each feature, please:
1. Estimate business value (revenue, cost savings, user growth)
2. Assess urgency (seasonal, competitive, compliance deadlines)
3. Calculate cost-of-delay = Business Value × Urgency
4. Categorize as Expedite/Standard/Defer
5. Recommend prioritization order
Context: [describe your business model and market conditions]
Downloadable Prioritization Templates
📊 RICE Scoring Template
Excel template for calculating RICE scores across multiple features with automatic ranking.
Download Template📋 MoSCoW Planning Template
Template for categorizing features and planning sprint allocations.
Download Template💰 Cost-of-Delay Calculator
Spreadsheet for analyzing opportunity costs and urgency factors.
Download Template🎯 Prioritization Dashboard
Comprehensive template combining all three frameworks for strategic planning.
Download TemplateBest Practices for Roadmap Prioritization
1. Use Multiple Frameworks
Don't rely on just one prioritization method. Combine RICE, MoSCoW, and Cost-of-Delay for a comprehensive view of feature importance.
2. Validate Assumptions with Data
Use user research, analytics, and market data to inform your estimates rather than relying solely on intuition.
3. Review and Update Regularly
Priorities change as market conditions, user needs, and business goals evolve. Reassess your roadmap monthly.
4. Involve Stakeholders
Include engineering, design, marketing, and sales teams in prioritization discussions to ensure alignment and buy-in.
5. Balance Short-term and Long-term
Don't focus only on quick wins. Ensure your roadmap includes strategic initiatives that build long-term competitive advantage.
Related Resources for Product Managers
📝 PRD Examples & Templates
Study real Product Requirements Documents to understand how prioritization fits into product planning.
📊 User Story Generation
Use prioritization insights to generate better user stories that align with strategic objectives.
🔍 Competitive Analysis
Use competitive insights to set more strategic priorities and identify market opportunities.
📝 Customer Interview Analyzer
Use customer insights to prioritize roadmap features that deliver the most user value.
🚀 Launch Checklist Prompts
Ensure your prioritized roadmap items are ready for successful launch.
🎯 Strategic Planning
Learn how to set strategic objectives and key results that guide your prioritization decisions.
📚 Get weekly prioritization templates and strategic planning tips
Join 5,000+ Product Managers receiving:
- ✨ Weekly curated AI prompts that save hours
- 💡 Exclusive PM strategies and frameworks
- 🎯 Early access to new features and prompts
Join your peers from Google, Meta, Amazon and other top companies