Day 274 of the Daily · Product Management

User Story Mapping

5 min read · 4 principles · apply it by lunch

Morning. A backlog is a list. Nobody’s day has ever happened in a list.

The question

Your team has committed to a release next: could one real customer start at the very beginning and get all the way through to the thing they actually came for using only what’s above the line — or does it stop somewhere in the middle, polished at step one and missing entirely at step four? A backlog sorted by priority almost always slices the wrong way.

The idea

Jeff Patton spent years coaching teams who’d turned a product into a flat, prioritised list and then wondered why the first release felt broken. In 2008 he published a piece called The New User Story Backlog is a Map, expanded in 2014 into User Story Mapping for O’Reilly, and his fix is almost embarrassingly physical: stop sorting the backlog and lay it out. Across the top go the things a person does, left to right in the order they do them — the backbone of the story. Under each one hang the details, the variations and the alternatives, the most necessary at the top. The list now has two dimensions instead of one, and a release stops being the first thirty cards. It becomes a horizontal line drawn across the whole map: everything above it ships, and it ships as something a person can get through end to end. Alistair Cockburn calls that thinnest working path a walking skeleton — ugly and unfinished, but alive along its whole length. Don’t confuse it with the MVP you were taught earlier: an MVP is the smallest thing that tests a hypothesis, so it’s a learning device; a walking skeleton is the smallest thing a real customer can get all the way through, so it’s a release. A one-dimensional backlog can’t show you either line, which is why sorting by priority so reliably builds the opening beautifully and strands the customer at step four.

In the Daily · 4 principles and a template

User Story Mapping is Day 274 of 365.

In the Daily, each of its four principles is explained in full, with a one-page template to apply it the same day. A new framework arrives every morning at 7am for a year, across all fifteen courses of the FutureMBA curriculum.

$29 a month · cancel any time · 7-day money-back guarantee

More from Product Management

The next four in the course.

All 22 Product Management frameworks
Day 283 · Product Management

Brooks’s Law

Think about the last project that ran late on you: when the extra people arrived, who stopped doing their own work in order to bring them up to speed, how many weeks went by before the newcomers were producing more than they were consuming, and did anyone put either of those two costs on paper before the decision got made?

See the framework →
Day 293 · Product Management

The Five-User Test

Have you ever sat behind someone who’d never seen your product, handed them a real task and then stayed silent while they failed at it — or is everything you believe about how the thing gets used assembled entirely from your own hands on your own keyboard?

See the framework →
Day 302 · Product Management

Affordances and Signifiers

Somewhere in your product sits a control that needed a tooltip, an onboarding step and a help article wrapped around it before anybody could work out what it did — so if all three were deleted tomorrow and nothing else changed, how many of your customers would still know where to click? The explaining is the part you can count. The control underneath it is the part somebody would have to fix.

See the framework →
Day 311 · Product Management

Which Side to Subsidise

If you run anything that needs two groups to turn up before either of them gets any value — buyers and sellers, readers and writers, players and developers — can you name which of the two you’re deliberately underpricing, say what the other side is paying extra for the privilege of reaching them, and tell me whether either of those numbers was ever a decision rather than something you inherited from whichever side signed up first?

See the framework →