We're familiar with creating user stories as well as user flows. User story mapping is an activity that combines both of these activities while increasing our team collaboration. It also gives us a tangible place to prioritize and document things like problems, questions, things we should be listening for in our user tests, and a visual representation of the extent of the work we're about to undertake.
- User stories intention is to help create understanding of what we're building and why
- However, over time we've perhaps lost site of their intention by focusing too much on the format that user stories take.
- The intention is to tell stories--to communicate.
- User story mapping helps give us an activity that seeks to broker conversations across the team to create mutual understanding and allows us to prioritize features/details of our build.
I tried one of those broth bowls from Panera where they're trying to do a faux ramen. It was ok, but a lot more noodle ratio than broth.