Feature Prioritization Report

Q1 Roadmap Planning

Features Analyzed: 4
Framework: RICE Scoring (Reach x Impact x Confidence / Effort)
Capacity: 16 person-weeks

---

Executive Summary

Recommended Q1 Roadmap (fits 16-week capacity):

1. Onboarding wizard (3 weeks - RICE: 567)
2. Reporting (6 weeks - RICE: 525)
3. Search (2 weeks - RICE: 285)

Total Effort: 11 weeks (leaves 5 weeks buffer or contingency)

Deferred to Q2+:

• Integrations (RICE: 200) - High effort (10 weeks), low confidence (50%). Risk of consuming entire quarter for uncertain outcome.

Key Insight: All three recommended features can ship this quarter with healthy buffer. Integrations has the lowest RICE score and highest risk profile - defer until you can increase confidence through discovery or prototyping.

---

RICE Scores Ranked

Rank	Feature	RICE	Reach	Impact	Confidence	Effort	Quadrant
1	Onboarding wizard	567	2,000	Medium (1.0)	85%	3 wks	Fill-In
2	Reporting	525	1,500	High (3.0)	70%	6 wks	Big Bet
3	Search	285	1,200	Low (0.5)	95%	2 wks	Fill-In
4	Integrations	200	800	Massive (5.0)	50%	10 wks	Big Bet

---

RICE Calculation Methodology

Formula: RICE = (Reach x Impact x Confidence) / Effort

Impact Scale Used:

• Minimal = 0.25
• Low = 0.5
• Medium = 1.0
• High = 3.0
• Massive = 5.0

Confidence: Expressed as decimal (85% = 0.85)

Example Calculation (Onboarding wizard):

• RICE = (2,000 x 1.0 x 0.85) / 3 = 1,700 / 3 = 567

---

Value vs. Effort Matrix

High Value | Big Bets                  | Quick Wins
           |                           |
           | * Reporting               | (none)
           | * Integrations            |
           |                           |
           |---------------------------|---------------------------
           | Time Sinks                | Fill-Ins
           |                           |
           | (none)                    | * Onboarding wizard
           |                           | * Search
           |                           |
Low Value  +---------------------------+---------------------------
             High Effort                  Low Effort

---

Detailed Analysis by Quadrant

Big Bets (High Value, High Effort)

Reporting - RICE: 525

• 1,500 users affected, high impact per user
• 6 weeks effort, 70% confidence
• Recommendation: BUILD THIS QUARTER. Strategic investment with strong RICE score. Start after onboarding wizard to maintain momentum.

Integrations - RICE: 200

• Massive impact potential BUT only 50% confidence
• 10 weeks effort = 62.5% of quarter capacity
• Recommendation: DEFER TO Q2. Run a 2-week discovery spike first to validate approach and increase confidence from 50% to 75%+. At 75% confidence, RICE would jump to 300.

Fill-Ins (Lower Value, Low Effort)

Onboarding wizard - RICE: 567

• Highest RICE score despite “fill-in” classification
• 2,000 users (highest reach), medium impact, 85% confidence
• Only 3 weeks effort
• Recommendation: BUILD FIRST. Despite lower value classification, exceptional RICE score makes this the clear starting point. Quick win to build momentum.

Search - RICE: 285

• 1,200 users, low impact per user, 95% confidence
• Only 2 weeks effort
• Recommendation: BUILD THIRD. Fits easily in remaining capacity. High confidence (95%) means low execution risk.

---

Recommended Roadmap

Phase 1 (Weeks 1-3): High RICE Quick Build

• Onboarding wizard (3 wks) - RICE: 567

Phase 2 (Weeks 4-9): Strategic Investment

• Reporting (6 wks) - RICE: 525

Phase 3 (Weeks 10-11): Polish & Ship

• Search (2 wks) - RICE: 285

Remaining Capacity: 5 weeks buffer (31% contingency)

Use buffer for:

• Overruns on reporting (most likely)
• Integrations discovery spike (2 weeks)
• Technical debt or bug fixes

---

Sensitivity Analysis

If reporting takes 9 weeks instead of 6 (50% overrun):

• Cumulative effort: 14 weeks
• Still fits capacity with 2-week buffer
• Mitigation: Search can be deferred to Q2 if needed

If you increase integrations confidence to 75%:

• RICE jumps from 200 to 300
• Still ranks #4 (below search)
• Still recommend deferring: 10 weeks is too large for Q1 with 3 other features

Close rankings to monitor:

• Onboarding (567) vs. Reporting (525) = 8% difference
• Small reach changes could flip order
• Recommendation stands: Start with onboarding for momentum

Risk assessment:

• Lowest risk: Search (95% confidence, 2 weeks)
• Medium risk: Onboarding (85% confidence)
• Higher risk: Reporting (70% confidence, 6 weeks)
• Highest risk: Integrations (50% confidence, 10 weeks) - defer

---

Strategic Recommendations

Build This Quarter

1. Onboarding wizard - Highest RICE, affects most users, builds momentum
2. Reporting - High value strategic bet, strong RICE score
3. Search - Low effort, high confidence, fits in remaining capacity

Defer to Q2

Integrations - Despite “massive” impact rating, 50% confidence and 10-week effort make this too risky for Q1. Run 2-week spike first to:

• Validate technical approach
• Confirm integration partner APIs
• Increase confidence to 75%+
• Re-score for Q2 with better data

Key Success Factors

• Ship onboarding first to demonstrate early wins
• Protect 5-week buffer for reporting overruns
• Don’t commit to integrations without discovery spike
• Track actuals vs. estimates to improve Q2 planning

---

Next Steps

1. Validate estimates with engineering team (especially 6-week reporting estimate)
2. Start onboarding wizard (Week 1) - highest RICE score
3. Kick off integrations discovery spike in parallel (Weeks 1-2 with separate team member if capacity exists)
4. Transition to reporting (Week 4) after onboarding ships
5. Build search (Weeks 10-11) if capacity remains
6. Review integrations spike results at end of Q1 for Q2 planning