Lesson 29: Prioritization Fundamentals

Across 24 lessons, this curriculum has repeatedly bumped into the same underlying question without ever naming it directly: when multiple genuinely valid things compete for the same limited time and resources, how do you actually decide? Lesson 16 built a Severity/Frequency Grid for pain points. Lesson 19 built an Opportunity Comparison Grid for opportunities. Lesson 10 insisted a real strategy must say no to something. Lesson 21 insisted an MVP must cut anything not necessary for its specific test. Each of these was, in effect, a scoped, local prioritization framework. This lesson generalizes the underlying discipline: prioritization is the practice of deciding what to work on next, using an explicit, defensible method rather than intuition, seniority, or recency alone — and it is, in a real sense, the skill this entire curriculum has been building toward from Lesson 1 onward.

This lesson matters because prioritization is where every other discipline in this curriculum — validated research, laddered pain points, sized opportunities, a real strategy, a scoped MVP — ultimately has to cash out into an actual, defensible decision about sequence: what gets built first, second, and not at all, at least for now. A team can do everything else in this curriculum correctly and still fail here, by falling back on whichever voice is loudest (Lesson 5, Lesson 16) or whichever idea was most recently discussed (Lesson 16, Lesson 19), precisely the failure patterns this curriculum has repeatedly named. This lesson closes that gap with formal, named prioritization frameworks.

Learning Objectives

