> If we give each other time to explain ourselves using words and pictures, we build shared understanding. > —[[Jeff Patton]], *[[Patton - *User Story Mapping*|User Story Mapping]]* User story mapping is a method and book by [[Jeff Patton]]. [^USM] [^USM]: [[Jeff Patton]]. 2014. *User Story Mapping: Discover the Whole Story, Build the Right Product*. Sebastopol, CA: O’Reilly Media. ![[user-story-map.png]] User Story Mapping is a method of using sticky notes or cards to map out the primary activities, sequential steps, and details a user would take to achieve a goal. Done together, story mapping helps create a shared understanding, surfaces risks and questions, and can ultimately help groups realize how to build less while delivering desired outcomes. Story mapping may take several hours (or even days!) depending on the depth and breadth of the product or feature. As understanding grows, update the map to reflect the new understanding. You will want at least 4 different colored sticky notes, one for each of the following types: - Primary Activities (e.g., green) - Steps (e.g., blue) - Details (e.g., yellow) - Risks/Questions/Important Notes (e.g., pink) ![[IMG_3219_(1).jpg]] User Story Map from a client plan session. In this example green stickies were used for Activities, blue stickies for Steps, yellow for Details, and pink for Questions, Risks, and Important Notes. ### **Building out the story map:** 1. Start by identifying the **Personas** you will be creating the story map for. These should include any actors in the system, including the system itself. 2. Write down each of the primary **Activities** people will use the software for and put these in rough horizontal order. Each activity should be its own sticky note (e.g., blue sticky). Throughout the exercise, the order of these activities may change. Activities are best written as single words or short phrases, such as “Signing up,” “Creating a new record.” 3. Underneath each **Activity**, write down each **Step** on a note and place them left to right in the order they would likely be done in. Together you’ll begin to naturally reorder the steps you come to a shared understanding throughout the exercise. While people using the software may perform activities in different orders at different times, steps are typically done as part of a specific activity. 4. Directly under each **Step,** add the **Details** for that step. Place each detail vertically under the step it belongs to, ordered by importance or level of detail. Details are best written as short verb phrases, such as “Upload an image,” “Attach an audio file,” or “Add free text.” 5. Throughout the mapping exercise and especially at the end, take time to walk through the steps and narrate the story to ensure it makes sense to you and others. Doing so will often reveal gaps in the group’s understanding, invite conversation, and improve everyone’s shared understanding. ### **Finding the “Critical Path”** A key benefit of story mapping is the ability to “slice” the map into multiple deliverable chunks around specific goals. This is done by moving all the **Details** down below a vertical line (e.g., using blue painter’s tape) and then moving only the **Details** needed for the first release above the line. The **Activities** and **Steps** always remain at the top, but may not have any **Details** as part of a particular slice. The story map can be sliced multiple times to tease out multiple releases. ![[story-mapping.png]] Illustration of story map with three “slices” ### **Documenting the Story Map** ![[Story_Map_(1).jpg]] ## Additional Resources - [User Story Mapping 101 (Video)](https://www.nngroup.com/videos/user-story-mapping/?utm_source=Alertbox&utm_campaign=27cc444eff-EMAIL_CAMPAIGN_2020_11_12_08_52_COPY_01&utm_medium=email&utm_term=0_7f29a2b335-27cc444eff-24186965)