<?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 Andrew Dunn on Medium]]></title>
        <description><![CDATA[Stories by Andrew Dunn on Medium]]></description>
        <link>https://medium.com/@iamandrewdunn?source=rss-fd7e2533055f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*DL0dETvQwWoiHE7VUrK4Wg.png</url>
            <title>Stories by Andrew Dunn on Medium</title>
            <link>https://medium.com/@iamandrewdunn?source=rss-fd7e2533055f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 09:51:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@iamandrewdunn/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[The ROI of Good Design]]></title>
            <link>https://medium.com/@iamandrewdunn/the-roi-of-good-design-c190bd921230?source=rss-fd7e2533055f------2</link>
            <guid isPermaLink="false">https://medium.com/p/c190bd921230</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[pirate-metrics]]></category>
            <category><![CDATA[ux-strategy]]></category>
            <category><![CDATA[product-led-growth]]></category>
            <dc:creator><![CDATA[Andrew Dunn]]></dc:creator>
            <pubDate>Tue, 05 Aug 2025 20:08:29 GMT</pubDate>
            <atom:updated>2025-08-05T20:08:29.137Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UcR8zgqLAOxzvI-YrfnXDQ.png" /></figure><p><strong>An overview of practical frameworks to develop UX strategy, align teams, and drive product-led growth</strong></p><p>When people find something good, they can’t keep it to themselves — they share it. Whether it’s a restaurant, TV show, life hack (you name it), we’re wired to recommend the things we enjoy. It’s deeply tied to <a href="https://en.wikipedia.org/wiki/Maslow%27s_hierarchy_of_needs">esteem</a> and the psychology of advocacy.</p><p>This basic human behavior is also the engine behind <a href="https://www.productled.org/foundations/what-is-product-led-growth">Product-Led Growth</a> (PLG). The idea is simple: if a product delivers real value quickly, users will return, build habits, and eventually promote it to others. Growth compounds when activation and advocacy are built into the experience itself. That’s the promise of PLG.</p><p>But PLG isn’t just about freemium models or viral invites. At its core, it’s about experience. It’s about reducing the time it takes for someone to go from “What is this?” to “I need this.” That’s where a product’s design becomes the differentiator.</p><p>Great design isn’t decorative. It’s strategic. It removes friction. It clarifies intent. It reduces time-to-value value. And ultimately, it unlocks a right to win and fuels growth.</p><p>What I’d like to share are a few frameworks for developing UX strategy — models to guide it, questions to shape it, and practical methods to design for delight and impact.</p><p>This is the approach I’ve come to rely on, not just to guide my own work, but to help product and design teams navigate ambiguity, build conviction, and align on user centered outcomes that drive the business forward.</p><h3>The best button is no button</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*546rUyqhAONzlEajDIYK0g.png" /></figure><p>It’s easy to think design is about how a product looks, but the deeper craft is in how it works. It’s a creative process of subtraction driven by curiosity, aimed at removing a user’s decision making process until a product feels like an extension of themselves.</p><p>You see this principle taken to its logical extreme with AI. The experience feels natural. It’s conversational. You just describe what you want, and the system interprets your intent and gets to work.</p><p>But that doesn’t mean UX disappears. In fact, it becomes even more essential. Without thoughtful structure — context, transparency, feedback, boundaries, trust — the experience loses its magic. AI apps may not rely on action-oriented interfaces, but they still require good design.</p><p>That’s why I come back to this mindset constantly in my work and with my teams. Regardless of what we’re making, the question is the same: what can we remove? And not just clicks, but complex decisions and doubt.</p><p>Because in a world where people can try another product instantly with zero commitment, speed and clarity is make or break.</p><h3>Design is all about Time-to-Value</h3><p>Design reviews are some of the most fun moments of my week. I get to be with creatives, learn, and make stuff. But that doesn’t mean they’re without challenges — especially when reviewing with stakeholders who may not have the language to describe what’s not working.</p><p>Too often, someone will describe something the team’s been working on for weeks, months, as <em>“not intuitive.” </em>It stings. But it’s best to lean into it and ask them to “<em>tell me more</em>.”</p><p>Usually, what they’re reacting to isn’t the design itself, but something deeper: a missing feature, a confusing path, unclear wording, or visual hierarchy.</p><p>In these moments I always return to <a href="https://www.researchgate.net/figure/This-easy-to-understand-model-illustrates-three-key-components-of-the-user-experience_fig2_302073931">Christian Rohrer’s Simple Model of UX</a>. It’s a framework that helps me unpack feedback and pinpoint which dimension of the user experience is actually in question.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I31y6yD1XM3_2fnE0vr0aw.png" /><figcaption>The Simple Model of UX, by Christian Rohrer</figcaption></figure><ul><li><strong>Value</strong>: Does the product do what users need it to do?</li><li><strong>Interaction</strong>: Is the path to success familiar and efficient?</li><li><strong>Content</strong>: Do the words, labels, and icons help or hinder?</li><li><strong>Appearance</strong>: Does the styling establish trust and support focus?</li></ul><p>At the heart of the model is value. It’s the centerpiece of any product experience, and ultimately a product strategy question. If the features don’t deliver what users need, then no amount of polish will make a product shiny.</p><p>But if the value is there, then everything else (interaction, content, appearance) determines how quickly users can access it.</p><p><strong>Time-to-value</strong> becomes the first real measure of any design. It can be tracked in minutes, but also in taps, clicks, or screens it takes to complete a job to be done.</p><p>Time-to-value is great because you don’t need user data to evaluate it. You can spot it in a wireframe. In a Figma prototype. In a design review.</p><p>It becomes a shared focus — one that helps teams evaluate how quickly a user can get to what they came for. You don’t need a dashboard to ask:</p><ul><li>What’s the task the user is trying to complete?</li><li>How many steps does it take?</li><li>Which steps slow them down the most?</li></ul><p>Leveraging TTV + the simple model of UX, teams can get specific about what’s working and what’s not.</p><p>It turns ambiguous feedback like “this isn’t intuitive” into something actionable. Maybe the interaction is inefficient. Maybe the value isn’t obvious. Maybe the copy needs clarity.</p><p>Time-to-value relates to all of it. It helps designers simplify with less guesswork, and it helps stakeholders engage in the conversation without needing to speak design jargon.</p><p>This is why I reference it constantly in design reviews. It doesn’t just help us discuss points of friction. It helps us agree on how important they are to address.</p><h3>An example of 1-click sharing</h3><p>To illustrate this, consider the evolution of Box’s file sharing experience.</p><p>In 2011, sharing a file meant jumping through multiple steps: selecting a share method, adjusting access settings, generating a link, and maybe doing it all again after realizing the permissions weren’t right. It worked — but there was room for improvement.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GGx3dBZh13v5IB93kkNeLA.png" /><figcaption>The 2011 Box sharing experience</figcaption></figure><p>In 2012, We streamlined the sharing options, surfaced permission settings, and tucked less used security options away. Overall, we cut the number of decisions most users had to make.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*AJhu_-2hmDG0GMsV" /><figcaption>The 2012 Box sharing experience</figcaption></figure><p>2018 brought more enhancements and a visual uplift. All options were brought to a single view, emailing links was now a thing of the past, and people no longer had to manually type (or copy/paste) email addresses to invite their co-workers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YE_1z6MXF23rqXJTV2ytPA.png" /><figcaption>The 2018 Box sharing experience</figcaption></figure><p>And lastly, users could directly copy a link from anywhere in Box (which automatically opened the sharing modal to confirm their security preferences) — shaving off one final click to value.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X3DsUKUL2jky_mdmVLR2UQ.png" /><figcaption>Image of what happens when “Copy Link” is selected when viewing a file in Box</figcaption></figure><p>Comparing the flows from 2011 to the present, it’s plain to see how much simpler the experience has become.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*msXie5LCY6OCjeo7f3oWWA.png" /><figcaption>The 2011 Box sharing flow outline</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qn3XVIUy3yPj2U69Q_IeVA.png" /><figcaption>The present day Box sharing flow outline</figcaption></figure><p>Users benefit because they can share faster, with much less effort. And here’s the kicker: sharing is one of Box’s highest-leverage points of activation + advocacy. It’s where Box demonstrates its value and encourages new users to try it. So improving this flow didn’t just make the experience better — it introduced more users to Box.</p><h3>Designing for Product-Led Growth</h3><p>Time-to-value is a simple, powerful lens. It helps teams shorten the path to success and sparks the right conversations in design reviews. But to tie UX to business outcomes in a more meaningful way, it’s important to consider every user’s journey as a conversion funnel.</p><p>For this, I like to leverage the pirate metrics framework.</p><ul><li><strong>Acquisition &amp; Activation:</strong> These early stages are about how users find your product and how quickly they reach their first moment of value. Design plays a huge role here. How clear is the setup? How fast can someone succeed? These moments shape whether users stick around.</li><li><strong>Retention:</strong> This is the measure of habit. If activation moments are repeatable and valuable, users come back. Retention is the signal of product-market fit, and it’s deeply influenced by whether the UX supports sustained success.</li><li><strong>Referral &amp; Revenue:</strong> These aren’t flows you can force — they’re outcomes. When people believe in a product, they’ll share it. When it delivers real value, they’re more likely to pay. Design still matters here, but as a catalyst, not a call-to-action.</li></ul><p>Take the prior example of Box’s sharing experience. Successfully sharing a file is a meaningful point of activation along the user journey — an “Aha” moment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6RQcUEiCYyY0ulrV3DwKtQ.png" /><figcaption>A flow highlighting activation points that mark the completion of a file sharing task</figcaption></figure><p>If we zoom out to view the user journey more broadly, we’ll see that sharing is one task among many along a journey to achieve a goal — AKA the job the user is trying to complete.</p><blockquote><em>(JTBD) As a product marketer, I would like to collaborate with my team on a blog post, so that I can publish it when we release a product.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eWeKsXi3nrq2A1TaZ0EyJQ.png" /><figcaption>A flow illustrating all the tasks (points of activation) within a job-to-be-done</figcaption></figure><p>Zooming out again from this journey to the user’s lifecycle, we see that activation sits between acquisition and retention.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fq9M_--iWNg-uBaPlUwTQg.png" /><figcaption>A flow depicting pirate metrics along a user’s lifecycle</figcaption></figure><p>If users repeatedly complete activation moments, they’re considered retained. Retained users buy and may eventually turn into champions who refer the product to others. But this isn’t guaranteed. It’s a funnel.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F9RGJR1GpisS0nCZXrehOA.png" /><figcaption>An image displaying pirate metrics as a conversion funnel</figcaption></figure><p>When we overlay these metrics with the PLG flywheel, it’s easy to see how they relate to each stage of a user’s lifecycle.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zaWUSh242TEEVAXw2UWXpQ.png" /><figcaption>An image displaying pirate metrics along the PLG flywheel</figcaption></figure><p>Lastly, when we bring it all back to the Simple Model of UX, pirate metrics offer a more complete way to understand which parts of the user experience are working and why.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CLBtxILH8ClOq852TKZ19Q.png" /><figcaption>An image of pirate metrics as they relate to the Simple Model of UX</figcaption></figure><p>Combined, these frameworks help teams know which aspect of the experience along the user journey is affecting the business. They equip everyone speak in objective, hypothesis-oriented terms, and transform a design review from subjective reactions into strategic conversations.</p><blockquote><em>(e.g.) “The 2011 sharing flow impedes a key </em><strong><em>activation </em></strong><em>moment</em><strong><em> </em></strong><em>and it could be a lot faster. The </em><strong><em>interaction</em></strong><em> takes 8+ clicks. I think all the decisions the user has to make is increasing the </em><strong><em>time-to-value</em></strong><em> when the experience should be building momentum. If we consolidate the options available in the modal, we can drive greater </em><strong><em>activation</em></strong><em>, which will lift </em><strong><em>retention</em></strong><em> and </em><strong><em>referral</em></strong><em> down stream.”</em></blockquote><p>All of this gives us the theory: the models, the metrics, and a shared language to connect user experience to outcomes. But putting it all into practice and developing a tactical product and UX strategy may still feel fuzzy.</p><p>It’s in these moments — when there’s no spec yet, just a vague idea — that I lean on a simple set of questions to guide the process and develop a story.</p><h3>Start with the story</h3><p>I think it’s natural to be idea-forward. To experience a problem and jump to a solution. For someone to pitch a feature and ask me (or someone on my team) to design it. It’s a fine place to start the discovery process — to work backwards and unpack an opportunity.</p><p>My focus is always on understanding the story.</p><p>The best product stories unfold like the ending of a home renovation show — when the host reveals the updates and the owners are in tears because all their dreams just came true.</p><p>As the camera pans across each room, we see the transformation. Flashbacks show how things looked before. And even though we just watched the whole journey, we find ourselves in disbelief, because the “before” already feels hard to imagine.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*EIMLmyITDqpcD2oa" /></figure><p>That contrast, the before and after, is incredibly powerful. It’s what we pay to see. And it’s how I encourage my teams to present their work.</p><h3>Build the strategy in layers</h3><p>To get started, I coach teams to ask a specific set of questions to help them understand the user’s current experience and build out the strategy in layers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jGd5-af0mncMxdHvX3I_Bw.png" /><figcaption>A simple layered strategic model</figcaption></figure><p>The first layer is the job to be done. What are they? (use cases). Who needs them? (personas). And how might we help them? (needs and requirements).</p><p>Next is documenting the user journey end to end. Sometimes, the journey already exists and needs to be optimized. Other times, we’re building something entirely new — requiring us evaluate the journeys of incumbent and competitive experiences.</p><p><a href="https://medium.com/@iamandrewdunn/how-to-build-frictionless-products-2750d828c5a5"><strong>A product friction evaluation</strong></a> is a great exercise to guide the process. Leveraging it offers teams a clear picture of the “before,” take inventory of the issues found, and quantify time-to-value. Along the way, it becomes easy to visualize the “after.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fjNsJ51mSYXV-glK" /><figcaption>An illustration of The Product Friction Evaluation</figcaption></figure><p>I can’t overstate the value of documenting user journeys. They’re consistently the most effective tool for helping teams align on what we’re building and why.</p><p>The storyboard format resonates — it’s visual, succinct, and reads like a movie. Each task becomes a scene, where we see the protagonist (our user) struggle, adapt, and ultimately accomplish something meaningful.</p><p>Moreover, you can’t effectively track pirate metrics, analyze funnels, or unlock Product-Led Growth without a complete view of the journey.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GHikRHdM-4TaoabwrzA1Gw.png" /></figure><p>Of course, there are more layers, questions, and tools involved in developing strategy — every project is a snowflake. But keeping the process simple is important. It gives teams a repeatable starting point and space to try their own methods.</p><h3>Good Design Delivers Business Results</h3><p>As you apply these ideas, my hope is that you’ll grow in confidence to lead and contribute to strategy at any stage, regardless of your role.</p><p>I’ve found these methods help to clear the fog of ambiguity, ask the right questions, and host conversations that shape outcomes. They offer a common ground. A shared language for discussions that build conviction.</p><p>Design is ultimately a process that forms the connective tissue teams need and a powerful accelerant for the business.</p><p>In a competitive landscape where <a href="https://s3.amazonaws.com/designco-web-assets/uploads/2019/01/The-New-Design-Frontier-from-InVision-012919.pdf?utm_campaign=Design+Maturity">less than 20% of companies</a> have data-driven design practices, good design is a strategic differentiator and growth lever. Investing in it will deliver outsized returns and ensure you’re building products people love — the ones they want to share.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c190bd921230" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How To Build Frictionless Products]]></title>
            <link>https://medium.com/@iamandrewdunn/how-to-build-frictionless-products-2750d828c5a5?source=rss-fd7e2533055f------2</link>
            <guid isPermaLink="false">https://medium.com/p/2750d828c5a5</guid>
            <category><![CDATA[user-experience-design]]></category>
            <category><![CDATA[product-led-growth]]></category>
            <category><![CDATA[workshop]]></category>
            <category><![CDATA[jobs-to-be-done]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Andrew Dunn]]></dc:creator>
            <pubDate>Mon, 22 Jan 2024 19:02:42 GMT</pubDate>
            <atom:updated>2024-01-23T02:25:32.000Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BQVxlO0_vQFLkU0mVYTKKg.png" /></figure><h3>TLDR; What is a Product Friction Evaluation?</h3><p>A Product Friction Evaluation is a team exercise that identifies points of friction along a user journey and crowdsources ideas to make a product easier, faster, and more delightful to use.</p><p>During the workshop teams review and rate all the tasks a user may complete to accomplish their goal. If a step is rated to be difficult based on what a user feels, thinks or does, then a “How might we” is added by the rater to highlight a opportunity to fix it — this statement conveniently doubles as a user story to kick-start the design process or drive further research.</p><p><strong>Total workshop time:</strong> 1–2 hours<br><strong>Resources:</strong> <a href="https://docs.google.com/presentation/d/1Sw2B6n4dRb62COe3FBTRdNksg7l6wNbWVIWzWP_Wlho/edit?usp=sharing">GSlide</a> and <a href="https://www.figma.com/community/file/1331383412727109113/product-friction-evaluation-workshop-template">Figjam</a> workshop templates</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fdocs.google.com%2Fpresentation%2Fembed%3Fid%3D1Sw2B6n4dRb62COe3FBTRdNksg7l6wNbWVIWzWP_Wlho%26size%3Dl&amp;display_name=Google+Docs&amp;url=https%3A%2F%2Fdocs.google.com%2Fpresentation%2Fd%2F1Sw2B6n4dRb62COe3FBTRdNksg7l6wNbWVIWzWP_Wlho%2Fedit%3Fusp%3Dsharing&amp;image=https%3A%2F%2Flh7-us.googleusercontent.com%2Fdocs%2FAHkbwyLnjcmOlviKeNCCxZ19vhCNSSZkm_SmWKSPiDl1n1FczcfznryN4RXvUbmO27e8a8Ey4ZRshwjU4f8-CkziW_QrOTJXKF8T6Izx5ijyq4AfrOk%3Dw1200-h630-p&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=google" width="700" height="559" frameborder="0" scrolling="no"><a href="https://medium.com/media/52d7a69f41949710a8aae49aa858a0f9/href">https://medium.com/media/52d7a69f41949710a8aae49aa858a0f9/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.figma.com%2Fembed%3Fembed_host%3Doembed%26url%3Dhttps%3A%2F%2Fwww.figma.com%2Ffile%2FMiaOFht59E3aWQQNzChtJs%2F%255BTEMPLATE%255D-Product-Friction-Evaluation-Workshop%3Ftype%3Dwhiteboard%26node-id%3D0%253A1%26t%3DervKE34sWjMtk9Fl-1&amp;display_name=FigJam&amp;url=https%3A%2F%2Fwww.figma.com%2Ffile%2FMiaOFht59E3aWQQNzChtJs%2F%255BTEMPLATE%255D-Product-Friction-Evaluation-Workshop%3Ftype%3Dwhiteboard%26node-id%3D0%253A1%26t%3DervKE34sWjMtk9Fl-1&amp;image=https%3A%2F%2Fapi-cdn.figma.com%2Fresize%2Fthumbnails%2Fbf64df55-2ca5-4762-bbcb-4f221c1273ad%3Fheight%3D435%26bucket%3Dfigma-alpha&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=figma" width="800" height="450" frameborder="0" scrolling="no"><a href="https://medium.com/media/25a7b43046c9154d1e84160072365119/href">https://medium.com/media/25a7b43046c9154d1e84160072365119/href</a></iframe><h3>Why I love this exercise</h3><p>Over the course of my career I’ve led dozens of creative exercises and workshops to help teams align, collaborate, and develop product strategy. And of all the artifacts produced throughout the creative lifecycle, I’ve found user flows to be the most critical in helping people understand, <strong>“<em>What are we building and why</em>?”</strong></p><p>The storyboard format of a user journey is visual, succinct, and plays like a movie… each task is a scene, we observe the protagonist struggle and grow in the face of challenges, and in the end they accomplish something meaningful.</p><p>The Product Friction Evaluation is a type of journey mapping exercise that enables teams to evaluate a user’s story end-to-end as a funnel. It helps teams navigate the ambiguity of the<a href="https://www.nngroup.com/articles/discovery-phase/"> discovery and definition phase</a> of the creative lifecycle to define product strategy and prioritize requirements, because the ROI from good UX becomes plain to see.</p><h3>How is this workshop different from others?</h3><p>The Product Friction Evaluation is a Zoom-friendly workshop that blends multiple design thinking exercises together, most notably <a href="https://www.nngroup.com/articles/pure-method/">PURE</a> (Pragmatic Usability Rating by Experts).</p><p>It can be used to measure any product experience, doesn’t require a lot of up front user research, garners team alignment, produces constructive tactical outcomes, and only takes 1–2 hours.</p><p>During the exercise teams are oriented around a user and each task they must complete to accomplish their objective, and mark opportunities that would accelerate the user’s time to value.</p><p>Task success, the speed at which users can complete an activity with confidence, is critical in driving product adoption, retention, and advocacy. If tasks are easy to accomplish then users will be more likely to build sustained habits with a product.</p><p>In other words, PFE can help tighten<a href="https://www.nirandfar.com/how-to-manufacture-desire/"> Habit Loops</a>, make “<a href="https://www.appcues.com/blog/aha-moment-guide">Aha Moments</a>” easier to reach, and increase <a href="https://www.productled.org/foundations/what-is-product-led-growth">Product-Led Growth</a>.</p><h3>How does it work?</h3><p>To identify points of friction along a user journey, workshop facilitators need to provide participants with a job to be done, a user scenario, and a screenshot flow detailing every decision (click or tap) a user makes to complete their tasks and accomplish their goal.</p><p>Setup for the workshop doesn’t require specialization — <strong><em>anyone can do it!</em></strong></p><p>👉 Here’s a <a href="https://www.figma.com/community/file/1331383412727109113/product-friction-evaluation-workshop-template"><strong>Figjam workshop template</strong></a><strong> </strong>to help you get started.</p><h4>Step 1 — Identify a Job To Be Done</h4><p>The first thing that needs to be settled is the<a href="https://hbr.org/2016/09/know-your-customers-jobs-to-be-done"> Job To Be Done</a> — the primary reason someone would “employ” your product. Maintaining focus on the Job To Be Done vs isolated tasks enables teams to consider the user’s end-to-end journey, which may involve other products and services. Doing so will help teams consider opportunities and synergies to optimize the entirety of a user’s workflow and further differentiate your solution.</p><p>For example, I used Notion to draft this article. However, my goal wasn’t to draft an article, it was to publish one. Drafting the article was one of many tasks along my journey to achieve the goal.</p><blockquote>As a <strong><em>design leader at a software company</em></strong>, I need to <strong><em>write, format and publish articles</em></strong>, so I can <strong><em>share ideas that have helped my team</em></strong>.</blockquote><h4>Step 2 — Define a user scenario</h4><p>Who the user is and their motivations, needs, limitations, and past experience will shape their expectations and decision making process using your product. For example, if a user is familiar with a competitive product they may experience greater cognitive load if your product works differently.</p><p>If you have personas, pick one and base your scenario off of it. Otherwise, define one yourself with the information you have on hand. The definition of your target user doesn’t need to be perfect, it only needs to provide your team with a lens in which to view their journey.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QRb7wVvM6NtJhDIf" /><figcaption>Example persona</figcaption></figure><p>I’ve found it most helpful to evaluate the first time user experience. Teams are often so familiar with their product that they unconsciously overlook: areas where the product isn’t guiding, confusing information architecture, non-standard interaction patterns, and workarounds.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*K63YBD2D-zOeUDYt" /><figcaption>Example “Job To Be Done” scenario</figcaption></figure><h4>Step 3 — Map the user flow</h4><p>There are seven general stages in a user journey:</p><ol><li><strong>Awareness</strong> — Prospective users discover your product exists.</li><li><strong>Consideration </strong>— Prospective users learn more about your product.</li><li><strong>Evaluation</strong> — Trial users test your product and compare with their existing solution.</li><li><strong>Purchase</strong> — Users convert to customers.</li><li><strong>Onboarding</strong> — Users learn more about product capabilities and how to best use it (may happen prior to purchase).</li><li><strong>Retention</strong> — Users continue to engage with your product with frequency.</li><li><strong>Advocacy</strong> — Users invite, champion, or recommend your product to others.</li></ol><p>You may define your users’ journey differently, but it’s helpful to remember that they always start as strangers and should mature to advocates.</p><p>It’s also ok to omit stages if you feel they aren’t worth evaluating. For example, if your goal is to review a product experience, you might exclude preceding marketing or e-commerce conversion flows.</p><p>Lastly, you may want to only focus on the happiest, simplest, or most likely path a user would take to complete their objective. Evaluating less common paths and error scenarios will increase overall effort.</p><h4>How to map a flow</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jqIkI9flGNo9gavU7sVS5g.png" /></figure><ol><li><strong>Add screenshots</strong> — Choose a starting point and take screenshots of each decision and click/tap required to complete the job to be done.</li><li><strong>Add descriptions </strong>— Include a sentence describing what the user is doing at each step in the flow as it might not be obvious with a static image.</li><li><strong>Add task sections </strong>— Once all the steps have been captured, chunk the flow into discrete tasks and add an avatar to each task section to indicate who’s involved.</li><li><strong>Add details</strong> — (Optional) Tag specific steps in the flow to call out “Aha movements” or relevant insights (e.g. user quotes or click flow data) to better equip participants to evaluate the user journey.</li></ol><h3>Running the workshop</h3><h4>Part 1 — Independent Evaluation</h4><p>Participants are to spend the first half of the workshop reviewing the user scenario and flow independently. The idea is for them to put on the lens of the user and take a walk in their shoes.</p><p>During the independent evaluation, direct participants to internalize an<a href="https://www.nngroup.com/articles/empathy-mapping/"> empathy mapping exercise</a> and rate each step.</p><p>“Ask yourself, ‘What would the user say, think, feel, or do at each step?’ And based on these considerations, rate on a scale of 1–3 how difficult it would be for the user to complete it and move forward.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aCVsDezQI77fdDzWX-ULzQ.png" /></figure><p>If a step is rated as a 2 or 3, direct participants to add a “How Might We” comment. I find HMW statements do a great job at highlighting the problem and opportunity in the most succinct way. They can also double as a user story and be repurposed in a product spec.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UfOvGjEPVr3slUvVQ0PJxQ.png" /></figure><h4>Part 2 — Group Discussion</h4><p>After everyone has had an opportunity to complete their evaluation, zoom out to view the journey at a glance. The rating markers will create a heat map of UX issues and it should be easy to observe areas where the team is most aligned.</p><p>To initiate the discussion, start at the first step with a yellow or red marker. Review the HMW statements, add notes and continue forward in sequence.</p><p>If you are low on time, focus on the steps that look the most severe or keep it open ended — “What steps and issues stood out to you the most?”</p><h3>Wrap up</h3><p>After a healthy discussion I find it best to thank everyone, share high-level next steps, and let ideas breathe. I’m also a fan of summarizing the results of the exercise and allowing cross-functional leads to make progress on follow up activities async to reduce overall effort.</p><h4><strong>Next Steps:</strong></h4><ol><li><strong>Prioritize opportunities</strong> — Use the ratings heat map to prioritize the most critical “How might we…” statements and draft hypotheses.</li><li><strong>Review behavioral data</strong> — Evaluate click-flow analytics (or instrument the flows) to measure task success and drop offs along the funnel.</li><li><strong>User test the flow</strong> — Observe people using your product to validate the issues identified and plot new ones along the flow (this is a living artifact after all).</li><li><strong>Evaluate competitors</strong> — Map competitive flows and compare scores.</li><li><strong>Start concept design</strong> — <a href="https://www.nngroup.com/articles/user-story-mapping/">Draft an ideal user flow</a> to capture the next level of requirements, or try<a href="https://designsprintkit.withgoogle.com/methodology/phase3-sketch/solution-sketch"> solution sketching</a>.</li><li><strong>Compare the before and after</strong> — Use the flow and score from the exercise as a baseline to compare improvements. The first objective should be to reduce the number of red and yellow areas, and the second is to reduce the total number of steps involved. It’s better to add a step if it will reduce the difficulty of another than eliminate a step if it adds more cognitive load.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i6Gr39vT4V4vfNsHuPP4HA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2750d828c5a5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>