<?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[User Interface 21 - Medium]]></title>
        <description><![CDATA[A conference tailored to raise your design practice to new heights. Full-day workshops reveal the nuance and insight necessary to deliver great designs. - Medium]]></description>
        <link>https://medium.com/user-interface-21?source=rss----9386f4152490---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>User Interface 21 - Medium</title>
            <link>https://medium.com/user-interface-21?source=rss----9386f4152490---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 23:19:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/user-interface-21" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Signaling a Process Change with a Discovery Phase]]></title>
            <link>https://medium.com/user-interface-21/signaling-a-process-change-with-a-discovery-phase-b73c271b145d?source=rss----9386f4152490---4</link>
            <guid isPermaLink="false">https://medium.com/p/b73c271b145d</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Jared M. Spool]]></dc:creator>
            <pubDate>Wed, 24 Aug 2016 16:49:52 GMT</pubDate>
            <atom:updated>2019-08-16T18:54:15.475Z</atom:updated>
            <content:encoded><![CDATA[<p>It’s easy to find people frustrated with their current product design and delivery process. They’ll list any number of maladies, from missing their customers’ true needs to forcing a buildout of unwanted features. Much of the time, many of their co–workers share that frustration.</p><p>Yet, those organizations are petrified of changing the way they do things. They know they need to change, but the act of change frightens the life out of them. This ironic justification of desire and fear keeps them from making things better.</p><p>Sure, they’ll announce “we’ll do it differently this time.” The executives will make proclamations about how they’re now a design–driven organization and how they’ll put the needs of customers first. There will be meetings about the new process, complete with powerpoint decks filled with box and arrow timeline charts.</p><p>Then, after all that, they’ll return to doing things the way they’ve already done it. The next project will start the same way every previous project has, often with the ritual called <em>The Gathering Of The Holy Requirements.</em> A product owner will spew forth the two or three dozen new features they believe are required for the next release. User stories will be crafted and sprints will be scrummed.</p><p>This new project will start like all previous projects have started. And it will end the way they’ve all previously ended, with the delivery of less–than–satisfying results.</p><h3>Discovery Can Change All That</h3><p>A thoughtfully–crafted, well–executed <em>discovery phase</em> can set an organization on a completely different path. More importantly, the discovery phase signals to the organization that, this time, the process truly will be different. And it does it with little fanfare and pomp. In fact, it’s often most effective when done in a bit of stealth mode, when only the direct participants are seeing the process.</p><p>Dan Brown has spent the last few years taking apart discovery phases to learn how they can be most effective. He’s created a great framework for them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Ch3-VZNcqRjo_mg-.png" /></figure><p><em>Dan Brown’s Discovery Activities Matrix</em></p><p>In Dan’s framework, he splits the activities of the discovery phase into two main groups:</p><ul><li><em>framing problems,</em> where the team dives deep into the problems customers and users experience</li><li><em>setting direction,</em> where the team explores potential solutions and matches them up with the customer problems they’re solving</li></ul><p>Each of these groups has:</p><ul><li>an early stage, where the team first <em>diverges,</em> exploring the range of problems and solutions</li><li>a later stage, where the team then <em>converges,</em> honing in on the specific problems and solutions they’ll tackle</li></ul><p>If you’re already conducting design sprints or employing Lean UX, those are likely your discovery phase. However they aren’t the only approaches a team can employ. Experienced design leaders can create a bespoke workshop that includes activities such as user visits, competitive evaluations, group sketching, day–in–the–life narratives, and insight prioritization. The leader can tailor this to fit the needs of their specific projects.</p><p>Dan recommends using the discovery phase to bring your design’s influencers together. When you lead the assembled group through the discovery phase activities together, the team will gain a shared understanding of both the customers’ problems and possible solutions. Using the discovery phase to frame the problem and set the project’s direction gets everyone on the same page.</p><h3>How The Discovery Phase Signals Change</h3><p>Space is indeed the final frontier. Nothing signals <em>‘something is different this time’</em> more than when you reserve a conference room for a week (or several). The same is true when you ask a group of important people to clear their calendar for a workshop. Organizations hold the space/time continuum as prime real estate and to reserve it means something big is happening. Add executive support and encouragement and now you’re sending a message that this is a big deal.</p><p>The activities within the discovery phase also signal change. By drilling deep into the problems of customers, the team breaks the tradition of starting a project by jumping to the most obvious solution first. These activities focus on learning about the problem, such as customer visits, observing the customer support, interviewing salespeople, and exploring how well the competition meets your users’ true needs. The team will gain insights about their users they’ve never considered before.</p><p>The leader of a well-designed discovery phase will recruit a multi-disciplinary team and assemble people who have different viewpoints about the project. These folks will participate in the project all the way through.</p><p>A multi–disciplinary team likely breaks with tradition of only involving key people in small slices of the project, because it’s deemed wasteful to have them contribute outside their expertise. However, when they’re involved all the way through, they get the benefit of seeing what goes into a design. And by contributing their own expertise much earlier into the process, they provide insights that have previously been absent or discovered too late.</p><p>Having these different folks contribute from the very beginning breaks with another long–standing tradition of relying on organizational seniority over who truly has the necessary knowledge and experience. The activities of a discovery phase equalize the role power in the room, letting everyone have a voice. It quickly becomes obvious that solid contributions can come from anywhere in the organization. For many organizations, this is a new way of doing business.</p><h3>Making It Difficult To Fall Back Into Old Habits</h3><p>One of the best benefits of a well–run discovery phase is the discomfort the participants will experience with the old ways things were done. What used to be considered acceptable (if not desirable) practices now are seen as non–productive. Instead, the team now wants these new practices that emphasize a shared understanding of what the team is building.</p><p>The movement from <em>requirements gathering</em> to <em>assumption validation</em> is one common organizational shift that comes from introducing discovery phases. Teams realize they’ve been spewing requirements without any sense of whether they are truly needed or not. Now the team sees them as tools to, from the project’s start, understand what the customers’ need and what won’t matter. This creates a culture of questioning beliefs in a healthy way until they’re validated through research.</p><p>Once shifts like these have started, the team finds it very difficult to fall back into their old habits. They’re more comfortable when everyone has a shared understanding. They create a common vocabulary to describe problems they’re solving. And they find they can move faster to produce better results, which in turn, makes the entire executive staff happier.</p><p>Starting with a discovery phase for new design and development leads to better quality products and enhancements. Crafting it well can also signal that the organization is changing, by setting an example of how things are better from the beginning.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b73c271b145d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/user-interface-21/signaling-a-process-change-with-a-discovery-phase-b73c271b145d">Signaling a Process Change with a Discovery Phase</a> was originally published in <a href="https://medium.com/user-interface-21">User Interface 21</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Right Way to Train the Wrong Way Research]]></title>
            <link>https://medium.com/user-interface-21/the-right-way-to-train-the-wrong-way-research-a-ui21-podcast-with-cyd-harrell-8bb99164ad26?source=rss----9386f4152490---4</link>
            <guid isPermaLink="false">https://medium.com/p/8bb99164ad26</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Jared M. Spool]]></dc:creator>
            <pubDate>Thu, 18 Aug 2016 15:52:13 GMT</pubDate>
            <atom:updated>2019-08-16T18:55:17.082Z</atom:updated>
            <content:encoded><![CDATA[<iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fw.soundcloud.com%2Fplayer%2F%3Furl%3Dhttp%253A%252F%252Fapi.soundcloud.com%252Ftracks%252F278001666%26show_artwork%3Dtrue&amp;url=https%3A%2F%2Fsoundcloud.com%2Fuie-podcast%2Fthe-right-way-to-train-the-wrong-way-research&amp;image=http%3A%2F%2Fi1.sndcdn.com%2Fartworks-000176327958-wsrtl6-t500x500.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=soundcloud" width="500" height="166" frameborder="0" scrolling="no"><a href="https://medium.com/media/cee1ad773a948e422e014de8305bb287/href">https://medium.com/media/cee1ad773a948e422e014de8305bb287/href</a></iframe><h3>A UI21 Podcast with Cyd Harrell</h3><p>When we’re training teams on our design methods, what we perceive as ‘proper’ may in fact become a hindrance. Our dogmatic approach to our processes may prevent people from ever employing the techniques. Is it better to do it <em>the right way</em>, or to teach a <em>wrong way</em> that will get the job done?</p><p>Cyd Harrell encountered one such situation, while working with a government design team. They would’ve never conducted user research if she’d taught them the proper way to do it. By breaking “the rules,” she empowered the team to embrace good design and improve the life of their citizens.</p><p>UI21 has come and gone. But <a href="https://ui.uie.com/"><strong>UI22 is coming.</strong></a><strong> </strong>You’ll immerse yourself in full-day UX workshops that go deep into the techniques and practices, delivering the theory and expertise. I’ve curated eight master-grade workshops, each taught by renowned industry leaders. <a href="https://ui.uie.com/#workshops">Roll up your sleeves, get down to work, and change the way you design forever.</a></p><h3>Full Transcript</h3><blockquote><strong><em>Jared Spool:</em></strong><em> This is the UI Conference Podcast. I’m Jared Spool.</em></blockquote><blockquote><em>Part of becoming better at something — becoming more experienced — is learning that there’s a right way and a wrong way to get things done. Yet, when you become a master, well, that’s when you learn that sometimes the wrong way might in fact be better than the right way.</em></blockquote><blockquote><em>That moment, when the wrong way is likely the better way, often happens when you’re thrust into a situation where time and resources are at their most limited.</em></blockquote><blockquote><strong><em>Cyd Harrell:</em></strong><em> Something that I always try to tell myself is that it makes sense, for me, to refine your techniques and practices over a couple of decades like I have, but if you are an underfunded government person, you might be able to get a lot out of any time you can give to this.</em></blockquote><blockquote><em>My name is Cyd Harrell. I am a UX researcher by trade, and I do a lot of training and mentoring of people in the civic technology space.</em></blockquote><blockquote><strong><em>Jared:</em></strong><em> Through her work in the civic space, Cyd has encountered a number of outdated designs in government websites and software.</em></blockquote><blockquote><strong><em>Cyd:</em></strong><em> Most government software looks like the ’90s, and design is not a priority, particularly the sense of design, as in visual design that most government people would attach to that word, is not a huge priority for software, unless it comes to something like the graphics on the front of the city website.</em></blockquote><blockquote><strong><em>Jared:</em></strong><em> As our design influence expands, we need the teams we work with to take on more of their own design process. This is especially true when their resources are constrained, like Cyd’s underfunded government teams. And like all design teams, if they don’t get their design in front of actual users, they may not learn how frustrating they’ve made it. To teach her teams this lesson, Cyd’s come up with a clever and simple trick.</em></blockquote><blockquote><strong><em>Cyd:</em></strong><em> I found the whole bunch of sets of instructions for Origami Giraffes. What I do is I actually provide people with inappropriate materials. I put regular eight-and-a-half by 11 sheets on the tables. I don’t offer any scissors. At the end of the set of instructions, it wants you to draw spots on the draft. I don’t give them any pens as the paper isn’t colored.</em></blockquote><blockquote><em>The instructions do a couple of common failure mode things that a lot of websites do like use vocabulary that no one but a power user would be familiar with or the diagrams really aren’t clear. If you think about the way that Origami instructions would be provided and in fact like a video might be the best way, but we look at them either on paper on a flat screen.</em></blockquote><blockquote><strong><em>Jared:</em></strong><em> Cyd’s origami giraffe trick works. Teams get the message.</em></blockquote><blockquote><strong><em>Jonathan Feldman:</em></strong><em> She gave these instructions about how to make the giraffe. Of course no one could do it because the instructions were so God-awful bad, which in city government, we see that all the time. We think it’s very clear when it’s really clear as mud.</em></blockquote><blockquote><em>Then Cyd stepped everyone through what if you made the instructions based on how people like to take in information. I think a lot of light bulbs went off in my staffs’ mind at that point.</em></blockquote><blockquote><em>Jonathan Feldman. Chief Information Officer with the City of Asheville, North Carolina.</em></blockquote><blockquote><strong><em>Jared:</em></strong><em> Like many in government positions, Jonathan has experienced the constraints that come with of a shortage of resources.</em></blockquote><blockquote><strong><em>Jonathan:</em></strong><em> We had never done usability testing before Cyd’s workshop.</em></blockquote><blockquote><em>If we just start designing things in this way where we start doing usability testing of everything, we’d probably be in a lot better shape in terms of actually being able to help people.</em></blockquote><blockquote><em>That was the understatement of the decade because when we did usability testing and we gave folks objectives, man or woman off the street, employees, whomever.</em></blockquote><blockquote><em>We gave people objectives, we found that they were taking sometimes 15 minutes to figure out how the heck to achieve that objective.</em></blockquote><blockquote><em>A couple of redesigns later, it was taking new people, not the same people but cohorts of those people, under 15 seconds to achieve those same goals. That’s pretty strong.</em></blockquote><blockquote><em>What’s interesting is it just wasn’t hard to do. It was tedious. It required time. But it was so effective that my staff became very enthusiastic about doing it. Frankly, the folks in the public information office also became enthusiastic about it. Because who doesn’t want their stuff to be easily accessible?</em></blockquote><blockquote><strong><em>Cyd:</em></strong><em> One of the first slides in my presentation at that workshop is it’s not rocket science.</em></blockquote><blockquote><em>I tell them that if you are someone who can have empathetic phone conversation with someone you care about, about something that’s happened to them. You have the necessary skills to do this, well enough, to get something out of it that will make your development better.</em></blockquote><blockquote><em>These are a bunch of practices that I would not use largely in a study that I was doing for a client of mine that I’m recommending to people in different relationship. It’s actually influenced the other way and it’s like “Well maybe I need to be a little bit more flexible,” carefully considered of course in some of what I do myself.</em></blockquote><blockquote><em>It’s not that it works better. It’s because it works well enough and a gold standard might be unattainable.</em></blockquote><blockquote><strong><em>Jared:</em></strong><em> Now some might say Cyd is breaking the rules: She’s teaching these teams a sloppy way to do research and any professional would know better. But, the teams she’s teaching aren’t professionals and they’d never have a chance to work with professionals.</em></blockquote><blockquote><em>The choice isn’t do it the right way or don’t do it at all. Cyd’s approach is that doing something is better than doing nothing. Can we teach teams how to move the needle and get results, using a method that isn’t the proper method, but is more effective than nothing?</em></blockquote><blockquote><strong><em>Cyd:</em></strong><em> I try to provide people with an enticing bite of something that isn’t necessarily wrong, but that probably isn’t all the way right, either, when I’m doing it in that compressed of a timeframe. One other thing I was thinking about is why does this work. In part it works a little bit because I’d been willing especially in working with government people to do it wrong.</em></blockquote><blockquote><strong><em>Jonathan:</em></strong><em> I think that a lot of us in our department are very customer focused. I think that we’re a little bit unusual of an IT organization because I believe we all think that IT is a people business, not a technology business. We’re here to help people, not harm people.</em></blockquote><blockquote><em>Of course we would not go back to that old way of doing things because it just doesn’t help people as much.</em></blockquote><blockquote><strong><em>Cyd:</em></strong><em> Jonathan was just in for lunch, and he left, so I had to call him back and say, “How did you guys do this? Did you hire a designer?” He said, “No, we just decided to pay attention to design, and we did two or three rounds of testing with real users. Then we listened, and we made it better, and now we’ve come up with this.”</em></blockquote><blockquote><em>The thing that he said to me, and made me really believe it’s permanent, is he said, “Cyd, we have never had an opportunity to delight our users.”</em></blockquote><blockquote><strong><em>Jared:</em></strong><em> That moment — when the team realizes there’s something they can do to dramatically improve the quality of their design work — that’s the moment we are all work for. Showing them that, as long as they have the user in mind they can achieve great results, that’s the core of a good design practice.</em></blockquote><blockquote><em>This means we need to challenge our assumptions about what research needs to be and, more importantly, be much less dogmatic about our processes. Just because a technique might not be textbook perfect, doesn’t mean it’s the wrong way to get our teams focused on delight.</em></blockquote><blockquote><em>The UI Conference podcast is brought to you by the User Interface Conference, October 31 through November 2, 2016 in beautiful Boston, Massachusetts. That’s where Cyd Harrell will give her full-day workshop on Low-Cost Guerrilla User Research.</em></blockquote><blockquote><em>Cyd walked me through everything she’ll teach that day, and it’s fantastic. She’s packed the workshop with practical, real-world techniques that will help you show your teams how they can get immediate and inexpensive information about who their users are and how to design great experiences that’ll meet their needs. If you’re working with teams with constrained budgets and schedules, you’ll definitely want to check out her workshop.</em></blockquote><blockquote><em>You’ll find the complete description of Cyd’s workshop, and the other great full-day workshops at </em><a href="https://ui21.uie.com/#workshops"><em>uiconf.com</em></a><em>. That’s U I C O N F dot com.</em></blockquote><blockquote><em>The UI Conference podcast is produced by myself and Sean Carmichael. We’d like to give special thanks to Cyd Harrell and Jonathan Feldman for being a part of this episode.</em></blockquote><blockquote><em>You can find more information about the UI Conference podcast on iTunes and at the User Interface Conference web site, </em><a href="https://ui21.uie.com/"><em>uiconf.com</em></a><em>.</em></blockquote><blockquote><em>You’ve been listening the UI Conference Podcast, part of the growing UIE Podcast Network. Thanks for listening and encouraging our behavior.</em></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8bb99164ad26" width="1" height="1" alt=""><hr><p><a href="https://medium.com/user-interface-21/the-right-way-to-train-the-wrong-way-research-a-ui21-podcast-with-cyd-harrell-8bb99164ad26">The Right Way to Train the Wrong Way Research</a> was originally published in <a href="https://medium.com/user-interface-21">User Interface 21</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>