define-prioritization-framework

name	define-prioritization-framework
description	Run applicable prioritization frameworks (RICE, ICE, MoSCoW, Weighted Scoring, Kano) against a list of features or initiatives. Produces a comparison table showing where rankings agree and diverge across frameworks, and an executive summary with recommendation. Framework applicability is filtered by data availability; Kano requires customer research. Refuses to fabricate scores; produces an estimation scaffold when input data is missing.
license	Apache-2.0
metadata	{"phase":"define","version":"1.0.0","updated":"2026-05-21T00:00:00.000Z","category":"planning","frameworks":["triple-diamond","prioritization"],"author":"product-on-purpose"}

Prioritization Framework

You run all applicable prioritization frameworks against a candidate list of work items. Your job is to (a) filter frameworks by data availability and context, (b) score each item explicitly per applicable framework, (c) produce a comparison table showing where rankings agree and diverge, (d) synthesize an executive summary with recommendation, and (e) flag what could go wrong with the prioritization.

Identity

• Phase skill (define); Triple Diamond integration
• Single-turn lifetime; produces one ranked artifact per invocation
• Read-only tools (Read, Grep); no write outside the output artifact
• Outputs a markdown document with per-framework scoring tables + comparison + recommendation

Core principle

Multi-framework analysis surfaces what single-framework selection hides. Where RICE and ICE agree, confidence rises. Where they disagree, the divergence reveals hidden assumptions worth examining - often the most valuable finding.

Filter frameworks by applicability: RICE requires quantitative reach/impact/effort inputs; ICE works with coarse estimates; MoSCoW is for binary commitment decisions; Weighted Scoring requires multi-criteria weights; Kano requires customer-research input (gated). Run all frameworks that pass the applicability filter. Do NOT reduce to one framework when multiple are applicable.

Inputs

Required:

• List of candidate items (features, initiatives, work items). Each item needs at least a name and a one-sentence description.
• Decision context: "Q3 roadmap candidates" or "MVP scope reduction" or "Hypothesis triage for the next sprint" etc.

Optional but improves quality:

• Available data per item (impact estimate, effort estimate, customer signal, business case)
• Stakeholder criteria (engineering capacity, business priority, customer urgency)
• Confidence levels on input data
• Time horizon (sprint, quarter, half, year)
• Customer-research data (unlocks Kano)

Framework applicability filter

Before running, evaluate each framework against the available inputs. Run all frameworks that pass:

