{"id":12213,"date":"2017-02-17T14:22:52","date_gmt":"2017-02-17T12:22:52","guid":{"rendered":"https:\/\/mozaicworks.com\/?p=9981"},"modified":"2017-02-17T14:22:52","modified_gmt":"2017-02-17T12:22:52","slug":"3-uses-story-maps-build-better-product","status":"publish","type":"post","link":"https:\/\/mozaicworks.com\/blog\/3-uses-story-maps-build-better-product","title":{"rendered":"3 uses for story maps to build a better product"},"content":{"rendered":"

One of the first techniques I learned as a beginner Product Owner was user story mapping<\/strong>. I immediately found it was easy to understand and apply. What took a while longer was appreciating its true power – identifying all the situations where it can be applied.<\/p>\n

In the eventriX<\/a> team, we use it to keep the product roadmap, plan development iterations, detail potential features, and even plan meetings. Read on for 3 detailed examples – how story maps help us get the job done better & more efficient.<\/strong><\/p>\n

Quick intro to story mapping<\/h2>\n

A story map is a way of visually telling a story, to support conversations. The main purpose is to build shared understanding<\/strong> for the members of the team.<\/p>\n

When building a story map, a best-practice is to involve all the relevant people in the team<\/strong>. In the case of a product team, gather people like product owner, tester, technical lead, architect, UX\/UI designer etc. Because of their various backgrounds and interests, they all bring in useful perspectives. Plus, in the end, everyone has a clear & common understanding of what they start working on.<\/p>\n

Tip:<\/em> As a PO, I sometimes quickly create a story map for a problem \/ feature I\u2019m dueling with. I randomly leave it around the office.<\/em> It always ends up attracting attention from someone else in the team. In this way, I  have useful conversations, getting valuable input and, bonus, not distracting anyone from their immediate work.<\/p>\n

How to build a story map<\/h2>\n

Let\u2019s take a simple real-life example and follow the steps together: build the story map of prepping & getting to work in the morning.<\/p>\n

\"The<\/a>
The Storymap of Andrew’s Morning<\/figcaption><\/figure>\n
    \n
  1. Start with the goal<\/strong>. What is the story map about? What are you trying to accomplish? Top-left corner, clear and visible – why?<\/li>\n
  2. Make visible who does the actions in the story map. Who is the actor in the scene we are describing? Who is the persona<\/strong><\/a> for the product features you are to detail?<\/li>\n
  3. On the first row, left to right, insert the main steps of the story map – main activities<\/strong> that need to happen.<\/li>\n
  4. Move on and detail each main activity<\/strong> – column by column, left to right.<\/li>\n<\/ol>\n

    Optional: in the case of product features, you can move further to a sketching approach – create planned product iterations<\/strong>. What are the main details we need to implement right away and what can be delayed? Select and draw a line between each iteration.<\/p>\n

    Tip:<\/em> Build at the level of detail that serves your purpose.<\/em> For example, the \u201cMake coffee\u201d single activity above, could be detailed into its own story map. Depending on the persona of the story map, it will look very differently – ex. someone making an espresso will have a totally different \u201cMake coffee\u201d story map than someone using a french press.<\/p>\n

    When exploring product features, you might choose to build story maps for multiple options that solve the underlying problem. Do this confidently – it will allow you to best analyze ups & downs for each option and make the best choice. Thus everyone in the team will contribute and understand the final decision.<\/p>\n

    Use-case 1: product roadmap<\/h1>\n

    <\/a><\/p>\n

    This was the story map for eventriX<\/a> first product MVP. The main goal is on the big green post-it<\/strong> in the top-left. Continue on that row and you find the legend of the story map.<\/p>\n

    Because we have two personas interacting with the product<\/strong>, the main activities are noted on different colored post-its:<\/p>\n