1
Apply the RICE framework (Reach, Impact, Confidence, Effort) to score and compare candidate initiatives quantitatively.
2
Apply the MoSCoW method (Must have, Should have, Could have, Won't have) as a qualitative, stakeholder-facing prioritization technique, and identify when it's more appropriate than RICE.
3
Distinguish "eating the frog" (tackling the highest-value hard thing first) from artificially easy sequencing, and explain the trade-offs of each.
4
Identify the "prioritization theater" failure pattern, where a formal-looking framework is used to rationalize a decision already made for other reasons.
5
Synthesize prior lessons' scoped, local prioritization tools (severity/frequency, opportunity sizing, strategic fit) into a single, coherent scoring approach for comparing dissimilar candidate initiatives.

Lesson 10 (Product Strategy Basics), Lesson 16 (Pain Points), and Lesson 19 (Opportunity Identification). This lesson assumes fluency with severity/frequency scoring, opportunity sizing via importance-satisfaction and prevalence, and the discipline of genuine strategic exclusion — this lesson generalizes and formalizes these prior, narrower tools into explicit, named prioritization frameworks applicable across a full backlog of dissimilar candidates.

RICE: A Quantitative Scoring Framework

RICE is a widely used scoring framework for comparing dissimilar candidate initiatives on a common numeric scale, using four factors:

Reach: how many people (or what fraction of a validated segment, per Lesson 18) will this initiative affect within a given time period?
Impact: how much will this initiative affect each person it reaches — typically scored on a simple scale (e.g., massive, high, medium, low, minimal), often assigned a corresponding numeric value?
Confidence: how confident is the team in the reach and impact estimates, given the strength of the underlying evidence (directly connecting to Lesson 11's Evidence Trustworthiness Ladder) — typically expressed as a percentage?
Effort: how much time and resource investment will this initiative require, typically expressed in person-time (e.g., person-months)?

The RICE score is calculated as:

RICE Score = (Reach × Impact × Confidence) / Effort

RICE's genuine value is forcing explicit numbers onto each factor, rather than allowing a comparison to remain vague — a candidate initiative that "feels important" must be translated into an actual reach estimate, an actual impact estimate, an honest confidence level, and an actual effort estimate, all of which can be questioned and debated on their specific merits, rather than accepting or rejecting the initiative based on an unstated, holistic impression.

Confidence as the Discipline-Enforcing Factor

The Confidence factor deserves particular attention, since it is the mechanism that connects RICE directly back to this curriculum's research rigor (Lessons 11–13, 19). A candidate initiative based on a vivid anecdote or an unvalidated assumption (echoing Lesson 16's "vivid but rare" warning) should receive a low confidence score, appropriately discounting its overall RICE score relative to a candidate backed by genuine, validated evidence — even if the vivid anecdote's raw reach and impact estimates look impressive on paper. This is precisely the mechanism that prevents RICE from simply reproducing Lesson 16's "loudest voice" or "vivid but rare" failure patterns under a different, more formal-looking name: a low-confidence estimate should genuinely lower the score, not be treated as a formality to move past quickly.

MoSCoW: A Qualitative, Stakeholder-Facing Method

MoSCoW is a simpler, qualitative categorization method, sorting candidate items into four buckets:

Must have: absolutely required for this release or initiative to be considered successful or complete.
Should have: important, but the release could technically function without it if truly necessary.
Could have: desirable, but with a clearly lower priority than "should have" items.
Won't have (this time): explicitly and deliberately excluded from the current scope, directly echoing Lesson 10's exclusion discipline.

MoSCoW is often more appropriate than RICE when a team needs to communicate priority quickly and clearly to a broad set of stakeholders (particularly non-specialist stakeholders less familiar with a quantitative scoring model), or when the goal is defining the boundary of a specific release rather than ranking a large, diverse backlog against each other on a single numeric scale. Its explicit "Won't have" category is a particularly valuable discipline, directly enforcing Lesson 10's argument that a real strategic choice requires explicit exclusion — MoSCoW makes that exclusion a visible, named category rather than an implicit, unstated omission.

"Eating the Frog" vs. Artificially Easy Sequencing

A specific, practical sequencing question, once priorities are established, is: within a set of similarly prioritized items, should a team tackle the hardest, highest-value item first, or build momentum with easier wins first? "Eating the frog" (a phrase associated with productivity writing, referring to tackling the most difficult, most important task first) argues for confronting the highest-value hard work early, since delaying it often means it never actually gets done, or gets rushed under worse conditions later.

The countervailing consideration is that artificially easy sequencing — deliberately front-loading a series of easy wins — can build genuine team and stakeholder confidence, demonstrate visible progress, and (particularly relevant to this curriculum's discovery discipline) surface early, cheap learning that might usefully inform how the harder, more important work is eventually approached. Neither approach is universally correct; the choice depends on specific context — how urgent the hard problem actually is, whether early wins would genuinely inform the harder work or merely delay it, and how much organizational patience and trust currently exists for a team to spend significant time on a single, high-value, high-difficulty initiative without visible interim progress.

The "Prioritization Theater" Failure Pattern

A specific, important failure pattern — directly extending Lesson 8's discovery theater concept — is prioritization theater: applying a formal-looking scoring framework (RICE, MoSCoW, or any other named method) to a set of candidates whose actual priority order has already been decided for other reasons (executive preference, sunk cost, internal politics), with the scoring exercise conducted after the fact specifically to produce numbers that justify the already-determined outcome. This directly parallels Lesson 24's warning about acceptance criteria written after the fact: a scoring framework applied retroactively, to rationalize a decision rather than genuinely inform it, provides the appearance of rigor without any of its substance.

The corrective discipline is the same one this curriculum has applied repeatedly: a genuine prioritization exercise must be capable, in principle, of producing a result that contradicts the team's initial expectation or preference — if a RICE or MoSCoW exercise never once produces a surprising or uncomfortable ranking, that is itself a warning sign worth taking seriously, echoing Lesson 8's core discovery-theater diagnostic applied directly to the practice of prioritization.

Common Mistakes to Avoid

Treating RICE scores as precise, objective numbers rather than structured estimates

RICE scores are only as good as the underlying reach, impact, and confidence estimates feeding into them — treating the resulting number as objectively precise, rather than as a structured, debatable estimate, overstates the framework's actual certainty.

Assigning high confidence scores to vivid anecdotes or unvalidated assumptions

This directly reintroduces Lesson 16's "vivid but rare" and "loudest voice" failure patterns under RICE's formal-looking numeric structure — confidence should genuinely reflect the strength of underlying evidence, not the persuasiveness or memorability of how a candidate was pitched.

Using RICE when MoSCoW would communicate priority more clearly to a broad stakeholder audience, or vice versa

These frameworks serve different purposes — RICE for ranking dissimilar candidates on a common numeric scale, MoSCoW for defining release scope and communicating clearly with less quantitatively focused stakeholders — and using the wrong one for the specific situation reduces the exercise's practical value.

Defaulting to "easy wins first" purely to avoid difficult work, rather than as a deliberate, justified sequencing choice

Artificially easy sequencing can be a legitimate strategy in the right context, but defaulting to it simply to defer difficult, high-value work indefinitely produces the opposite of genuine prioritization discipline.

Running a prioritization exercise after a decision has already effectively been made, to produce justifying numbers rather than genuine input

This is prioritization theater — a formal-looking exercise that could not, even in principle, have changed the outcome is not really prioritizing anything.

Mental Model

The Prioritization Synthesis Funnel

This lesson's mental model is the Prioritization Synthesis Funnel, which shows how this curriculum's earlier, narrower prioritization tools feed into a single, formal framework like RICE or MoSCoW.

Use this funnel as a synthesis discipline: when scoring a candidate's Impact for RICE, or deciding whether it's a "Must have" for MoSCoW, explicitly draw on the specific evidence this curriculum's earlier tools have already produced — a pain point's established severity and frequency, an opportunity's importance-satisfaction gap and segment prevalence, and whether the initiative follows from the company's actual guiding policy — rather than re-deriving a fresh, unmoored judgment from scratch for each new prioritization exercise.

Quick Reflection Checkpoint

Key Takeaway: How will you apply "The Prioritization Synthesis Funnel" when evaluating trade-offs in your product decisions?

Prioritization Fundamentals