User Story Mapping, book, Agile, design

User Story Mapping by the book

user story mapping, agile, design, book, Jeff Patton

All design, whether PowerPoint deck, website, software, product, operating model, or Thanksgiving dinner, is an effort to deliver experience. Experience can range from bad to good to exceptional and where you land along that range depends on how well the designer understands their audience need.

When design fails end-user need:

  • We waste time,
  • We waste effort,
  • Frustration builds, and
  • Trust is lost

A User Story creates better understanding. Before development starts, a user-story and a user story map provides design a view of user journey to solution.

User Story Mapping, as a software development tool, aims to focus design teams on users and user needs. But you say “I am not a software designer?” and I say, “everything we do is design, read on friend”.

Any effort to improve design is a wise investment for:

  • Trainers,
  • Organization development,
  • Communications,
  • Marketing, and
  • Beyond

In short, this is so much more than a software development tool.

Your Solution for Their Story

This book, User Story Mapping, written by Jeff Patton and Peter Economy comes from the source. It is Patton who conceived User Story Mapping to help software development effort meets end-user value. I always find the source a good source, by-the-by, and this book is also a great source for:

  • User story cards,
  • Persona development,
  • Story maps, and
  • User experience maps

The more clearly a product solves what’s in it for the user, the sooner value becomes realized. The book is both self-deprecating towards funny and instructive, I expect the skeptic in all of us appreciates the following from the authors:

When I first heard the term story, it bugged me. I’ll admit it. The idea that we’d trivialize the important things that people wanted by calling them stories didn’t seem right. But I’m a slow learner—a point I brought up earlier when discussing shared understanding. It took me a while to really get that:

Stories get their name from how they should be used, not what should be written.

Even before I’d really understood why stories had that name, I realized that I could write down a bunch of stories—a sentence or a short title —on sticky notes or cards. I could move them around and prioritize them to decide which one was more important. Once I decided that one was more important than another, then we could start having a discussion about it. This was super-cool. Why hadn’t I ever written things on cards and organized them this way before?

This is brilliant in simplicity and invaluable in practice. With User Story Mapping, the sequence, step-by-step, that the user goes through becomes a map to follow to solve, from need to delight. The story is a view for development and design to more easily share understanding an around.

Deliver Design Solutions

True understanding represents a difference between getting something done and getting something accomplishment.

Design is not about how you define something is done. Design is about how well deliver to a user’s need.

This is a fantastic resource to leverage in any design effort and I have used this book to teach other’s about story mapping, customer experience design, story cards, personas, and visualization.

So, go, create better stories. You will find it worth the effort.

Read More Books

See a more current set of books on my reading list heavy rotation page.


Subscribe to Email Posts and Join 1,262 New Friends
I believe in your privacy and will never sell or spam your email.

Share this Post

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.