Prioritization and Slicing

"They're all priority one." Every workplace has heard it. Seven items, all must-haves, all urgent, all top of the list. Here's the uncomfortable arithmetic: a list has exactly one top. If everything is priority one, then nothing is — someone has refused to decide. This lesson is about deciding.

By the end of this video, you'll be able to order a mixed backlog with a simple value-versus-effort lens, use MoSCoW labels to make priority conversations honest, and explain why cutting work into smaller slices delivers value sooner — every time, by definition.

Recall: the backlog is ordered. Not grouped, not color-coded — ordered. Position one, position two, position three. That ordering is the Product Owner's accountability from Module 2, and it's uncomfortable on purpose: it forces the question "if we could only do one thing next, which?" Dodge that question and the loudest stakeholder decides by volume. Answer it, and the order of a simple list quietly becomes your strategy — because in a world of limited capacity, sequence is the strategy.

The default tool is a two-by-two. One axis: how much value does this create — using last lesson's test, how strong is its "so that"? The other: how much effort will it cost? Four quadrants, four instincts.

High value, low effort: quick wins — generally do these first; they pay for the journey. High value, high effort: big bets — schedule them deliberately, and slice them (more in a moment). Low value, low effort: fill-ins — batch them for spare moments, never let them jump the queue just because they're easy. And low value, high effort: the money pit. The most useful thing you can do with a money pit is ask, out loud, why it's on the list at all. Often nobody remembers.

One refinement before we move on: risk is the tiebreaker. Sometimes the right first item isn't the easiest win but the scariest question — the item that tests whether the whole idea works. Doing the scary thing early is buying information while it's still cheap to act on.

The two-by-two is your private lens; MoSCoW is the public vocabulary. Four labels: Must have — the release fails without it. Should have — important, but the release survives its absence. Could have — nice, if room appears. Won't have — this time — explicitly out, explicitly recorded.

Here's the secret experienced people know: the power of MoSCoW is the W. Anyone can make a Must list — that's just wishing with capital letters. Writing "Won't — this time" next to a stakeholder's pet feature, in public, with the words this time softening the blow? That's the moment prioritization becomes real. A MoSCoW list with no Ws is a list that hasn't decided anything yet.

Now the move that multiplies everything above. Value doesn't exist while work is in progress — remember Module 3's opening: nothing has changed for anyone until something is delivered. Which yields a rule that sounds too simple to matter and changes everything: cut the work smaller, and value arrives sooner. So does feedback — and feedback is steering.

Back to the cake from Module 1: you don't bake the wedding cake before anyone tastes anything; you serve a slice, watch faces, adjust the recipe. A "big bet" quadrant item should almost never ship as one monolith — find the thin slice that delivers real value on its own, ship that, learn, continue. A small thing delivered beats a big thing promised. Every time. That sentence is two of this course's five principles shaking hands: outcomes over output, and finish over start.

You might think prioritization is about effort — do the easy stuff first, always. That's understandable; quick wins are genuinely lovely. Actually, effort only matters in ratio to value, and sometimes the right first move is a hard, scary, valuable slice — because it answers the question everything else depends on. Easy-first is a habit. Value-first, risk-aware, sliced small — that's a strategy.

Three things to keep. One: a list has one top — ordering is a forced, honest choice, and sequence is strategy. Two: value over effort as the lens, MoSCoW as the vocabulary, and the power of MoSCoW is the honest Won't. Three: smaller slices mean sooner value and sooner steering — a small thing delivered beats a big thing promised.

There's a name for the most extreme version of slicing — the smallest slice you'd build purely to learn something. It has a famous three-letter name, and almost everyone uses it wrong. Five minutes, next lesson.