User Story Mapping
by Jeff Patton · first published 2013
63% recommend38% neutral
Why HN recommends it
Practical, readable guide to user story mapping, a process for laying out a product's user activities and building releases around them. Readers say it changed how they worked. Suits product people and agile teams.
Summarised by Claude from recommending comments
Affiliate links. As an Amazon Associate I earn from qualifying purchases.
Mentions per year
What Hacker News says
Related books
2016–2024The lean product playbook
Dan Olsen
Recommended by 11 · mentioned by 1211 recommend · 12 mention11 recommend · 1211 recommend
Shape Up
Ryan Singer
Recommended by 5 · mentioned by 85 recommend · 8 mention5 recommend · 85 recommend
2016–2022Sprint
Jake Knapp, John Zeratsky, Braden Kowitz
Recommended by 8 · mentioned by 138 recommend · 13 mention8 recommend · 138 recommend
2009–2023Inspired
Marty Cagan
Recommended by 42 · mentioned by 4742 recommend · 47 mention42 recommend · 4742 recommend
2009–2026The Lean Startup
Eric Ries
Recommended by 284 · mentioned by 612284 recommend · 612 mention284 recommend · 612284 recommend
…actually be iconoclastic and go with Visual Explanations which I think has more to offer programmers over pure data visualization. Again, just grab one every day, flip through 3-4 pages, rinse, repeat. * User Story Mapping - Extremely memorable book - it gives you a pretty clear field guide on prioritization, empathy, communication ... just a great book. * Badass by Kathy Sierra - I flip through this book again and again.…
on “Alan Kay's answer to ‘what are some forgotten books programmers should read?’” ↗…including things like scoping, design, development, testing, general software engineering best practices, collaboration, etc. If you're weak in architecting / product management, I typically recommend User Story Mapping by Jeff Patton and Making Things Happen by Scott Berkun, which are both excellent how-tos with great examples to build on. If you're strong in math, I recommend Understanding Machine Learning from Theory…
on “The Hundred-Page Machine Learning Book” ↗…of books I posted in another thread: * Steve Blank’s The Startup Manual or Four Step to Epiphany. * Dan Olsen, The Lean Product Playbook * Ryan Singer, Shape Up * Jake Knapp, Sprint * Jeff Patton, User Story Mapping * Stephen Wunker, Costovation * Jackie Bavaro, Cracking the PM Career Also checkout /r/productmanagement subreddit.
on “Getting started in product management? Any recommended books?” ↗Good point- that all said, if we're automating requirements we're not solving the problems that tend to matter. The key to requirements building is in the process. The best process I've found so far is User Story Mapping (Jeff Patton has an amazing book on it)
on “What Can You Put in a Refrigerator?” ↗Start with Steve Blank’s The Startup Manual or Four Step to Epiphany. Other books Dan Olsen, The Lean Product Playbook Mart Cagan, Inspired Ryan Singer, Shape Up Jake Knapp, Sprint Jeff Patton, User Story Mapping Stephen Wunker, Costovation
on “Ask HN: I'll Build the Top Comment” ↗…with Steve Blank’s The Startup Manual or Four Step to Epiphany. Other books: * Dan Olsen, The Lean Product Playbook * Mart Cagan, Inspired * Ryan Singer, Shape Up * Jake Knapp, Sprint * Jeff Patton, User Story Mapping * Stephen Wunker, Costovation Also checkout /r/productmanagement subreddit.
on “Ask HN: Good resources to become a better Product Manager?” ↗…these tactics resonated with my team and our codebase has seen marked improvements in the past few months. I'm looking forward to our process catching up so we can do more than "DDD Lite." Jeff Patton, User Story Mapping. This book was fun, practical, and completely outside any way I'd ever worked. It also helped me understand exactly why I've failed every time I tried to make my own SaaS startup on nights and weekends.…
on “Ask HN: What did you read in 2025?” ↗I loved reading "User Story Mapping" and putting it to use. It really changed how I worked. Highly recommended. http://shop.oreilly.com/product/0636920033851.do
on “Ask HN: Better tools for the software requirements / scoping phase?” ↗…delivering value is an anti-pattern in itself. Second, Agile doesn't ask people to estimate ("respond to change over follow a plan"). Management asks people to estimate. Jeff Patton says it best in User Story Mapping, the "client-vendor anti-pattern" > It's the client's job to know what he wants, and explain the details to the vendor. It's the vendor's job to listen, understand, and then think through a technical…
on “What distinguishes great software engineers? (2019) [pdf]” ↗In our tech consulting onboarding guide it says (paraphrasing Jeff Patton's User Story Mapping), "Be doctors, not waiters. Where does it hurt? is the only question you should need."
on “Commenting vs. Making” ↗…be enough. While I am whining, while Personas is a good tool - keep it to a minimum - no full size cutout dolls, CV, background story, accessories, etc. I suggest to keep it to the level described in User Story Mapping (Patterson) and stop there... Anchor the personas with the sales guys, support guys, and people that potentially have met a user.
on “How to Become a UX Designer” ↗What's the greatest compliment you can get on HN? Already been done! (Bonus points if it's "And I did it!") Event Storming is a type of behavior analysis, perhaps a step up from User Story Mapping, that looks much more geared to plugging into a FP paradigm than any of its predecessors. In the past, we've focused a lot on structure in our models. This is the flip-side, looking at behavior. And…
on “EventStorming: Continuous discovery beyond software modelling” ↗…Kindle: - No Rules Rules - Never Split The Difference - The Manager's Path - The Almanack of Naval Ravikant - Ultralearning - The Hard Thing About Hard Things - What You Do is Who You Are - User Story Mapping - Inspired - The Lean Product Playbook - Competing Against Luck - Domain Driven Design - Patterns of Enterprise Application Architecture - Data-Driven Marketing - Designing Data-Intensive…
on “What is expected of a engineering manager?” ↗