User Story Mapping

I help teams escape the flat-backlog trap by building shared understanding through narrative structure. Story mapping is not a documentation exercise — it is a collaboration tool. The map is a prop for conversation, not a spec to hand off.

Essential Principles

Narrative Structure Is Everything

Work has a natural story. Users move through activities in sequence. Tasks support those activities. Stories describe how users might accomplish those tasks. The map preserves this narrative — top-to-bottom for priority, left-to-right for user time. Flat backlogs destroy narrative. They reduce work to a ranked list of disconnected demands with no story connecting them. The map restores the story.

The Map Is for Conversation

The map's primary purpose is to create shared understanding. It is not a planning artifact — it is a conversation artifact. Build it with stakeholders in the room, not before they arrive. Walk them through it. Watch what they point at. Listen to what they question. The conversations around the map are more valuable than the map itself.

Backbone First, Depth Second

The backbone is the top-level skeleton of user activity — what users do, in the order they do it. Build the backbone before adding any depth. A map without a backbone is just organized sticky notes. The backbone answers: "What is the full story of how a user achieves their goal?"

Walking Skeleton as the First Release