Prioritization

Overview

Prioritization is not a single framework but a family of tools with a shared purpose: making defensible, explicit decisions about which initiatives to pursue when everything seems important and resources are finite. The three most commonly used in consulting contexts:

The Impact/Effort Matrix (also called the Value/Effort Matrix or Effort/Impact Matrix) plots potential initiatives on two axes — expected impact (y-axis) and effort or cost required (x-axis) — to quickly segment them into four categories. No single inventor is reliably identified; the 2×2 format is an analogue to the BCG Matrix applied to workstreams rather than business units, and it became standard in consulting and product management in the 1990s.

MoSCoW was developed by Dai Clegg of Oracle in the mid-1990s for use with the DSDM (Dynamic Systems Development Method) agile framework. The acronym categorizes requirements or initiatives into: Must have (non-negotiable — without these, the initiative fails), Should have (high priority but not critical to immediate success), Could have (nice to have if time and budget allow), Won't have this time (explicitly excluded — but possibly revisited later). The lowercase "o"s in MoSCoW are padding to make the acronym pronounceable.

Weighted Scoring is a decision analysis technique with roots in operations research and formalized in approaches like Kepner-Tregoe Decision Analysis (1965). A set of evaluation criteria is established, each assigned a weight reflecting its relative importance. Each option is then scored against each criterion, and the weighted scores are summed to produce a composite ranking.

When to Use It

Whenever a client has more potential initiatives, features, or requirements than they can pursue simultaneously — which is almost always. The choice of tool depends on the nature of the decision:

• Impact/Effort Matrix: fast, visual, good for early-stage prioritization or cross-functional workshops. Best when "quick wins" vs. "big bets" framing is useful.
• MoSCoW: good for scope decisions with a hard constraint (a deadline, a budget, a release window). Excellent for conversations where stakeholders disagree about what's essential vs. desirable.
• Weighted Scoring: best when the decision is high-stakes, criteria are complex, or the team needs to defend its recommendation to a demanding audience. The rigor of explicit weighting forces the criteria conversation that informal prioritization avoids.

How It Works

Impact/Effort Matrix

1. List all initiatives or options.
2. For each, estimate impact (high/low) and effort/cost (high/low).
3. Plot on the 2×2. Four quadrants emerge:
   • Quick wins (high impact, low effort): do these first
   • Major projects (high impact, high effort): plan and resource carefully; don't skip
   • Fill-ins (low impact, low effort): do if capacity allows
   • Thankless tasks (low impact, high effort): avoid or eliminate
4. Discuss: is there agreement on placement? The disagreements reveal assumptions worth surfacing.

MoSCoW

1. Define the constraint: what is the binding limitation — a date, a budget, a team size?
2. List all candidate requirements or initiatives.
3. Categorize each as M, S, C, or W. Rules: Musts alone should be achievable within the constraint; Shoulds add value if the Musts come in under budget; Coulds are stretch goals; Wonts are explicitly deferred.
4. Validate: can the Musts actually be delivered within the constraint? If not, either the Musts need to be re-negotiated or the constraint does.
5. Get explicit buy-in on the Wonts — these are the hardest part of the conversation.

Weighted Scoring

1. Define the evaluation criteria: what factors matter for this decision?
2. Assign weights: how important is each criterion relative to the others? Weights should sum to 100%.
3. Score each option against each criterion (typically 1–5 or 1–10).
4. Calculate weighted scores: score × weight, summed across criteria.
5. Rank options by total score.
6. Sanity-check: does the ranking feel right? If not, challenge the weights — they embed the judgment calls that drive the outcome.

Common Pitfalls

• Effort underestimation — teams systematically underestimate implementation effort, especially on initiatives that are exciting or familiar; push for explicit effort assumptions before plotting
• Impact conflation — "impact" needs to be defined: impact on revenue? Customer satisfaction? Speed? Without agreement on what's being measured, the matrix reflects different assumptions for different initiatives
• Everything is a Must — MoSCoW only works when stakeholders are willing to say "Won't." If every requirement is a Must, the prioritization exercise is theater
• Criteria chosen to justify a pre-decided answer — weighted scoring is only as honest as the criteria and weights; post-hoc rationalization looks rigorous but isn't
• Prioritization without sequencing — knowing what's important isn't the same as knowing what to do first; good prioritization produces an ordered action plan, not just a ranked list

Recommended Books

• Bulletproof Problem Solving — Charles Conn & Robert McLean
• Inspired — Marty Cagan
• Thinking Strategically — Dixit & Nalebuff