Frameworks replace debate with comparison. The Eisenhower Matrix sorts work by urgency and importance to clarify what to do, schedule, delegate, or eliminate. RICE scores ideas by Reach (users or events affected per period), Impact (a 0.25-to-3 per-user multiplier), Confidence (a percentage for evidence strength), and Effort (person-months), calculated as (Reach × Impact × Confidence) ÷ Effort. ICE is a lighter cousin — Impact, Confidence, Ease — but its main limitation is that it skips Reach, which can over-rate features that delight a small audience over work with broader reach.
MoSCoW groups work into Must have, Should have, Could have, and Won't have (for now). It is useful but has an ambiguity trap: stakeholders inflate "Must" until everything is mandatory, so many teams impose strict caps (for example, no more than 60% of items at Must) to restore signal. The Kano model classifies features by how they shape customer satisfaction. Must-be features are expected — their absence causes dissatisfaction but their presence creates no delight. Performance features scale linearly — more is always better. Attractive features delight when present but cause no dissatisfaction when missing. Reverse features are a warning sign: more actually decreases satisfaction for some users. Indifferent features do neither. Opportunity scoring takes a different angle: it prioritizes where customer importance is high but current satisfaction is low — a clear signal for where investment will move the needle.
Weighted Shortest Job First (WSJF), from the Scaled Agile Framework, divides Cost of Delay by Job Size to schedule the highest WSJF first. Cost of Delay captures the economic impact per unit time of NOT having a feature — it combines business value, urgency, and risk reduction. Sometimes a lower-value item with high cost of delay outranks a higher-value item that can wait safely. Value-vs-effort analysis produces a familiar 2x2: quick wins (high value, low effort, usually first to ship), big bets (high value, high effort, requiring strategic commitment), fill-ins (low value, low effort, good for slack), and time sinks (low value, high effort, usually cut or deferred indefinitely).
When ranking needs to surface disagreement rather than bury it, lightweight workshop techniques help. Buy-a-Feature gives stakeholders fake money to "buy" features; their allocation reveals real priorities. Dot-voting hands each participant a fixed number of stickers to place on options. The 100-point method asks each stakeholder to distribute 100 points across options, forcing trade-offs and revealing intensity of preference. More formal structures include prioritization scorecards (options against weighted criteria, totaled per option), Multi-Criteria Decision Analysis (MCDA), and the Analytic Hierarchy Process (AHP), which derives weights from structured pairwise comparisons. When scoring produces wide agreement without rigor, forced distribution scoring (requiring a fixed percentage at each rating tier) prevents grade inflation — the "if everything is a 10, nothing is a 10" trap.