Jeff Patton
Updated 2026-04-06
Product coach and author, best known for Story Mapping. Relevant here because he offers one of the most practical antidotes to flat, contextless backlogs.
Context
Patton matters not because he introduced another PM buzzword, but because he made an old problem visible: once teams split work into small tickets too early, they lose the user flow, the dependencies, and the intended experience. Story Mapping restores that larger picture.
That places him between strategy and delivery. His method is concrete enough for workshops and prioritization, yet strong enough to improve the quality of discovery conversations. That makes him more useful in this wiki than many general-purpose agile sources.
Core Ideas
- The user journey is the right order for work - not the backlog, but the user’s path provides structure
- Stories are markers for conversation, not perfect specs - strong teams talk instead of pretending completeness through cards
- Smaller slices improve learning - a well-cut slice reduces effort and increases insight speed
- Visualization is decision work - a story map is not decoration, but a tool for exposing gaps and priorities
Connections
- User Story Mapping - his central book and canonical source
- Product Discovery - his thinking helps teams understand problems and user flows before delivery
- Inspired - Cagan describes the operating system; Patton provides one of its most useful concrete practices
- Continuous Discovery Habits - both favor continuous learning over linear requirement handoff
- Petra Wille - same product context, different emphasis
Sources
- User photo of the User Story Mapping book cover from 2026-04-06