<?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 Sara Hill on Medium]]></title>
        <description><![CDATA[Stories by Sara Hill on Medium]]></description>
        <link>https://medium.com/@sarashill?source=rss-b22ac90885dd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*KP0OINw3ZvLT9Bql.</url>
            <title>Stories by Sara Hill on Medium</title>
            <link>https://medium.com/@sarashill?source=rss-b22ac90885dd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 02:31:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sarashill/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[A map for uncovering your assumptions]]></title>
            <link>https://medium.com/@sarashill/a-map-for-uncovering-your-assumptions-15f1eb02ea2a?source=rss-b22ac90885dd------2</link>
            <guid isPermaLink="false">https://medium.com/p/15f1eb02ea2a</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[journey-mapping]]></category>
            <dc:creator><![CDATA[Sara Hill]]></dc:creator>
            <pubDate>Wed, 26 May 2021 15:26:09 GMT</pubDate>
            <atom:updated>2021-05-26T15:26:09.330Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="An illustration showing a remote meeting conference call with four people in their home environments all looking at a flow diagram. One person is pointing to it, one is holding their thumb up, one person is holding the diagram, and the other is looking thoughtfully." src="https://cdn-images-1.medium.com/max/1024/1*lR8y4gbsdhPf5Nfq_OQO8A.png" /><figcaption>Illustration by Alek Mackie.</figcaption></figure><h4>How I use journey mapping to align teams before they begin</h4><p>Mapping the <a href="https://ux.shopify.com/user-journeys-should-feel-invisible-293381711589">user’s journey</a> is the first step to understanding a user’s world. Journey mapping is a key UX exercise to help teams work through their assumptions, understand user context and needs, and identify opportunities for improvement.</p><p>Earlier this year, I connected with Shopify’s Channels team to help them run a journey-mapping workshop to benchmark their assumptions and practice. I’m going to share my lessons learned and the templates we used because a few shifts in how you plan and run a journey-mapping workshop can lead to much more actionable outcomes.</p><h4><strong>Experience foundations</strong></h4><p>First, it’s useful to know we conducted our journey-mapping exercise within our framework of experience foundations, which break down user problems into modular, interconnected elements.</p><p><a href="https://polaris.shopify.com/">Polaris</a>, Shopify’s design system, encourages teams to focus on experiences first. Although many people associate a design system with code and UI components to ensure consistency, our Polaris team is trying to break that paradigm and encourage teams to focus on experiences first instead.</p><p>So, at Shopify, when we talk about <a href="https://ux.shopify.com/why-design-systems-need-experience-foundations-c5a6967fc4e7">experience foundations</a> we’re talking about:</p><ul><li><strong>Journeys</strong>, the steps users take when they interact with Shopify to do a job</li><li><strong>Context</strong>, the circumstances surrounding a user: the who, what, where, and how</li><li><strong>Factors</strong>, the changing conditions shared across experiences that impact a design</li></ul><p>We encourage teams to start by mapping their user’s journey. By understanding the various touchpoints a user has within and out of Shopify, teams can start to understand how one decision they make for their product area impacts other product areas, and how the user moves through them.</p><p>Journey mapping gives teams an opportunity to step back, see the whole picture, and grow their systems thinking skills.</p><figure><img alt="Circular model showing describing context, the journey, and the factors that make up Shopify’s experience foundations" src="https://cdn-images-1.medium.com/max/1024/0*nZA_GAEANAProy_F" /></figure><h3>Identifying the need for a journey map</h3><p>The Channels team was focusing on a project to enable <a href="https://developers.shopify.com/">external development partners</a> to design and build end-to-end merchant and buyer sales channel experiences.</p><p>The team’s goal was to better understand the development partner’s pain points, so they could see where they were aligned and where there were gaps before jumping to a solution. Since the team was moving fast, and they had a tight deadline they needed to meet, they needed a way to check that the product they were each designing individually was adding up to a quality end-to-end experience. We decided to run a journey-mapping workshop to help the team identify opportunities and align around a shared vision.</p><h3>Planning the workshop</h3><p>We planned our workshop to include mapping of the current and future state, clustering and themes, and reflections.</p><p>Since Shopify employs people all over the world, we held the workshop virtually over Google Meet. With the workshop being remote, it was important to be organized and plan everything out so that the group could focus on the work at hand and not get distracted with technology hurdles.</p><p>Keeping a few key principles in mind kept us on track.</p><p><strong>Be intentional with tool choice. </strong>I originally set up the workshop in Figma but realized that not everyone has edit access, and there can be a bit of a learning curve. I chose Miro as an alternative because everyone at Shopify has access and it’s easy for anyone to learn on the fly.</p><p><strong>Include the right people.</strong> We ran the workshop with a cross-disciplinary group of 8 people that work on different aspects of Channels. Having a diverse, cross-disciplinary group ensures unique perspectives and viewpoints across the journey; each discipline brings different perspectives and considerations to the work that are valuable to consider.</p><p><strong>Identify stages in advance. Or don’t. </strong>“Stages” is the row at the top of the journey map that represents each stage of the journey. I worked with my co-facilitator, staff product designer <a href="https://veronicawong.ca/">Veronica Wong</a>, to define some stages before the workshop so the group had a place to start.</p><p>We let the group know at the beginning of the workshop that these stages could change based on what we came up with for the other pieces of the map.</p><h3>Running the workshop</h3><p>Even with the best foundations in place for a great workshop, it’s important to guide the discussion, keep everyone engaged, and provide time to reflect. Here’s my advice to do exactly that:</p><p><strong>Re-define the journey stages at the start of the workshop. </strong>While we defined the stages before the workshop, we ended up renaming a stage and removing another during the workshop. But, by failing to call out each stage to define and agree what each meant at the beginning, we delayed identifying these gaps.</p><p>Stages we defined before the workshop:</p><ul><li>Discover</li><li>Learn</li><li>Try</li><li>Use</li><li>Seek support</li><li>Extend</li><li>Maintain</li><li>Deprecate</li></ul><figure><img alt="The stages of the journey that were defined prior to the workshop" src="https://cdn-images-1.medium.com/max/1024/0*XkRzBXeanZroCXFW" /><figcaption>The stages of the journey that were defined prior to the workshop.</figcaption></figure><p>Stages we settled on during the workshop:</p><ul><li>Discover</li><li>Learn</li><li>Build</li><li>Seek support</li><li>Extend</li><li>Maintain</li><li>Deprecate</li></ul><figure><img alt="The stages of the journey after the group made adjustments" src="https://cdn-images-1.medium.com/max/1024/0*0JndztL09xZg0tsv" /><figcaption>The stages of the journey after the group made adjustments.</figcaption></figure><p>Stages can be distracting. It was useful to set the stages beforehand as a starting point but it also caused folks to focus on what was there and made it a little harder to think about any unrepresented stages. We uncovered this by probing and asking questions about gaps we were starting to see:</p><ul><li>As participants are filling out the map, look for stages on the map where there are fewer sticky notes. You can use this as a flag for possible gaps in knowledge. Ask open-ended questions to the group to dig deeper.</li><li>Look across the map as a whole and see if the sticky notes at each stage feel like an end-to-end experience. This will help you start to identify if a stage is missing.</li></ul><p><strong>Understand the current state — and imagine the future. </strong>It was important to have the team map the current state of the development partner’s journey to gain alignment and identify areas of opportunity, but it was equally important to take time to imagine the ideal state, too.</p><p>For the future state map, the group picked one key pain point from the current state to focus on. By focusing on one pain point, we were able to see how changing that one aspect affected later stages in the journey.</p><figure><img alt="Current state map showing major pain points and themes in the development partners journey." src="https://cdn-images-1.medium.com/max/1024/0*vv4AlpgRt3blE1Z-" /><figcaption><em>Current state map showing major pain points and themes in the development partners journey.</em></figcaption></figure><p>Through grouping and dot voting, we saw that a lot of the pain points were earlier on in the process. The lack of documentation, examples, and guidance resulted in a lot of confusion and increased questions to Support.</p><figure><img alt="Future state map with a focus on clear documentation and guidance" src="https://cdn-images-1.medium.com/max/1024/0*NcLhpz0wUJOnsFd6" /><figcaption><em>Future state map with a focus on clear documentation and guidance.</em></figcaption></figure><p>In the future state, the group focused on what the journey might look like if there was clear documentation, examples and guidance. As a result, we started to see a lot more sticky notes focused on positive emotions like: “excited” and “pride”. Seeing what the future could look like created a sense of energy within the team.</p><p>After the cluster step of the current-state mapping, I ended up pausing a bit longer so everyone had an opportunity to voice their thoughts and perspectives.</p><p><strong>Baking in time for reflection is important.</strong> I found that I had planned out the workshop with a lot of tasks for the group to complete within a pretty tight timeline. The entire workshop was initially scheduled into 2 two-hour time slots. There was some allocated time to reflect, but I’d only allotted about 10–15 min during each session.</p><p><strong>Prompt further discussion with thoughtful questions.</strong> Since the group was made up of people with deep knowledge of different aspects of the journey, we wanted to keep everyone together to facilitate a deeper conversation and build alignment. This meant we, as facilitators, needed to really guide the conversation through thoughtful questions and be prepared to take the time needed to dig into any topics that individuals needed more clarity around.</p><p><strong>Keep the conversation flowing.</strong> “Popcorning” is a good way to start the conversation. One person starts the discussion off by sharing a thought and then selects another person in the group to add on and share any thoughts or insights they have. I prefaced this activity with: “you don’t have to share if you don’t want to”, so people didn’t feel too put on the spot.</p><p><strong>Try co-facilitation. </strong>I hadn’t co-facilitated a workshop before but it was great. I found that my co-facilitator was really strong at keeping folks on track and adjusting to the room. I was able to jump in and have the group pause, and take time to slow down when needed.</p><p><strong>Be open to adjusting the plan. </strong>Since we decided to pause and make space for more discussion and reflection, we didn’t have as much time as planned for the future state mapping. We adjusted by skipping the clustering and themes, and went straight to the reflection.</p><p>The group focused on talking about the vision and what would be nice-to-have versus non-negotiable for that journey to come true. Since team alignment was actually more important of an outcome than any documented deliverable, we focused on ensuring there was space and time for people to reflect and internalize the journey we were working through. It was more important for people to get a chance to break free of their different roles and perspectives, and see things through the eyes of their users.</p><p><strong>Have real users join for part of the workshop. </strong>We didn’t invite development partners — the real users of the Channels products — to the session, so a lot of what we came up with was assumption-based instead of research-based. This was partly due to timing, but also, this exercise alone was a great way to prepare the team for running their own user workshop in the future. It also kept the team focused on benchmarking their own assumptions first.</p><p>Having participating users would give the team more confidence that the outcome of the journey map was an accurate representation of the users’ experience.</p><p>Overall, the workshop went really well and helped the team see where they were aligned and where there were gaps. What’s more, the team now has the skills and framework to run another workshop with users in the future, and is fully-equipped with an aligned team, benchmarked assumptions, and an ideal state.</p><p>For any teams that are struggling with alignment and prioritization, I’d recommend journey mapping as a really valuable exercise.</p><p><em>If you’re interested in reading more, find out </em><a href="https://ux.shopify.com/assumption-slam-how-not-to-make-an-a-out-of-u-and-me-2d9012c105a0"><em>how UX research can use an assumption slam and mapping to help product teams</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15f1eb02ea2a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>