<?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 Penny Marsh Collisson on Medium]]></title>
        <description><![CDATA[Stories by Penny Marsh Collisson on Medium]]></description>
        <link>https://medium.com/@pennymarshcollisson?source=rss-7b414007ddb------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*o-MuEtmPNV7LF2lMrKFtsg.jpeg</url>
            <title>Stories by Penny Marsh Collisson on Medium</title>
            <link>https://medium.com/@pennymarshcollisson?source=rss-7b414007ddb------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 11:18:02 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@pennymarshcollisson/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[User Research Makes Your AI Smarter]]></title>
            <link>https://medium.com/microsoft-design/user-research-makes-your-ai-smarter-70f6ef6eb25a?source=rss-7b414007ddb------2</link>
            <guid isPermaLink="false">https://medium.com/p/70f6ef6eb25a</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[microsoft]]></category>
            <category><![CDATA[research-and-insight]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Penny Marsh Collisson]]></dc:creator>
            <pubDate>Mon, 01 Jul 2019 16:29:03 GMT</pubDate>
            <atom:updated>2019-07-01T19:49:09.953Z</atom:updated>
            <content:encoded><![CDATA[<h4>Some things we’re learning about doing UX research on AI at Microsoft</h4><p>By <a href="https://medium.com/u/7b414007ddb"><em>Penny Marsh Collisson</em></a><em> and </em><a href="https://medium.com/u/c6a984b9d30c"><em>Gwenyth Hardiman</em></a><em>, illustrations by </em><a href="https://medium.com/u/95740bc97010"><em>Michaelvincent Santos</em></a><em>.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*wV8ut4NSmq4SPKoe8I7e3A.png" /></figure><p>As AI grows more prevalent, it’s changing what people expect from technology and how they interact with it. That means that every UX-er and customer-obsessed product person needs to consider not only how to <a href="https://medium.com/microsoft-design/ai-guidelines-in-the-creative-process-807b6d31cda2?source=friends_link&amp;sk=a942f71c0ca9ccc5129687cdd1042fb7">create effective AI experiences</a>, but also how to collect customer feedback along the way. Easy…right?</p><p>The good news is that many traditional research tools can help gauge customer reactions to AI. Ethnographies, focus groups, prototype research, customer surveys, and logs are all still relevant. <strong>However, AI systems differ from classical systems in that they’re context aware, personal, and able to learn over time. They also have limited accuracy and unique failure modes. </strong>These things introduce new challenges and opportunities when researching the UX of AI.</p><p>Today we’ll share practical tips for researching the UX of AI that we’ve learned along the way at Microsoft.</p><h3>Diversify your recruit</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*H8iNXnWSQShYlKOsPar4cw.png" /></figure><p>As UX-ers, it’s our responsibility to ensure that the experiences we deliver embrace diversity and respect multiple contexts and capabilities. That’s especially important with AI. If your AI UX is only usable for a subset of users, potentially harmful bias will creep into your AI models. <strong>An arbitrary sample of participants, or even a split on basic demographics like gender and age, will not be enough to ensure your AI is inclusive.</strong></p><p><em>Even during early feedback stages, recruit for a wide array of characteristics such as these:</em></p><ul><li>Attitudes toward AI and privacy</li><li>Profiles of tech adoption</li><li>Levels of tech self-efficacy</li><li>Geographies</li><li>Social contexts and norms</li><li>Physical, cognitive, or emotional abilities</li></ul><h3>Fake it till you make it with Wizard of Oz techniques</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*m7UzdfKmtcmF_7cg7QPmNA.png" /></figure><p>During early prototyping stages, it can be hard to get a good read on how your AI is going to work for people. Your prototype might be missing key functionality or interactivity that will impact how participants respond to the AI experience.<strong> </strong><a href="https://en.wikipedia.org/wiki/Wizard_of_Oz_experiment"><strong>Wizard of Oz studies</strong></a><strong> have participants interact with what they believe to be an AI system, while a human “behind the curtain” simulates the behavior that the AI system would demonstrate.</strong> For example, a participant might think the system is providing recommendations based on her previous selections when a person in another room is actually providing them. When people can earnestly engage with what they <em>perceive</em> to be an AI, they will form more complete mental models, while interacting with the experience in more natural ways.</p><h3>Integrate people’s real stuff into your AI prototype</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*U3QuHcBl2xFCY02QcgVHNQ.png" /></figure><p>If study participants see generic content, their reactions may mislead you. <strong>People respond differently when the experience includes their real, personalized content such as photos, contacts, and documents.</strong> Imagine how you feel about a program that automatically detects faces in photographs. Now, imagine seeing the faces of your loved ones identified by the system. Your reaction may be very different when you see people you know. You’ll need to spend extra time pre-populating <a href="https://medium.com/microsoft-design/prototyping-empathy-1bdb08e3260c?source=friends_link&amp;sk=e50262550f8cef53fe7b4c7a557bdf40">your prototype</a> with people’s “real” content, but it will be worth the effort.</p><h3>Reference a person instead of an AI</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*KKo0hhdhYSsnituz1tiJcA.png" /></figure><p>AI has a lot of hype and folklore around it. For that reason, referencing AI can cue participants to make certain assumptions — both good and bad — about their experience. For example, participants might key in on highly publicized stories of bias or failure in AI systems. Or they could assume AI is more capable and perfect than it will ever be. <strong>Getting participants to think about how a </strong><a href="https://medium.com/@jdlovejoy/human-centered-ai-cheat-sheet-1da130ba1bab"><strong>human could help them</strong></a><strong> can be a good way to glean insight about where AI can be useful.</strong></p><p><em>Here are some alternatives to talking about AI:</em></p><ul><li>Invite participants to share how they currently enlist other people to achieve their goals.</li><li>Ask participants how they would want a human expert to behave.</li></ul><h3>Understand the impact of your AI getting it wrong</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*H9SlDkDlIdai0XCu1mjjSQ.png" /></figure><p>AI isn’t perfect. It’s probabilistic, fallible, and will make mistakes. Especially early in the design cycle, it can be easy to create perfect prototypes and get an overly optimistic response to your UX. While planning evaluations, build in realistic quirks or pitfalls to bridge the gulf between the shiny concept and realistic product execution. <strong>Once you understand how your AI’s failure modes impact people, you can design to mitigate their impact.</strong></p><p><em>Here are a few methods to consider:</em></p><ul><li>Intentionally introduce things into your prototype that are likely to be “wrong.”</li><li>Ensure that system interactions in your Wizard of Oz studies <a href="https://www.microsoft.com/en-us/research/uploads/prod/2019/02/Sketching-NLP.pdf">include different kinds of errors</a>.</li><li>Take participants down different paths: things are right, a little right, a little wrong, totally wrong.</li><li>Invite conversation about where failures would be most impactful to their experience.</li></ul><h3>Dive into mental models</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*BqDhPj236dVbEg1VY-JeNA.png" /></figure><p>People don’t need to understand the nuts and bolts behind the technology powering AI to have a positive experience with it.<strong> But they need a mental model of the system — what it delivers, when, and why — to have realistic expectations of the system’s capabilities.</strong> It can be easy to assume that people correctly understand how your AI works, when frequently their understanding is wrong (even if they’re confident about it!). Once we locate the gaps in people’s mental models, we’re better equipped to shore them up with our designs.</p><p><em>To understand how participants envision your AI system, try this:</em></p><ul><li>Ask participants to write down the “rules” for how the system works. For example, give them a result and ask them to explain why and how the system produced it.</li><li>Have participants imagine that a human gave them a specific result. Ask what it is about the data, or their interactions, that would have caused the human to give them that result.</li></ul><h3>Highlight exceptions as well as trends</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*fbY9EBYxXcD9j8cV9Ps_Iw.png" /></figure><p>People will have different experiences with an AI depending on their context, the content they bring in, and the way they interact with the system. <strong>There are challenges with extracting qualitative insights around AI systems based on what <em>most</em> people do, or how they react, when every person’s experience is so personal.</strong> As you roll up results, pay close attention to outliers. Understand why participants had the unique experience they did within your sample. This is particularly important when evaluating the experience across a diverse audience.</p><h3>Talk with us</h3><p>These are ideas we’ve been recommending to other people researching AI, but we’re sure there are other ideas out there. What do you think? What did we miss? We’d love to hear about your experiences. Please share them in the comments. You can also catch <a href="https://www.linkedin.com/in/pennycollisson">Penny</a>, <a href="https://www.linkedin.com/in/gwen-hardiman-00a1b4133/">Gwen</a>, and <a href="https://www.linkedin.com/in/michaelvincent-santos-2244263/">Michaelvincent </a>on LinkedIn.</p><h3>Authors</h3><p><a href="https://medium.com/@gwenyth.hardiman">Gwenyth Hardiman</a> is a user researcher working on AI in Office.</p><p><a href="https://medium.com/@michaelvincent.mvcms">Michaelvincent Santos</a> is a designer working on collaboration in Office.</p><p><a href="https://medium.com/@pennymarshcollisson">Penny Collisson</a> is a user research manager working on AI in Office.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*1tIygvWQrYoY2FXyDRhq-w.png" /></figure><p><em>With special thanks to Trish Miner, Erin Wilcox, Joline Tang, Thomas Dunlap, Paul Scudieri, Sara Bell, Brandon Haist, Jared LeClerc, Andrew Lambert, Joshua Tabak, and Nitya Nambisan for their teamwork and contributions.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=70f6ef6eb25a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/microsoft-design/user-research-makes-your-ai-smarter-70f6ef6eb25a">User Research Makes Your AI Smarter</a> was originally published in <a href="https://medium.com/microsoft-design">Microsoft Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI Guidelines in the Creative Process]]></title>
            <link>https://medium.com/microsoft-design/ai-guidelines-in-the-creative-process-807b6d31cda2?source=rss-7b414007ddb------2</link>
            <guid isPermaLink="false">https://medium.com/p/807b6d31cda2</guid>
            <category><![CDATA[research-and-insight]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[microsoft]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Penny Marsh Collisson]]></dc:creator>
            <pubDate>Thu, 07 Mar 2019 16:04:55 GMT</pubDate>
            <atom:updated>2019-03-07T18:22:21.915Z</atom:updated>
            <content:encoded><![CDATA[<h4>How we’re putting the Human-AI Guidelines into practice at Microsoft</h4><p><em>By Penny Collisson, Saleema Amershi, Mihaela Vorvoreanu. Illustrations by Michaelvincent Santos.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*Fr3cJxVNWve24RtpnZPmPA.png" /></figure><p>We recently published <a href="https://medium.com/microsoft-design/guidelines-for-human-ai-interaction-9aa1535d72b9">the Guidelines for Human-AI Interaction</a>. These eighteen guidelines represent best practices for AI design. They provide guidance on how to create meaningful AI-infused experiences that leave users feeling in control, and respect their values, goals, and attention. For example, they prompt us to <em>make clear how well the system can do what it can do</em> (guideline 02) and <em>make clear why the system did what it did</em> (guideline 11) to help users navigate AI-infused experiences that may be <a href="https://uxdesign.cc/a-peoples-bill-of-rights-for-personalization-9148dc7d8291">inaccurate</a>.</p><p>In the Microsoft Office product group, we’ve started to build these guidelines into our work. <strong>For example, our teams perform </strong><a href="https://uxdesign.cc/heuristic-analysis-for-ux-how-to-run-a-usability-evaluation-12c86d43936f"><strong>heuristic evaluations</strong></a><strong> using a handy deck of </strong><a href="https://www.microsoft.com/en-us/research/uploads/prod/2019/01/AI_Guidelines_Cards_PrintQuality.pdf"><strong>AI guideline cards (with examples)</strong></a><strong> we created for the guidelines.</strong> We shape usability tasks and discussion guides with the guidelines in mind. We use the guidelines to bolster our case when sharing back research findings.</p><p>We recently started to explore how the guidelines can play a role throughout the entire design process. That is, can the guidelines <em>inspire</em> creative and human-centered thinking, in addition to being a tool for product evaluation and refinement? If so, how? Today we’ll share a few ideas.</p><h3>#1. Decide on a few guidelines to rally around.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*juGDZXz-3J002iWCyn8qHw.png" /></figure><p>Focusing on eighteen guidelines at once may seem like a daunting task. It also might not invoke the creative mindset you’re after in early design stages. So, consider ways to bring focus:</p><ul><li>Agree on a few guidelines that are most important for your experience. <em>Time services based on context</em> (guideline 3), for example, might be especially relevant for experiences that include notifications.</li><li>Pick one of the <a href="https://medium.com/microsoft-design/guidelines-for-human-ai-interaction-9aa1535d72b9">four guideline categories</a> (i.e., Initially, During Interaction, When Wrong, or Over Time) to ideate around first.</li><li>Assign sponsors to different guidelines. Ask those people to be on the lookout for new opportunities or violations, and to track what they observe in the product backlog.</li></ul><p>The key is that you can create a different mindset simply by managing attention in creative ways.</p><h3>#2. Explore (don’t avoid) violations.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_76WlbGG6LnOWFKD6eGv-w.png" /></figure><p>It’s natural to want to brush aside guidelines you <em>aren’t</em> intending to follow. After all, things that might go wrong are stressful, and stress is the <a href="https://medium.com/attack-the-front/stress-is-the-enemy-of-creativity-bc642639749b">enemy of creativity</a>. Instead, explore violations. Doing so can help your team think outside the box. Try the following:</p><ul><li>Decide on a few guidelines to set aside or even deviate from and discuss why you will do that.</li><li>Outline the range of feedback you might hear. For example, what’s the worst and best feedback you might expect if your AI doesn’t <em>remember recent interactions</em> (guideline 12). How would you optimize the design in response to that feedback?</li><li>Do research with products on the market that violate different guidelines. For example, identify products that don’t <em>mitigate social biases</em> (guideline 06). Watch what people do, understand how they feel, and listen to what they ask for.</li></ul><p>Actively exploring violations might unlock new and creative ideas.</p><h3>#3. Mash up different approaches in design jams.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*GcONzRCUd1O1puUKdqU63g.png" /></figure><p>Design jams can be an awesome way to get a breadth of creative ideas for solving human-centered problems. Why not leverage the AI guidelines as a stimulus in your next jam? Here are some approaches:</p><ul><li>Have each of your team members optimize the experience for a single guideline. What are all the ways you could <em>scope services when in doubt</em> (guideline 10), when you aren’t clear on the user’s intent, for example?</li><li>Next, push people in the opposite direction — what does a terrible experience look like for this guideline in your AI? The juxtaposition of great and terrible design ideas may reveal new creative opportunities and pitfalls.</li><li>Ask people to create different mash-ups of the concepts produced. Integrating ideas — even seemingly opposing ones — can unlock new ways of thinking about your AI’s design.</li></ul><p>The act of bringing together different perspectives for approaching the guidelines can help your team get to truly innovative solutions.</p><h3>#4. Embrace tensions between guidelines.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZmKxVsjEHk7AgD1CZoRK1A.png" /></figure><p>It’s easy to learn a set of “rules” and see them as that, rules. But these aren’t AI rules, they’re AI guidelines. That means you break them, play with them, and even intermix them. Don’t avoid places where the AI guidelines conflict with each other, or even with <a href="https://www.nngroup.com/articles/ten-usability-heuristics/">classic interaction guidelines</a>. Dive headfirst into any tensions you can find and use them to create energy. For example:</p><ul><li>How do you <em>update and adapt cautiously</em> (guideline 14) the AI system’s behaviors, while also creating an experience that is predictable?</li><li>How do you <em>encourage granular feedback</em> (guideline 15) during regular interaction, while also achieving a minimalist design?</li></ul><p>Creative power often comes from having to consider two ideas that — at least at face value — seem to be in conflict.</p><h3>#5. Use prototypes to gather new perspectives.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n5SrHoQkQA_mbgsZ6BFC_A.png" /></figure><p>Prototypes can be used to <a href="https://medium.com/microsoft-design/prototyping-empathy-1bdb08e3260c">build empathy and even generate new ideas</a>. Consider ways to use the guidelines, and concepts you draw to solve for them, to focus your next prototype research. Try this:</p><ul><li>Do a co-creation activity using your early concepts as a stimulus. For example, take concepts that <em>make clear why the system did what it did</em> (guideline 11), and ask people to “redraw” it in a way that leaves them feeling more in control.</li><li>Explore reactions to a breadth of different concepts, and get people talking about why they like what they do. <strong>Your team can ideate on new concepts that optimize for all the positive themes.</strong> For example, take concepts that <em>convey the consequences of user actions</em> (guideline 16) into research, and evaluate what elements help most with comprehension.</li></ul><p>Your initial ways of solving for the guidelines can generate conversations with customers, and even more ideas.</p><h3>Talk with us.</h3><p>These are things we’ve been recommending to other people innovating with AI experiences at Microsoft, but we’re sure there are other ideas out there. What do you think? Are there other tactics you’re trying out with the guidelines?</p><p>If you’re up for it, share this article with your teams and start a conversation. Or with your network and start a debate. We’d love to hear about your experiences in the comments. You can also catch <a href="https://www.linkedin.com/in/pennycollisson">Penny</a>, <a href="https://www.linkedin.com/in/saleema-amershi/">Saleema</a>, <a href="https://www.linkedin.com/in/mihaelavorvoreanu/">Mihaela</a>, and <a href="https://www.linkedin.com/in/michaelvincent-santos-2244263/">Michaelvincent </a>on LinkedIn.</p><h3>Authors.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EZes4-xaGuHgUwyhYTi-Fg.png" /></figure><p><a href="https://www.linkedin.com/in/saleema-amershi/">Saleema Amershi</a> is a researcher working on human-AI interaction at Microsoft Research AI.</p><p><a href="https://www.linkedin.com/in/mihaelavorvoreanu/">Mihaela Vorvoreanu</a> is a program manager working on human-AI interaction at Microsoft Research AI.</p><p><a href="https://medium.com/@michaelvincent.mvcms">Michaelvincent Santos</a> is a designer working on collaboration in Office.</p><p><a href="https://medium.com/@pennymarshcollisson">Penny Collisson</a> is a user research manager working on AI in Office.</p><p><em>With special thanks to </em><a href="https://www.linkedin.com/in/ghardiman/"><em>Gwenyth Hardiman</em></a><em>, </em><a href="https://www.linkedin.com/in/ruthkikingil/"><em>Ruth Kikin-Gil</em></a><em>, </em><a href="https://www.linkedin.com/in/trish-miner-8635aa8/"><em>Trish Miner</em></a><em>, </em><a href="https://www.linkedin.com/in/ken-milne-4980043/"><em>Ken Milne</em></a><em>, </em><a href="https://www.linkedin.com/in/meghanstockdale/"><em>Meghan Stockdale</em></a><em>, and </em><a href="https://www.linkedin.com/in/benjaminaleshire/"><em>Benjamin Aleshire</em></a><em> for their teamwork and contributions.</em></p><p><em>Also with thanks to our team who developed </em><a href="https://www.microsoft.com/en-us/research/publication/guidelines-for-human-ai-interaction/"><em>The Guidelines for Human-AI Interaction</em></a><em>: Saleema Amershi, Dan Weld, Mihaela Vorvoreanu, Adam Fourney, Besmira Nushi, Penny Collisson, Jina Suh, Shamsi Iqbal, Paul Bennett, Kori Inkpen, Jaime Teevan, Ruth Kikin-Gil, and Eric Horvitz.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=807b6d31cda2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/microsoft-design/ai-guidelines-in-the-creative-process-807b6d31cda2">AI Guidelines in the Creative Process</a> was originally published in <a href="https://medium.com/microsoft-design">Microsoft Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Prototyping Empathy]]></title>
            <link>https://medium.com/microsoft-design/prototyping-empathy-1bdb08e3260c?source=rss-7b414007ddb------2</link>
            <guid isPermaLink="false">https://medium.com/p/1bdb08e3260c</guid>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[microsoft-design]]></category>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[research-and-insight]]></category>
            <dc:creator><![CDATA[Penny Marsh Collisson]]></dc:creator>
            <pubDate>Mon, 03 Dec 2018 17:10:42 GMT</pubDate>
            <atom:updated>2018-12-03T17:44:40.362Z</atom:updated>
            <content:encoded><![CDATA[<h4>Six tips for staying focused on people while prototyping</h4><p><em>By Penny Collisson and Genny Mangum. Illustrations by Michaelvincent Santos.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/598/1*T_xJMZPPRi9wy0ZzmA9Y6g.png" /></figure><p>Here’s a common scenario: Your team just spent a crazy week pulling together a prototype for upcoming user research. Schedules are tight, pressures are high. Despite all the effort, it turns out the prototype isn’t really what you needed to have an awesome conversation with a customer. But at this point, only small tweaks to the prototype are feasible — because who has time for more? And frankly, you would feel like a real jerk if you were to ask for more. The team just sunk in a massive amount of time and effort.</p><p>There’s no shortage of innovative prototyping tools that tackle this exact scenario by enabling you to work with more agility and speed. However, we recently started to wonder if what we really need is not a new tool, but rather a refined approach for ensuring our prototyping efforts are human centered. As a result of that thinking, we want to share six strategies we’ve found useful for staying focused on people while prototyping. These are a mix of things we’ve been trying, as well ideas that emerged in conversations we’ve had with dozens of researchers (within and outside of Microsoft) about how they ensure empathy is built in — versus bolted on — while prototyping.</p><p>Let’s dive in.</p><h3>#1. Make people your top prototyping requirement.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/280/1*qcIvnLZle3-QmZzusKTwlw.png" /></figure><p>It’s easy to get bogged down in technical limitations while planning a prototype. As UX-ers, it’s our responsibility to ensure prototyping is empathy-led. First, understand who you are designing your prototype for. Include and plan to learn from people with a wide range of perspectives (<a href="https://www.microsoft.com/design/inclusive/">check out our work on inclusive design</a>). Also, get super crisp on users’ goals and the job they’re hiring your product to do, in the users’ language. What will they find valuable? Usable? How should they feel and not feel? How will your prototype support understanding this?</p><h3>#2. Optimize for a human experience, not a feature.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/363/1*mF4ImBarA4kMd7ksD0qz_g.png" /></figure><p>People rarely, if ever, experience a feature in isolation. As part of planning your prototype, think through just how interactive or complete your prototype needs to be to approximate your users’ reality. Be careful about optimizing your prototype to make testing more feasible or a prototype easier to build. <a href="https://medium.com/microsoft-design/skip-user-research-unless-youre-doing-it-right-seriously-15494e5ee033">This can really impact the validity and value of your research</a>. For your data to be useful, the prototype needs to be true to what a person would experience end-to-end in the finished product. You might even need to include the place they’d be starting before they get to your product. For example, will they get to your service through a browser? Through an app?</p><h3>#3. Use prototyping to explore (as well as validate).</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/259/1*5QdgRV_wTg1ki0CK57hxbg.png" /></figure><p>You will create some prototypes to evaluate your team’s ideas. However, you can also use prototypes to explore ideas and develop empathy with what users really want and need in earlier design stages. Consider the following:</p><p>· Using more than one prototype to explore reactions</p><p>· Enabling people to “redraw” parts of your prototype to best fit their needs</p><p>· Iterating your prototype in a <a href="https://en.wikipedia.org/wiki/RITE_Method">RITE</a> study based on people’s input</p><p>The key is to design prototypes with the intent of generating new ideas, as well as evaluating current ones.</p><h3>#4. Know what it looks like if you’re wrong.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/329/1*X4XCCxbtFDkHTbT-xkZ9Fw.png" /></figure><p>By the time most of us have come up with an idea, prototyped it, and socialized it with stakeholders, we’re feeling invested. So, what happens if you get feedback from users and start to get a sense that your idea isn’t landing? Ahead of running prototype research, it’s a good best practice to outline the range of possible feedback that you might hear and what you might do about it. By doing so, you’ll be more open to hearing you’re wrong, so you have a chance to get it right.</p><h3>#5. Make it more authentic with people’s real stuff.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/301/1*epFa78dKhQVdrg4CPcbe9A.png" /></figure><p>Products today are more personal, more dynamic, more context aware, and often tailored based on history and usage. If your prototype isn’t these things too, you’re probably not getting a good read on how your product will land. Consider having participants bring in some of their own data — e.g., photos, files, or even contact lists — to your study. Even low fidelity prototypes can be designed to reflect these types of information on the fly. For instance, when using a paper prototype, you can paste users’ contacts, files, or even photos into it.</p><h3>#6. Use your prototype to share people’s experience.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/307/1*WJxAsh-23ZFv9FHiVJ_NhQ.png" /></figure><p>Imagine if your prototype literally gave your stakeholders and teammates a way to walk in the shoes of your users. That is, experience what your users experience as they interacted with the prototype. Consider if there are ways to allow your teammates to “play” the prototype through the lens of different users—for example, someone who had a good experience versus a bad experience, someone who was a power user versus a casual user, someone who had high confidence in their computer skills versus low confidence. This could include creating videos or prototyping multiple paths.</p><h3>Talk with us.</h3><p>These are six tips we have been recommending to other people prototyping at Microsoft, but we’re sure there are other ideas out there. What do you think? What did we miss? What did we get wrong, or even right? We’d love to hear about your experiences. Please share them in the comments.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/176/1*C1tUePnWR9SVDAqtPtAJmQ.png" /><figcaption>You can also catch <a href="https://www.linkedin.com/in/pennycollisson">Penny</a>, <a href="https://www.linkedin.com/in/genevieve-mangum-552aa47b">Genny</a>, and <a href="https://www.linkedin.com/in/michaelvincent-santos-2244263/">Michaelvincent </a>on LinkedIn.</figcaption></figure><h3>Authors</h3><p><a href="https://medium.com/@genny.mangum">Genny Mangum</a> is a user researcher working on UX frameworks in Office.</p><p><a href="https://medium.com/@michaelvincent.mvcms">Michaelvincent Santos</a> is a designer working on collaboration in Office.</p><p><a href="https://medium.com/@pennymarshcollisson">Penny Collisson</a> is a user research manager working on AI in Office.</p><p><em>With special thanks to Trish Miner, Meghan Stockdale, Gwenyth Hardiman, and Paul Scudieri for their teamwork and contributions.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1bdb08e3260c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/microsoft-design/prototyping-empathy-1bdb08e3260c">Prototyping Empathy</a> was originally published in <a href="https://medium.com/microsoft-design">Microsoft Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>