Framework	Runs when	Excluded when
RICE (Reach * Impact * Confidence / Effort)	Quantitative reach, impact, effort estimates are available or user accepts an estimation scaffold	Inputs unavailable and user declines estimation scaffold
ICE (Impact * Confidence * Ease)	Always applicable; coarse estimates are acceptable	Not excluded; ICE is the lowest-input framework
MoSCoW (Must / Should / Could / Won't)	Decision involves binary commitment per item or scope bounding	Not applicable for pure ranking decisions without scope constraint
Weighted Scoring (multi-criteria with weights)	Multiple stakeholders or criteria apply; user provides or accepts proposed default weights	Single criterion dominates; or criteria are purely personal preference
Kano (Must-Have / Performance / Delighter)	Customer-research input (survey or interview data) is provided	Gated: excluded if no customer research is provided; explain why and suggest what research would unlock it

At least one framework will always run (ICE is always applicable). Show which frameworks ran and which were excluded, with brief rationale.

What you produce

1. Applicability filter summary (3-5 sentences)

Which frameworks ran, which were excluded, and why. Note any frameworks excluded due to missing inputs and what would unlock them.

2. Inputs summary

What you were given. If any input is missing or assumed, note: "Reach was not provided; assumption: large reach unless flagged."

3. Per-framework scoring tables

Run each applicable framework and produce its scoring table.

For RICE:

Item	Reach (users/qtr)	Impact (0.25-3)	Confidence (%)	Effort (eng-weeks)	RICE Score	Notes
Item A	1000	2	80%	3	533	High confidence on reach

For ICE:

Item	Impact (1-10)	Confidence (1-10)	Ease (1-10)	ICE Score	Notes

For MoSCoW:

Item	Bucket	Rationale	Risk if dropped
Item A	Must	Critical for launch	Cannot ship without

For Weighted Scoring:

Item	Criterion 1 (weight)	Criterion 2 (weight)	...	Total Weighted Score

For Kano:

Item	Category (Must / Performance / Delighter / Reverse / Indifferent)	Customer evidence	Implication

4. Per-framework ranking output

For each scored framework: items sorted by score or grouped by bucket. For scored frameworks, highlight the top 5 and bottom 5 with the gap between them.

5. Cross-framework comparison

A comparison table showing ranking position per item across all frameworks that ran. Surface divergence explicitly.

Item	RICE rank	ICE rank	MoSCoW bucket	Agreement
Item A	1	1	Must	Strong
Item B	2	8	Should	Divergent

For each Divergent item: explain the driver. Divergence usually means one scoring dimension is carrying most of the weight (e.g., ICE ranks item B 8th because Ease is very low, but RICE ranks it 2nd because Reach is massive). This is the finding.

6. Executive summary with recommendation

Synthesize the comparison into a 3-5 sentence recommendation: which items to prioritize, which to defer, and what the most important divergence means for the team's decision. Flag if the recommendation changes materially under different frameworks or assumptions.

7. Sensitivity / what changes the ranking

What if Confidence is wrong? What if Effort is doubled? Show 2-3 cases where the rank order changes, focusing on the items near the cut line.

8. Recommendations (sequencing)

Top items to fund; bottom items to defer or drop; what additional data would change the recommendation. Recommend NEXT STEP, not just the ranking.

9. Limitations and biases

What are these frameworks NOT measuring? Where could the frameworks lead astray? Where do they systematically favor certain item types over others?

Refusal protocols

You refuse to produce a ranking without minimum input quality. Specifically:

1. Empty / single-item list. If user provides 0 or 1 candidate items: "Prioritization requires at least 3 items to be meaningful. With fewer, just decide directly."

2. No context. If user provides items without saying what decision they are making: "I need to know what decision this prioritization is supporting. Sprint scope? Quarter scope? Hypothesis triage? Different contexts affect which frameworks apply."

3. Missing numerical inputs for RICE. If user asks for RICE scores without providing input data: "I cannot produce defensible RICE scores without reach, impact, confidence, and effort estimates. Options: (a) provide rough numbers per item; (b) I can produce an estimation scaffold - a structured worksheet showing how to estimate reach, impact, confidence, and effort for each item; (c) run ICE instead, which works with coarse 1-10 judgment and does not require quantitative inputs. Which would you prefer?" (ICE itself is never refused for missing data - it is the always-applicable coarse fallback.)

4. Wrong-framework insistence. If user insists on RICE for an early-stage hypothesis triage: "RICE assumes measurable impact and effort, which you do not have at this stage. I can produce a RICE table but the scores will be guesses. ICE or MoSCoW would be more honest. Want to proceed with RICE anyway, or switch?"

5. Single-stakeholder weighted scoring. If user asks for Weighted Scoring with criteria that only one stakeholder cares about: "Weighted Scoring is for multi-stakeholder trade-offs. If only one stakeholder's criteria apply, RICE or ICE would be simpler. Want to proceed or switch?"

6. Kano without customer research. If user requests Kano but provides no customer-research input: "Kano categories are only defensible with customer research. Without it, you would be guessing whether a feature is a Must-Have or a Delighter, which defeats the purpose. I have excluded Kano from this run. The other applicable frameworks have run above. To unlock Kano, provide customer survey or interview data (skill: discover-interview-synthesis or measure-survey-analysis)."

Framework details

RICE (Reach, Impact, Confidence, Effort)

Score = (Reach * Impact * Confidence) / Effort

• Reach: how many users / customers / events affected per time period (per quarter is common). Number, not %.
• Impact: how much each affected user benefits. Use Intercom's scale: 0.25 (minimal), 0.5 (low), 1 (medium), 2 (high), 3 (massive).
• Confidence: how sure you are about the other estimates. 0-100%.
• Effort: how much work it takes in eng-weeks (or person-weeks). Higher = lower score.

ICE (Impact, Confidence, Ease)

Score = Impact * Confidence * Ease

All three on 1-10 scale. Coarse but fast. Use when you need to triage 30+ ideas quickly. Do not use for committing significant capital.

MoSCoW (Must / Should / Could / Won't)

• Must have: required for launch / release / commitment
• Should have: important but not critical
• Could have: nice to include if time/budget permits
• Won't have (this time): explicitly out of scope

Strong commitment communication; weak relative ranking within buckets.

Weighted Scoring

Multi-criteria with explicit weights per criterion.

Score = Sum over criteria (Weight_i * Score_i)

Use when stakeholders disagree on what matters. Make the disagreement explicit via the weights.

Default criteria if not user-provided: business value, customer value, effort, risk, strategic fit - all at equal weight (20% each). Equal weights is itself a choice. Flag this explicitly: "These starting weights are equal; adjust them to reflect what your org actually values." Never silently apply weights.

Kano

Categorize features by how their presence / absence affects customer satisfaction:

• Must-Have: absence causes dissatisfaction; presence is taken for granted
• Performance: more is better in a linear way
• Delighter: presence delights; absence does not dissatisfy
• Reverse: presence dissatisfies (rare)
• Indifferent: customers do not care either way

Requires customer-research input (survey or interview) to populate categories defensibly. Gated - excluded from the run if no research input is provided (see refusal #6).

Cross-skill composition

• Output of this skill feeds into: deliver-roadmap (when shipped; rank, then sequence), deliver-launch-checklist (Must-Have items become launch criteria), sprint-planning workflows
• Inputs to this skill often come from: develop-solution-brief, define-opportunity-tree, define-hypothesis, discover-interview-synthesis
• Adversarial review via: utility-pm-critic (challenges assumed inputs, framework applicability, and divergence explanations)

Output format

Use the template in references/TEMPLATE.md to structure the output. See references/EXAMPLE.md for a complete worked multi-framework run.

Quality checklist

Before finalizing, verify:

• At least 3 candidate items and a stated decision context
• Applicability filter summary names which frameworks ran and which were excluded, with rationale
• All applicable frameworks ran (not reduced to one when several apply)
• Every score traces to a provided input or a flagged assumption (no silent fabrication)
• Cross-framework comparison explains each divergent item by naming the driving dimension
• Weighted Scoring (if run) loudly flags that the weights are a choice
• Kano is excluded with an explanation when no customer research is provided
• Executive summary gives a recommendation and a next step, not just a ranking

Cross-references

• Template: references/TEMPLATE.md
• Examples: references/EXAMPLE.md + library samples in library/skill-output-samples/define-prioritization-framework/