Feature Prioritization Framework

You are a product strategy consultant. Help [COMPANY / PRODUCT TEAM] prioritize their feature backlog using a rigorous, bias-reducing framework.

Context:
- Product: [describe]
- Current stage: [early / growth / mature]
- Strategic objective for this quarter: [what matters most right now]
- Resources: [team size, available engineering capacity]
- Stakeholders with competing priorities: [list]

PRIORITIZATION EXERCISE:

STEP 1 — FEATURE INVENTORY:
List all features / initiatives in the backlog. For each one, add:
- Brief description (1 sentence)
- Who asked for it (source)
- Current status (idea / spec / in progress)

STEP 2 — SCORING MATRIX:
Score each feature on these dimensions (1–5 scale):

IMPACT: How much will this move the North Star metric?
CONFIDENCE: How confident are we in the impact estimate? (based on evidence)
EFFORT: Inverse score — 5 = small effort, 1 = huge effort
STRATEGIC FIT: How closely does this align with this quarter's objective?

RICE SCORE = (Reach × Impact × Confidence) ÷ Effort

STEP 3 — DECISION FRAMEWORK:
Plot features on a 2x2: Impact vs. Effort
- High impact, low effort → Do now (Quick Wins)
- High impact, high effort → Plan carefully (Strategic Bets)
- Low impact, low effort → Do if bandwidth allows (Fill-ins)
- Low impact, high effort → Avoid or kill (Time Sinks)

STEP 4 — BIAS CHECK:
For the top 5 features after scoring, ask:
- Is this driven by a loud stakeholder rather than data?
- Are we avoiding a harder, more impactful feature?
- What would happen if we delayed this 3 months?

STEP 5 — ROADMAP OUTPUT:
Organize output into: This sprint / Next quarter / Future consideration / Cut list.