<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Tobias Holm Jensen on Medium]]></title>
        <description><![CDATA[Stories by Tobias Holm Jensen on Medium]]></description>
        <link>https://medium.com/@tobiasholmjensen?source=rss-68d797336a55------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*B3a4bzf3douGdG4P4-iaaA.png</url>
            <title>Stories by Tobias Holm Jensen on Medium</title>
            <link>https://medium.com/@tobiasholmjensen?source=rss-68d797336a55------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 01:20:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tobiasholmjensen/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Think, Make, Check — Moving Quickly, Together.]]></title>
            <link>https://medium.com/kustomerengineering/think-make-check-moving-quickly-together-1c0cf7cb2638?source=rss-68d797336a55------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c0cf7cb2638</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[lean-ux]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[collaboration]]></category>
            <dc:creator><![CDATA[Tobias Holm Jensen]]></dc:creator>
            <pubDate>Wed, 15 Dec 2021 14:51:09 GMT</pubDate>
            <atom:updated>2021-12-15T20:35:34.620Z</atom:updated>
            <content:encoded><![CDATA[<h3>Think, Make, Check — Moving Quickly, Together.</h3><p>Written by: <a href="https://medium.com/@mattdylangoldman">Matt Goldman</a> and <a href="https://medium.com/@tobiasholmjensen">Tobias Holm Jensen</a></p><p>At Kustomer, we foster shared ownership and collaboration with cross-functional product teams. These cross-functional teams are typically made up of one Product Designer, one Product Manager, one Engineering Manager and a collection of Engineers. The idea is to create teams that come together to work on specific product improvements within an area of the Kustomer platform. To make this successful, we strive to involve everyone in every phase of the project — from problem discovery through implementation.</p><p>We, <a href="https://medium.com/@mattdylangoldman">Matt</a> (Software Engineer) and <a href="https://medium.com/@tobiasholmjensen">Tobias</a> (Product Designer), work together on the team called Platform Automations. This team is responsible for the product features that enable our customers to set up automated workflows in the application. Our team is always looking for ways to enhance our collaboration and deliver valuable software to our users. Recently, we began working using a process inspired by Lean UX which allows us to quickly test and validate our assumptions using functional prototypes. This process consists of three main phases: Think, Make, and Check. In this blog post, we will present the work we did and how Lean UX helps us remove process waste, and foster constant collaboration and rapid experimentation.</p><figure><img alt="process diagram of Lean UX that displays the three steps: Think, Make, and Check" src="https://cdn-images-1.medium.com/max/1024/1*HqhnGe7q4l1Jt5GEZf7A4w.png" /><figcaption><em>The three steps of Lean UX: Think, Make, Check</em></figcaption></figure><h3>💡 Think</h3><p>The first phase of Lean UX is about aligning the team on a problem, our assumptions about it, and our ideas for how to solve it.</p><h4>Starting with a goal</h4><p>One of the main objectives at Kustomer is to improve the product for tremendous scale and growth. A key ingredient in doing so is reducing the time our internal implementations team spends on custom implementations to get new customers set up in the Kustomer platform. To reduce this, we need to come up with innovative solutions that allow new customers to set up Kustomer on their own. One specific problem that we observed was that our implementation team spends a lot of time ingesting data from our customers’ old systems into their Kustomer instance. To achieve this, they would set up workflows that sync data through a webhook into the customer’s Kustomer instance. This seemed like a problem worth focusing on, so we decided to research it further.</p><h4>Building empathy through research</h4><p>To better understand the observed problem and to understand whether this was an impactful problem to solve, we decided to set up multiple interviews with Kustomer employees from the implementation team. To make sure we could collect diverse perspectives and foster alignment within the team, we involved all team members to sit in on these interviews and ask questions. After the interviews were done, we would debrief on key takeaways, surprising insights and observed pain points.</p><p>What we found was that about 75% of custom implementation work was made up of ingesting data into Kustomer. This validated our initial observation that the custom work performed by our implementation team mostly consists of ingesting data.</p><h4>Map out the user journey</h4><p>To create mutual understanding of the problem area, we decided to do a cross-functional workshop with the team. The goal was to map out the user journey with a clear understanding of the goals and jobs to be done. We started by outlining each step in the process, which people and activities were involved, and in particular the pain points along the way in this process.</p><p>Next, we brainstormed on the opportunities for improving the highlighted pain points. The goal here was to generate a wide range of divergent ideas in order to fully understand the various approaches to solving the problem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/691/0*dpQlCLaF_5M2DLFq" /><figcaption><em>The user journey map we created with activities, pain points, and opportunities.</em></figcaption></figure><p>Then, to understand which idea to focus on, we decided to prioritize each idea on a spectrum between effort and impact. The goal of this exercise was to identify the ideas and opportunities that balance the effort required from an operational and technical perspective as well as the actual business and user impact it will have. After prioritizing each idea and placing them in the impact and effort matrix, we started discussing which of these ideas would comparatively offer the biggest opportunity for solving the problem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/0*7BUE4ZQn5twQJ5RE" /><figcaption><em>The Impact/Effort matrix we used to prioritize ideas.</em></figcaption></figure><h4>Establish a hypothesis</h4><p>After having researched the problem, mapped out the user journey and aligned on the problem to solve, we decided to go with a solution that would offer Kustomer employees a tool that would allow them to set up an inbound webhook, map the fields coming in from this webhook and then automatically generate a workflow for them. Our hypothesis was that by providing a tool that would streamline the data mapping and workflow ingest process, we would shorten the implementation time by at least 10%.</p><h3>🔨 Make</h3><p>When the team has settled on a problem and the most impactful solution, the next phase is the Make phase. Here, the goal is to design collaboratively to make a minimum viable product that will help the team test their assumptions and hypotheses.</p><h4>Sketch it out</h4><p>Next up was translating the idea into an actual product. For this, we first sat down together and mapped out the desired user flow that would lead the user to accomplishing their goal. We often leverage user flows as a way to think process before user interface and to quickly start the conversation about the user experience we wish to create. We used this user flow to gather feedback from different stakeholders and to align on the proposed solution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SB83IB9unrmSLusb" /><figcaption><em>The user flow outlining the process steps</em></figcaption></figure><p>Then, we translated the steps of the user flow into actual wireframes of the product. By having the steps and tasks outlined it makes the wireframing process very quick. From this wireframing, we quickly decided on the solution to go with.</p><p>By doing the user flow and the wireframes, we were also able to articulate our assumptions about potential gaps in the solution. We decided to capture these and use them as validation points later in the process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cgHZC5L_PjBCwPxl" /><figcaption><em>Wireframes for the wizard experience</em></figcaption></figure><p>The solution we ended up with was a step-by-step experience that allows admins to set up a webhook connection to their backend, map the fields coming in via the webhook to the object in Kustomer and then automatically generate a workflow.</p><h4>Prototype it</h4><p>The basis for our prototyped solution was that all of the functionality to create a data ingest connection already existed in the Kustomer web application for years. However, users would have to jump between three different settings pages without any in-app direction to build a data ingest Workflow:</p><ol><li>Configurations for creating a new inbound webhook and managing your existing hooks.</li><li>Another configuration page for defining the custom data model (Klasses) in Kustomer that the source system will be mapped to.</li><li>The Workflow Builder: Workflows in Kustomer can be considered a visual programming language. The Builder is an advanced interface for building an automation triggered by POST requests to your inbound webhook to create or update objects in Kustomer, and perform other actions. A powerful and flexible engine that can be challenging for non technical personas.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oTU2s4hL76ZEQak1bZVwbA.png" /><figcaption><em>One of the steps in the wizard experience</em></figcaption></figure><p>Fortunately, Workflows built for ingesting data from another system followed a common structure. Our professional services team would consult internal documentation to guide them through creating a data ingestion Workflow, so we did have best practices documented, but setting it up was still a very manual process prone to user error. With this in mind, we were able to set our requirements for a useful prototype that we could build in a short timeframe:</p><ul><li>Consolidate the required configurations (Webhooks, Klasses, Workflow) into one wizard instead of being scattered across multiple pages.</li><li>Building a lighter version of each of the aforementioned settings pages within the wizard was a breeze since each of these resources were already stored in our global Redux state. The Redux actions and selectors for creating, updating and fetching these resources in the global state can easily be connected to our new wizard component so that all of the necessary metadata is readily available.</li><li>Our new wizard should generate a complex Workflow based on minimal user input.</li><li>As mentioned before, while these data ingest Workflows are complex, they follow a similar structure. Our wizard should be able to abstract the common patterns. In other words, the user should not have to worry about adding logic to the Workflow to account for looking up customers by email/phone, when to create an object versus update, error handling for bad data, etc. We can have the user just specify which attributes they want to map from their source system to Kustomer and our application will plug those parameters in for you to generate a robust data ingestion Workflow.</li><li>All form elements should use our existing reusable components.</li><li>We should only need to focus on creating a new component to track the form state of our wizard and handle generating the Workflow at the end. All of the form inputs in our prototype should be reusable components that we are already using in other settings pages in our platform. Having these reusable components readily available to plug into our prototype allowed for seamless communication between design and engineering while optimizing for developer velocity.</li></ul><h3>🔎 Check</h3><p>The third phase of Lean UX is to test the created artifact. In our case, we had now built a functioning prototype that would allow the user to configure actual functionality in the app. The goal here was to collectively understand the use of the prototype and potential shortcomings that we would need to improve on.</p><h4>Testing</h4><p>Building a new tool that simplifies a complicated and manual technical process for our admin users was exciting, but can also be overwhelming if we start thinking of all the possibilities of how we can extend the tool further. When considering the requirements, it was just as important for our team to set expectations and document what was out of scope for the prototype and could be addressed in future milestones.</p><p>Before we got too deep into planning the future milestones of this feature, we wanted to verify with our internal users that this minimum viable prototype saves them a significant amount of time when compared to the manual process. After our initial demo, the feedback was overwhelmingly positive and was the validation we needed to turn this prototype into a fully productized feature available to all our customers.</p><p>We even came up with new requirements while the prototype was still in progress, but also waited to validate with our internal Implementation Engineers’ feedback that we were heading in the right direction. We gathered feedback from this internal team by asking them to use our new wizard for real tasks they had to complete for clients instead of continuing with the old, manual and laborious process. It was in this phase that we tightened our feedback loop with this team by having a dedicated Slack channel and weekly video call to collect feedback and strategize around this feature.</p><h4>Iterating</h4><p>Depending on the feedback that we received, we quickly addressed it by creating a new ticket and/or adding the feedback as a line item in the product requirements document we were maintaining for this tool. Some of the new milestones included:</p><ul><li>Persisting the wizard configuration. In the prototype, we just want to prove that the wizard allows the user to easily create a complex Workflow. While being able to open up the wizard to modify an existing Workflow is a must for a GA release, we can demonstrate the value of our prototype without this requirement.</li><li>Different types of generated Workflow templates (such as mapping to Customers instead of a Custom Object). If our prototype can generate a Workflow for one use case, we should be able to adapt to other Workflow structures in the future.</li><li>Opening the wizard from a settings page. Since this was a prototype, we did not have to expose the wizard with a conventional settings page link or button. Instead, we can opt for using an obscure application route that we would only share with our internal users for testing.</li></ul><p>There were also a handful of small bugs discovered by our internal team as they used it in more real world scenarios. It was very easy to quickly fix and safely release bug fixes thanks to the continuous deployment infrastructure that we have for our web application.</p><h3>👀 Key takeaways</h3><p>Following the three phases of Lean UX: Think, Make, Check we successfully launched an impactful feature in a short amount of time. Looking back at the process, there are few important things to highlight.</p><h4>Solving problems as one team</h4><p>By bringing together the whole team throughout the process, we manage to create a shared understanding and alignment on the problem. This makes moving forward much faster as the need for documentation and alignment meetings is practically gone. Furthermore, this creates a feeling of shared ownership across functions in the team. It gives a feeling of togetherness and this enhances the collaboration even further.</p><h4>Rapid experimentation</h4><p>In addition to creating alignment, Lean UX also allows us to rapidly create artifacts that can be used for experimentation. When the focus is not on the perfect solution, but rather on the minimum viable and valuable product, we can much earlier in the process start testing our assumptions and then iterate based on the feedback received. Furthermore, as engineers, the requirements for a project or initiative may not be fully defined or even validated before it lands on our plates. A proof of concept or prototype that can be demoed to a small select group of users can be a great first step in eliminating uncertainty around the requirements.</p><h4>Design is a team effort</h4><p>Lean UX also allows everyone on the team to participate in the design process. By bringing together everyone from problem discovery to implementation, everyone on the team has a say about how to solve the problem and what solutions could get us there. In addition, the focus is less on design deliverables and more on making artifacts that can be used to validate assumptions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c0cf7cb2638" width="1" height="1" alt=""><hr><p><a href="https://medium.com/kustomerengineering/think-make-check-moving-quickly-together-1c0cf7cb2638">Think, Make, Check — Moving Quickly, Together.</a> was originally published in <a href="https://medium.com/kustomerengineering">Kustomer Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to: user story mapping workshop]]></title>
            <link>https://uxdesign.cc/how-to-user-story-mapping-workshop-448b58976ff?source=rss-68d797336a55------2</link>
            <guid isPermaLink="false">https://medium.com/p/448b58976ff</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[storymapping]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Tobias Holm Jensen]]></dc:creator>
            <pubDate>Wed, 16 Jan 2019 14:42:36 GMT</pubDate>
            <atom:updated>2019-03-11T19:00:44.267Z</atom:updated>
            <content:encoded><![CDATA[<p>If you’re a product analyst, product owner, product designer (or even a software engineer) and haven’t read the book <em>“User Story Mapping: Discover the Whole Story, Build the Right Product” </em>by Jeff Patton<em>, </em>then drop everything and read it <em>now! </em>This article is mainly useful for someone who has read the book and needs a guide to conduct a user story mapping workshop.</p><p>Introduced in 2014, user story mapping is a great tool for backlog visualization. In his book, Jeff Patton presents how and why you should create story maps to give your team a shared understanding of what you’re attempting to build and why. Story maps spark conversations and enable your team to have better conversations about the project throughout the development process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/285/1*EsdHVBgi4BDzb_qJhUXWSw.jpeg" /><figcaption>The front cover of the book (from Amazon.com)</figcaption></figure><h4>Why I created this guide</h4><p>I <em>loved</em> the book (<a href="https://amzn.to/2IlYWpN">which you can find here)</a> and I wanted to try out <em>everything</em> in it. Then, when a project for a new digital solution came up at Blackboard Insurance (where I currently work), I knew User Story Mapping would be ideal to apply. To prepare for the workshop, I had read the book, in which I had learned about the activities, the goals and outcomes. But one thing I was missing was how to actually carry it out in practice. I found very few resources online describing how to carry out user story mapping step-by-step.</p><p>This experience was very different from the first time I did a Design Sprint (<a href="https://amzn.to/2NcAk1s">you can find it here)</a>, where I easily and quickly found a bunch of excellent resources explaining how to carry it out step-by-step. Especially the free articles by the authors themselves (Jake Knapp and John Zeratsky) were very clear, straight-forward, and intuitive to follow.</p><p>Though the lack of great resources, I ended up stitching together a solid plan, I facilitated a successful user story mapping workshop, and from this I decided to publish a step-by-step guide for how to carry out a user story mapping workshop. Note: this is the first time I create a guide like this, and it is still work-in-progress and will be iterated on continuously. This means that everything is subject to change, and I would <em>love</em> your input.</p><p>Please feel free to copy, steal and claim any content from this guide as I have created it for you. ☺️</p><h3>Setting the stage</h3><p>Before your user story mapping workshop begins, you’ll need to have some important things in place. These things can take time to get set up, so make sure you have that time. Below you’ll find detailed checklists for everything you need to get done before carrying out the workshop.</p><h4>Checklist for setting the stage</h4><p>❏ <strong>Get a Decision-maker.</strong> To foster progress and decision-making in the workshop, you’ll need one person that will have the responsibility of making decisions along the way. Typically, this would be the business owner of the project.</p><p>❏ <strong>Find the right team.</strong> I’d recommend finding 7-10 people to participate in the workshop. Make sure to include people with different roles and skill sets in your organization. <em>Must-haves</em> include the product owner, business owner, an engineer, a product designer and a researcher. When you invite these people, make sure to explain why their participation is important — this will create more buy-in. <em>Tip: to complete the workshop in 1 day (about 7 hours) do not involve more than 15 people.</em></p><p>❏ <strong>Get someone with the clear vision.</strong> Ask someone from the leadership to define the long-term vision for the project. It shows your participants that your leadership is behind the project and that they consider it a priority.</p><p>❏ <strong>Pick a Facilitator.</strong> The facilitator will manage time, conversations, and the overall workshop activities. Look for someone who’s confident leading a meeting and synthesizing discussions on the fly. It might be you!</p><p>❏ <strong>If you don’t have some already — create (proto) personas.</strong> Sit down with a (UX) researcher and create a persona template based on the data you have about the users and the product. This will help get everyone aligned from the beginning of the workshop, and these personas will be vital when you start putting together the journey.</p><h4><strong>Checklist for supplies needed</strong></h4><p>❏<strong> Post-its. </strong>You’ll need lots of post-its in three different colors (I recommend purple/dark blue, light blue and yellow).</p><p>❏ <strong>Sharpies.</strong> I recommend the fine-point sharpies that are easy to read on a post-it from afar.</p><p>❏ <a href="http://amzn.to/1RyAavd"><strong>Time Timer</strong></a><strong>.</strong> For keeping time throughout the workshop. This will help visualizing how much time the participants have for each activity.</p><h3>The two parts</h3><h4>Part One: Map It All</h4><p>List the relevant users, their tasks, and what is needed to enable these.</p><h4>Part Two: Prioritize It All</h4><p>Prioritize the tasks according to the highest priority of the strategy.</p><h3>Checklist for Part One: Map It</h3><p><em>Note: the checklists are approximations. You can use them as inspiration or follow them strictly.</em></p><h4><strong>10 a.m.</strong></h4><p>❏ <strong>Introductions.</strong> If some people don’t know one another, do a round of introductions. Point out the Facilitator and the Decision-maker and describe their roles. Here, it would also be a good idea to include some kind of ice-breaker to loosen up the crowd and set the stage for creativity.</p><h4>10:20 a.m.</h4><p>❏ <strong>Explain the workshop. </strong>Describe the origin and purpose of user story mapping, the core activities and outline the process. Because it’s complex, people might not fully grasp what’s involved initially. Don’t worry if that’s the case. It will become clearer as you get into the different exercises.</p><h4>10:30 a.m.</h4><p>❏ <strong>Present the vision.</strong> Make the person you have decided to present the vision present. This is important to align the team with the outcomes, the expected value, the overall ‘why’ of the project from the get-go.</p><h4>10:40-ish</h4><p>❏ <strong>Present and rank user personas. </strong>List key (potential) users of the product. Ideally, you would use pre-made user personas from previous research (this is a big time-saver). Make sure to go over the goals and desired value for the user personas. <em>Tip: Ask the crowd if the persona descriptions lack anything. This will make them think about what they actually say.</em></p><p>After the presentation, rank the personas by priority and give each of them a different colored dot. This will be used for the later prioritization.</p><h4>11:00 a.m.</h4><p>❏ <strong>List the user tasks.</strong> To start the story mapping, ask everyone to individually write down on a post-it every step each user will take through the product — from their first touch to the point they leave. <em>Tip: keep it to 1 step per post-it and make them start with a verb.</em></p><p>❏ <strong>Organize the <em>tasks</em> into <em>activities</em>.</strong> Ask everyone to stick each post-it up on the wall in the order the personas will do the tasks (chronologically). Move duplicative or similar ideas next to one another. Look for logical groupings within your line of user tasks, collecting together all the tasks that contribute to the user achieving a wider goal. Label these groups as overall <em>activities</em> (3–5 words).</p><p>❏<strong> List the stories.</strong> Ask everyone to individually write down on a post-it everything that needs to be in place in your product to let the user achieve the goal of the activity. Each of these smaller units becomes the headline of a user story. It’s important these are written meaningfully.</p><p>❏<strong> Organize the story “stubs”. </strong>As a team, post the stubs up under the user tasks, and the wider epic, that they apply to. If there are duplicates, choose the best and stick that up.</p><p>You should have a comprehensive map by this stage. To make sure you do, get people to walk down the line to see if there are any gaps.</p><h4>1 p.m.</h4><p>Give a one-hour break.</p><h3>Checklist for Part Two: Prioritize It</h3><p>The objective of the second part is for everyone to discuss and define the minimum viable product. This is done by prioritizing all the stories into releases.</p><h4>2 p.m.</h4><p>❏ Decide which stories mainly benefit one persona and stick that persona’s dot on those stories. Straight away you can see which stories offer the most to your most valued persona.</p><h4>&gt;2:15 p.m.</h4><p>❏ <strong>Do a MoSCoW.</strong> Stick up three horizontal strips of tape across the wall. Leave room between the strips. You’ll be grouping user story post-its into swim lanes between these lines. Next we decide which stories we Must, Could, Should and Would do.</p><p>❏ Now move all the Musts above the top line of tape. While you’re at it, move all the other stories below the line, grouping them into Shoulds, Coulds and Won’ts. You can then arrange the user stories under the epic they help achieve.</p><p>❏ <strong>Define MVP.</strong> You now have your stories ranked in priority from top to bottom. At the top, the collection of Musts is your Minimum Viable Product. It’s the first thing you’ll be working on (though not the only thing). Get the team to walk along the map and make sure these Musts are all and only the stories needed to produce a cohesive, standalone product that lets customers complete enough of their goals that they’ll adopt your offering.</p><p><em>Tip: You need a ruthless focus on including only the minimum in your Minimum Viable Product.</em></p><p>This is the end of my guide. Hopefully, some of the thoughts here will help you design your own user story mapping workshop. Please let me know if there is anything missing or wrong.</p><h3>Next steps</h3><p>The user story mapping workshop is a great tool for kicking off a project. But it will only be successful if you have a clear plan for how to use these insights. These are some buckets of ‘next steps’ that you could consider to follow as well.</p><p>❏ Refine the stories and plan.</p><p>❏ Design the solution.</p><p>❏ Set up weekly reviews of designs.</p><p>❏ Start planning for development.</p><h3>Books mentioned</h3><p>User Story Mapping can be found on <a href="https://amzn.to/2IlYWpN">Amazon to about $30</a>.</p><p>Design sprint can be found on <a href="https://amzn.to/2NcAk1s">Amazon for about $30 as well.</a></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fux&amp;image=https%3A%2F%2Fucarecdn.com%2F6e8986c7-e64a-4116-9afb-fd71a476f0a9%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/a19f46680bac3cbdc42953c920d0c104/href">https://medium.com/media/a19f46680bac3cbdc42953c920d0c104/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=448b58976ff" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/how-to-user-story-mapping-workshop-448b58976ff">How to: user story mapping workshop</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>