# Prioritization and Slicing

Order work using value, effort, and risk, then slice it so value and feedback arrive sooner.

Duration: 10 min

A backlog has one top. This lesson makes ordering an explicit decision and shows why a small valuable slice delivered now beats a large promise delivered late.

## fmap-m3-l3-v1

The approved narration and storyboard are present in the source pack. Final media and captions remain review gates.

## fmap-m3-l3-digest

### Order is strategy

A list has one top. If every item is “priority one,” nobody has made the decision that limited capacity requires. Ordering asks: if we could do only one thing next, which would it be?

A value-versus-effort lens creates four useful conversations. High-value, low-effort items are quick wins. High-value, high-effort items are big bets to schedule and slice. Low-value, low-effort work is a fill-in, not automatically urgent. Low-value, high-effort work is a money pit whose place on the list should be challenged. Risk can break ties: an early scary slice may cheaply test whether the entire idea works.

MoSCoW supplies shared vocabulary: Must, Should, Could, and Won't—this time. The honest Won't is the discipline in the method. A list with no Won't items usually has not made a choice.

Slicing matters because value does not exist while work is merely in progress. A smaller valuable slice can be delivered sooner, creates evidence sooner, and lets the team steer sooner. A big bet should rarely travel as one monolith; find the thinnest slice that creates a real benefit or answers a consequential question.

Quick wins are useful, but prioritization is not “easy first.” It is value first, risk aware, and sliced small enough to finish.

## fmap-m3-l3-i1

This activity uses a model order to create feedback, not to claim that prioritization has one context-free answer.