<?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 Greg Smith on Medium]]></title>
        <description><![CDATA[Stories by Greg Smith on Medium]]></description>
        <link>https://medium.com/@gsmth00?source=rss-4ee03e1dcb85------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*29D_cxLegu-xPfbRbXbu4g.jpeg</url>
            <title>Stories by Greg Smith on Medium</title>
            <link>https://medium.com/@gsmth00?source=rss-4ee03e1dcb85------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 13:47:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@gsmth00/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[Creative constraints: How limitations can fuel creativity]]></title>
            <link>https://uxdesign.cc/creative-constraints-how-limitations-can-fuel-creativity-de3ef1e441b8?source=rss-4ee03e1dcb85------2</link>
            <guid isPermaLink="false">https://medium.com/p/de3ef1e441b8</guid>
            <category><![CDATA[creative-process]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[creativity]]></category>
            <dc:creator><![CDATA[Greg Smith]]></dc:creator>
            <pubDate>Wed, 27 May 2020 16:21:30 GMT</pubDate>
            <atom:updated>2020-06-09T11:25:10.534Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Keith Jarret sitting at a piano, staring at the keys" src="https://cdn-images-1.medium.com/max/1024/1*K8IL1D5UdcxDmkOUGie3jQ.jpeg" /></figure><p>When we think about creativity, or more specifically the process of “being creative”, there’s a tendency to envision it as something that happens with reckless abandon. Whether it’s a group of people sitting in a room full of whiteboards, furiously generating ideas, or an artist creating a masterpiece from a blank canvas, we can’t help but imagine creativity as something that thrives without structure or limitation. But the reality of what generally fuels creative thinking for most people is actually much different.</p><p>Take the story of Keith Jarret — a renowned American jazz pianist — and his 1975 performance at the Cologne opera house. For the people fortunate enough to be in attendance that evening, it was a magical experience that is widely regarded as one his most memorable concerts. The recording of that evening’s performance was released as a double-album later that year, and went on to become what is still the best-selling piano album of all time. Amazingly though, the concert almost never happened.</p><p>Jarret was well known for being a perfectionist, who had particularly stringent demands when it came to his pianos. When he showed up for the concert that day however, he discovered that there had been a mistake — instead of the concert grand piano he had arranged for, the venue had provided a much smaller baby grand. On top of that, the piano — which was generally used for rehearsals — was in poor condition and badly out of tune. On the verge of cancelling the show, Jarret was persuaded to continue on by the concert promoter, under the condition that they do what they could to get the piano up to his standards by showtime, since there wasn’t enough time to have a replacement brought in. They did what they could to tune it, but the end result was far from ideal, and they couldn’t do much to improve it’s tone and timbre, which led to jangly high notes and poor bass. And to add insult to injury, the piano’s pedals were malfunctioning.</p><p>When Jarret took the stage that evening for his solo improvisation, he knew that he would be confined by the limitations of the piano. Yet somehow, faced with those constraints, he went on to deliver an iconic performance for the ages. Because of the piano’s poor quality, he was forced to play in a way he wouldn’t normally have, creating a sound that could only have come from that particular set of circumstances, and on that particular night.</p><p>Asked later about the performance, the album’s producer attributed the uncharacteristic sound to the piano’s shortcomings, saying:</p><blockquote>“[Jarrett] played it the way he did because it was not a good piano. Because he could not fall in love with the sound of it, he found another way to get the most out of it.”</blockquote><p>It seems counterintuitive to think that creativity can be fueled by constraints, but that was the case for Keith Jarret, and has been my experience as well. While I don’t generally work with concert pianists, I do work with a variety of professionals who are looking to generate new, innovative ideas, and the deliberate use of constraints is one of the most effective ways to help them do that.</p><p>Constraints are often viewed negatively — as something that handicaps a process — but if you’ve ever participated in a typical “brainstorm” session, where everyone sits around the table, shouting ideas over one another before discussing them ad nauseum, you’ve seen how ineffective an open-ended ideation session can be. Applied the right way, and at the right time, constraints can actually be incredibly helpful and can enable teams to unlock ideas that would have otherwise gone unrealized. As a result, we deliberately incorporate constraints into our workshops — sometimes a specific limitation is built into a particular exercise ahead of time, and other times we’ll make an in-the-moment decision to apply a constraint, based on the dynamics of the particular group.</p><p>Here’s a list of some of the most common types we use to help fuel creativity in the teams we work with:</p><h3><strong>Time</strong></h3><p>Parkinson’s Law states that “work expands so as to fill the time available for its completion”. Whether you have an hour or a week to work on a particular task, it’s likely that the work will grow to fill that span. And while in some cases, more time to work on something is unquestionably better, ideation isn’t something that has to take very long. If a team is well primed — meaning they’ve spent the time to really understand the problem they’re trying to solve for — they can generally come up with ideas in a comparatively short period of time. In the course of a 2–3 day workshop, we generally only have 10–15 minutes of time allocated specifically to ideating. The teams come into that section of the day confident in their knowledge of the problem, and the strict time limit forces them to quickly get ideas out of their heads without discussion or evaluation. Time limits also play a critical role in forcing teams to make quick decisions throughout the course of a workshop, since there’s no opportunity to deliberate. Without a finite time limit, an ideation session can quickly spiral out of control into a meandering discussion, so this constraint can help you create a sense of urgency to keep things moving.</p><h3><strong>Discussion</strong></h3><p>One of the most effective meeting formats we’ve used to help teams come up with new ideas is something we call a <a href="https://www.youtube.com/watch?v=wqsULoGvlpc">Silent Storm</a>. It takes place over the course of 45–60 minutes, and aside from some prompting from the facilitator along the way, is done largely in silence. By eliminating discussion, we minimize unhelpful tangents and sidebar conversations, remove unnecessary debate over the validity of any particular idea, and strip away any opportunity for a strong personality to take over the conversation — all of which are potential downsides to a traditional “brainstorm” session. As a result, each participant can ideate freely and without judgement. It’s often uncomfortable at first, but teams are continually amazed at the effectiveness of the format, allowing them to efficiently generate new and innovative ideas — all without talking!</p><h3><strong>Space</strong></h3><p>Similar to Parkinson’s Law, we’ve often seen ideas expand to fill the <em>physical</em> space they’re given as well. Give someone a blank whiteboard, and they’ll either fill it with an overly complex idea or two, or will be so intimidated by the thought of filling all that blank space that they’ll effectively be paralyzed. That’s one of the many reasons we rely heavily on Post-it notes (and Sharpies!) in our sessions. The small space encourages brevity and the ephemeral nature of the paper itself allows participants to quickly jot down ideas without feeling as though they must first be fully baked.</p><h3><strong>Decisions</strong></h3><p>A productive ideation session can spawn tons of great ideas. So many in fact, that there can often be a tendency for a team to want to keep them all, instead of trying to decide on the one with the most potential upside. By trying to take all of their ideas forward however, a team won’t be successful in the implementation of any single one of them. On the flip side of that same coin, allowing teams the opportunity to decide on a single, top idea via an open discussion is an exercise in futility — people will quickly get bogged down in a lengthy discussion around the viability of each and every one of the ideas, and will usually still be unable to collectively decide on a single one. Instead, we use a voting system to ensure quick decision making. By giving every participant a finite amount of votes — and setting a strict time limit in which they must cast them! — we force efficient decisions, and ensure that the strongest ideas are taken forward in a democratic fashion.</p><h3><strong>Language/Wording</strong></h3><p>Sometimes, placing a constraint on the <em>types</em> of words people are able to use can help bring about unexpected ideas. Anyone familiar with the improv concept of “Yes, and” can attest the power of a simple reframe. At certain points in a session, we may have participants take top-voted ideas and quickly expand upon them by using the generative “Yes, and” technique. Rather than being able to evaluate or discuss potential issues with the ideas, they’re asked to only use the words “Yes, and…” prior to their statement — “<strong>Yes, and</strong> we could build it in virtual reality.” By constraining the use of certain language this way, we ensure that teams are quickly able to push the limits of their thinking around a given idea, and collectively generate something that a single person would not have been able to.</p><h3><strong>Artificial Constraints (“Powers of 10”)</strong></h3><p>There are times when a team may ‘hit the wall’ in their ideation, and seemingly run out of ideas. By imposing an artificial constraint however, we often see that it unlocks their ability to generate additional concepts, by pushing them to think of options they wouldn’t have otherwise. An example might be “What might this look like if we only had a budget of $10?”. Conversely, it could be something along the lines of “What if we had $10 million to build it?”. By picking a particular “lever” as a constraint (e.g. time, budget, technology, etc) and scaling it up or down exponentially, you can push teams to think outside of the box they may have gotten stuck within.</p><p>Constraints can be an especially useful tool, when properly applied. The next time you’re leading, or participating in, an ideation session, resist the tendency to follow the usual “group brainstorm” format and think about how you might leverage the power of constraints to help supercharge the team’s creativity.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de3ef1e441b8" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/creative-constraints-how-limitations-can-fuel-creativity-de3ef1e441b8">Creative constraints: How limitations can fuel creativity</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to talk to strangers, and why you should]]></title>
            <link>https://uxdesign.cc/how-to-talk-to-strangers-and-why-you-should-ea06dd191f0e?source=rss-4ee03e1dcb85------2</link>
            <guid isPermaLink="false">https://medium.com/p/ea06dd191f0e</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Greg Smith]]></dc:creator>
            <pubDate>Tue, 12 May 2020 14:15:37 GMT</pubDate>
            <atom:updated>2020-05-13T13:32:14.528Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Two men talking at a conference table, while one man captures notes" src="https://cdn-images-1.medium.com/max/1024/1*HWmMopVh8sdBOQNWOrZHUg.jpeg" /></figure><p>Most of us have meetings. They’re an inescapable part of working life, no matter what your profession. Meetings themselves can be good or bad, which is a topic for <a href="https://medium.com/ux-for-the-win/make-your-meetings-work-for-you-instead-of-you-working-for-your-meetings-fcff81a62bb">another post</a>, but regardless of what kind of work you do, it’s a solid bet that on any given day of the week, you’ll be meeting with one or more people you know — team members, stakeholders, colleagues, direct reports and/or bosses.</p><p>But how often are you meeting with people that you <strong><em>don’t</em></strong> know? As I look at my calendar for today, I have a handful of meetings with my team and a few project update conversations with various stakeholders, but the rest of the day will be spent talking to people I’ve never met before. And that’s not just today. In fact, that’s representative of a pretty normal day for me and my team — those conversations are user interviews.</p><p>We design and facilitate workshops for clients that are trying to better understand a problem space and solve some sort of issue. They may be trying to launch a new product or service to the market, or may be trying to improve upon an existing one. They may be trying to streamline a process, or better align their overall organizational structure. Sometimes they just need some help defining who they are as a team, and what they want to be known for. No matter what the circumstances though, the best place to start is always with their customers (users). Only by talking to those people — those strangers — to understand their individual experiences, can my team help the group we’re working with uncover unmet needs and then design solutions for them.</p><p>So as a result, I spend a large portion of most days talking to people I don’t know, asking them to share their personal experiences with me. And I love it. Not only is it a critical step to helping our clients identify new opportunities, but it’s something that I legitimately enjoy. One day I may be talking to someone about their experience navigating a hiring process within an organization. Another day I’ll be talking to someone about their experience using a website or digital application. And still the next, I’ll be having a conversation about someone’s experience leading a diversity program on a college campus. Sometimes I’ll have all of those conversations in the course of a single day. It’s fascinating being able to talk to so many different people, with such varied experiences, and is something I’d much prefer to the “weekly status update” type of meeting.</p><p>I recognize that not everyone has the need to talk to such a wide range of individuals as part of their job, but you should at least be talking to <strong><em>your</em></strong> customers on a regular basis. Your customers may be other, internal teams at your company, may be clients at other B2B organizations, or may be consumers in a particular market segment. But whoever they are, you should be talking to them.</p><p>In this age of data, we have a wealth of information at our fingertips, and it’s easy to assume that the highly customized dashboard we look at each day holds all the answers, but that’s rarely the case. Quantitative data is fantastic at helping us uncover <strong><em>where</em></strong> issues are occuring, but doesn’t generally do a great job at telling us <strong><em>why</em></strong>. To find that out, you’ll need to look to your customers. You’ll need to understand their experience, and see the world through their eyes. You’ll be amazed at how insightful a quick 20-minute conversation can be, and at what common themes will emerge after just a handful of them. But if you don’t have a lot of experience doing user interviews, getting started might be a little intimidating. The good news is that it’s not difficult, and is something that gets easier the more you do it. To help you get the ball rolling, here are 10 tips for how to make the most of the conversations.</p><h3><strong>Make sure you’re talking to the right people</strong></h3><p>This is less of a tip about <em>how</em> to conduct a user interview and more a word of caution about <em>who</em> you’re conducting the interview with. Make sure it’s with the right people — your actual customers. These are the people buying your product or using your service. It sounds simple enough, but on most projects, there are a variety of internal stakeholders and decision-makers involved, and there’s often a tendency to treat those people as the end-user. After all, if the decision-maker is the one who will be signing off on everything, it makes sense that you’d want to better understand what they’re ultimately looking for. There’s nothing wrong with having a conversation in order to clarify that person’s point of view, but just be sure you’re clear on who you’re ultimately solving for (hint: it’s your customer), and make sure you’re spending most of your time talking with those people.</p><h3><strong>Be friendly</strong></h3><p>This is a simple one, but is so important. Be friendly with the person you’re speaking to. Recognize that they may be uncomfortable coming into the conversation, and try to put them at ease. Ask how their day is going, and spend the first 2–3 minutes just establishing a rapport. This may be work for you, but it isn’t for them. Be a real person. This will go a long way towards ensuring they’re comfortable enough to really open up and be honest with their feedback, which is critical to uncovering valuable insights. Also, don’t forget that they’re a customer, and so it’s a great opportunity to ensure they have a positive touchpoint with your brand.</p><h3><strong>Set expectations upfront</strong></h3><p>Once you’ve gotten them comfortable, set the stage for the conversation. Let them know who you are, and why you’ve reached out to have this discussion. Make sure they know that you’re looking for their honest feedback, good or bad, and that there are no right or wrong answers. I also find it helpful to reiterate that the more open they are with us, the more likely we are to find ways to ultimately improve the product or service that they use.</p><h3><strong>Have a loose interview guide, but let the conversation flow naturally</strong></h3><p>There’s often a tendency to want to create a list of interview questions you intend to cover, and to use that to dictate the conversation. The problem with that approach however is that it tends to make the discussion feel more like a police interrogation than it does a natural conversation. If you’re just going down the list of questions you planned in advance, you’re almost certainly missing out on opportunities to go deeper on something interesting they say, that you hadn’t anticipated. So instead of a list of questions, I recommend an interview ‘guide’. Before I start user interviews, I’ll pull together a short document that outlines the learning goal(s) for the conversations (e.g. better understand the experience potential candidates are having during the hiring process) and a few high-level topics or themes that I want to try and dig into (e.g. how did they first learn about the job, what were their initial expectations prior to the interview, etc). I know that these are framed as questions, but the important distinction here is that they’re just guideposts to help me structure the conversation and not something that I blindly follow no matter what. What inevitably happens in every interview is that, as the person starts sharing their experience, they’ll mention some interesting and unexpected insight. When you hear that, it’s your opportunity to digress from the interview guide and ask them to go deeper — “That’s really interesting to hear that you felt that way. Can you tell me a little more about what you were thinking at that point?” It’s these unexpected tangents where the richest and most surprising insights almost invariably come from, so don’t lose the opportunity to learn because you’re too beholden to your list of questions. There will be plenty of conversations where you don’t fully cover all the topics/questions you set out to, but where you’ll still have gained a ton of really valuable information.</p><h3><strong>Ask open-ended questions</strong></h3><p>Not much to this one. Just ensure your questions are open-ended. “Did you enjoy using the product?” is far less likely to result in a valuable insight than is “Tell me about your experience using the product.”</p><h3><strong>Ask about specific experiences</strong></h3><p>It’s natural to want to ask someone about a hypothetical situation — “What would your ideal travel experience look like?” — but the answer you get is likely to be much less helpful than asking them to recount an actual experience they’ve recently had — “Tell me about the last time you traveled.” In one instance they’re providing factual information, and in the other, they’re making up the answer on the spot. These hypothetical types of questions can still serve a purpose, by allowing you to better understand the customer’s mindset, but when it comes to identifying pain points, you’re much better off asking for real experiences.</p><h3><strong>Channel your inner Spock</strong></h3><figure><img alt="Spock, a character from Star Trek, saying “I’m a scientist. Emotions are alien to me.”" src="https://cdn-images-1.medium.com/max/375/1*k4QHxK8SPaJX8i7mXvIeIQ.gif" /></figure><p>Fellow Trekies will know that Spock is a character from the popular Star Trek series. He was from the planet Vulcan, and was known for prioritizing logic above emotion. No matter what his emotional state at any given time, rarely did he show any outward signs of it. The same is true of a good interviewer. That’s not to say that you have to be robotic; as mentioned above, being a real person is key to making the customer you’re talking with comfortable. But as people share their experiences, good or bad, it’s your job <em>not</em> to react. If someone loves your product, don’t jump up and down for joy. And if someone hates it, don’t let on that you’re bummed to hear it. It’s human nature to want to please people, so if the person you’re interviewing sees that a certain type of feedback is making you especially happy, they’re likely to share more of that, and conversely, if they see that a certain type of feedback is making you especially upset, they’re likely to share less. What you want however, is their <em>honest</em> feedback, so try not to tip your hat one way or another.</p><h3><strong>Have someone else take notes (or record the conversation)</strong></h3><p>I have a hard time engaging in a conversation and capturing notes at the same time, so when it comes to user interviews, I’ll generally ask one of my teammates to join as well, so that they can capture insights while I focus on the discussion. And if that’s not possible, I’ll try and record the interview so that I can go back later and capture notes while I re-listen to it. In either case however, it’s important to be transparent about what’s going on. When you’re setting expectations in those first few minutes, let the person you’re speaking with know that you have a colleague listening in, or in the case of recording the interview, let them know why and ask for their permission first.</p><h3><strong>Thank them for sharing</strong></h3><p>Interviews can often be uncomfortable for people, especially if the subject matter is personal. If you do a good job of putting someone at ease and correctly setting the stage, people will often open up and share personal, emotional stories. When they do so, make sure to thank them for it — “Thanks so much for sharing that. I really appreciate it.” This goes a long way towards keeping them comfortable and letting them know that you’re really hearing them.</p><h3><strong>When you’re done, be done</strong></h3><p>Sometimes an interview will last 10–15 minutes. Other times you’ll find someone who has a wealth of information to share, and the conversation may go on a bit longer. But at some point in every interview, it will be clear that you’ve heard what they have to say and will have learned what you can. When you reach this point, thank the person for their time, lay out any next steps they may need to know about, and then wrap up. There can sometimes be a tendency to start ‘spitballing’ with the customer, talking about any number of different things, but this extra conversation is rarely helpful for either party. So be respectful of their time (and yours), and don’t be afraid to end the conversation once it’s clearly over.</p><p>While “talking to customers” may only be a formal job requirement for your organization’s product manager, I firmly believe that everyone in the company can gain something by listening to users. Time and again, I’m amazed at the insights that come from a few, short conversations, and in the ability for that information to rally a team around a singular focus. So if you’re not already making it a point to talk to strangers on a frequent basis, I encourage you to start.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea06dd191f0e" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/how-to-talk-to-strangers-and-why-you-should-ea06dd191f0e">How to talk to strangers, and why you should</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Everyone Needs The Occasional Dumpster Fire]]></title>
            <link>https://medium.com/ux-for-the-win/why-everyone-needs-the-occasional-dumpster-fire-a3936cff8a1e?source=rss-4ee03e1dcb85------2</link>
            <guid isPermaLink="false">https://medium.com/p/a3936cff8a1e</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[user-experience-design]]></category>
            <dc:creator><![CDATA[Greg Smith]]></dc:creator>
            <pubDate>Thu, 22 Aug 2019 18:29:40 GMT</pubDate>
            <atom:updated>2020-05-14T13:39:57.042Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*eYXVvtHAwviFB-DI0uaedA.gif" /></figure><p>It’s fantastic when things go well. Generally, that’s the payoff when you’re focused on the right priorities, and your team is making good decisions on how to spend their time. For my team and I, things “going well” means that we’re leading successful workshops, and that the teams we’re working with are coming out of the sessions with impactful, user-centered solutions that they can take forward and continue developing. Generally speaking, I would put the great majority of workshops we lead firmly into this category —teams regularly tell us about the value they got from the session, and we frequently get asked to come back and help out with other projects.</p><p>But every now and then, we’re involved in a project where things don’t go so well. There are a number of reasons as to why this might happen, but the end result is a workshop where things went awry, the team didn’t feel as though they got the value they were hoping for, and we spent much of the time spinning our wheels and trying to get everyone back on track. It wouldn’t be an overstatement to call a workshop like this a “dumpster fire” — we’ve certainly used that term ourselves in the past. Those projects are tough. Not only are you physically exhausted afterwards, but you’re somewhat emotionally beaten down, left to ponder what went wrong and how you can avoid the same thing happening again in the future. It’s not fun, but as we’ve come to realize, it can be incredibly helpful.</p><blockquote><strong>“Failure is simply the opportunity to begin again, this time more intelligently.” — Henry Ford</strong></blockquote><p>Nobody likes to fail, but the truth is that without failure, it can be difficult to really improve. When things are going well, it’s generally hard to find a compelling reason to innovate — why fix what’s not broken? It’s the bad experiences (like a poor workshop in our case) that give you the opportunity to take a step back, reevaluate things, and make some changes that help to ultimately improve your offering.</p><p>For us, after a recent workshop that went poorly, this meant taking a hard look at some of the criteria we use to evaluate the types of projects we take on — something that we hadn’t previously seen a need to revisit. As a result of that exercise however, we’ve now better defined the type of work we want to get involved with. Those changes — which we likely wouldn’t have made without the motivation of that bad workshop — have made our offering stronger, and will ultimately benefit future groups and projects.</p><p>Dumpster fires aren’t generally fun, but if you use them as a learning opportunity, they can be extremely valuable.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a3936cff8a1e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ux-for-the-win/why-everyone-needs-the-occasional-dumpster-fire-a3936cff8a1e">Why Everyone Needs The Occasional Dumpster Fire</a> was originally published in <a href="https://medium.com/ux-for-the-win">UX for the win!</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[An intro to Design Thinking]]></title>
            <link>https://uxdesign.cc/an-intro-to-design-thinking-c8879d7a88ac?source=rss-4ee03e1dcb85------2</link>
            <guid isPermaLink="false">https://medium.com/p/c8879d7a88ac</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[user-centered-design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[user-experience-design]]></category>
            <dc:creator><![CDATA[Greg Smith]]></dc:creator>
            <pubDate>Tue, 08 Jan 2019 17:36:59 GMT</pubDate>
            <atom:updated>2020-05-13T13:55:44.451Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Wall full of post-it notes" src="https://cdn-images-1.medium.com/max/1024/1*gw6L04RqzthPtqBkHjkHBw.jpeg" /></figure><p>My team and I love Design Thinking. Like <em>really</em> love it. Which is good, I suppose, given that it’s a core focus of our job — going around and introducing others to the concept, and then helping them apply it to various business challenges they’re trying to solve. We live and breathe it in everything we do, both professionally and personally, because it’s just one of those things that can’t be “turned off” once you know it. We often joke that it’s something akin to <a href="https://www.youtube.com/watch?v=zQ1_IbFFbzA">that scene from The Matrix</a> where Neo is offered two pills. One pill — the blue one — makes him go back to sleep and continue living the life he always has. The other one — a red pill — opens his eyes to the world around him so that he can see things as they truly are. That might be a little extreme as an example, but it’s not too far from the truth — once you’ve seen the benefit of taking a user-centric approach to problem solving, you can’t help but notice all the instances in which people <em>don’t</em> do it!</p><p>Given our obsession with design thinking, we can sometimes lose sight of the fact that not everyone is as familiar as we are. In fact, it’s probably a fair assumption that lots of people have never even heard of it (gasp!). Well, if you’re one of those people, fear not, this post is for you.</p><h3><strong>So, what is design thinking?</strong></h3><p><a href="https://www.ideo.com/about">IDEO</a>, the company widely credited with inventing design thinking, defines it simply as “a process for creative problem solving”, but let’s go a little deeper.</p><p>At its core, design thinking is a methodology for solving human-centered problems. A human-centered problem being one which directly involves a human being — usually your customer or user. So for example, while design thinking can’t help you figure out how to solve that algebra equation your kid brought home from school (what’s a coefficient again?), it <em>can</em> help you figure out how to improve the usability of your website. The difference being that the former problem doesn’t have a human at the center of it, whereas the latter does — the one that’s trying to navigate your site.</p><p>While design thinking is often associated with the development of physical or digital products, it can also be applied to more experiential problems, like improving the efficiency of your customer service hotline. It’s even been used to come up with solutions to things like hunger, poverty and how to get drinking water to a remote third-world village. <em>Anything</em> that has a human being at the center of it.</p><h3><strong>How does it work?</strong></h3><p>While incredibly powerful when done correctly, design thinking isn’t particularly complex or difficult. It’s really about simple mindset shifts and ways of asking questions differently.</p><p>Design thinking can be applied in any number of ways, but the standard flow goes something like this…</p><figure><img alt="Design thinking process: Empathize, Define, Ideate, Prototype, Test" src="https://cdn-images-1.medium.com/max/1024/0*1CKHsZhKYW7u3JTs" /></figure><p><strong>Empathize: </strong>One of the fundamental cornerstones of design thinking, the logic goes that ‘in order to truly solve for your user, you first need to put yourself in their shoes’. This is done by gathering data — qualitative data from something like an interview generally being the best suited for this step — in order to really immerse yourself in the experience that your users are having. This is critical to the process, and is the only way to keep teams from solving for themselves, or based on their own assumptions.</p><p><strong>Define: </strong>Upon immersing yourself in the experience of your users, you’ll then clearly define who specifically they are and what problems they have. Most products or services have multiple user types they need to cater to, so this step helps to narrow your focus on the one or two you’re most interested in solving for in the near term.</p><p><strong>Ideate: </strong>Next, you’ll start to come up with solutions to that user’s problems, confident that those ideas are grounded in real data. You’d be amazed how many projects just jump to this part of the process, getting people together in a conference room to brainstorm ideas based on a potentially made-up problem that hasn’t been validated.</p><p><strong>Prototype: </strong>Once you’ve settled on an idea or two, it’s time to prototype. The idea here is to quickly build something that you can use to learn whether or not you’re on the right track.</p><p><strong>Test: </strong>Finally, it’s time to test your idea… with real users! Using your prototype, you’ll find out whether or not people understand your idea, and whether or not they like it. These findings then feed back into the process such that it’s continually iterative.</p><h3><strong>What design thinking isn’t</strong></h3><p>We’ve seen design thinking help teams come up with truly innovative solutions time and again. It’s an invaluable tool, and can be applied to a huge range of problems, but it’s worth noting some of the most common misconceptions people have.</p><p><strong>Design thinking isn’t something only designers can do.</strong> While plenty of creative-types leverage design thinking in their roles, it’s something that absolutely anyone can do. It doesn’t require a degree in graphic design, just a commitment to the process and a passion for solving problems.</p><p><strong>It’s not a ‘check the box’ activity.</strong> It’s not something you just insert as an additional step within your existing process, because design thinking is an entire process in of itself. You can’t just “throw it” at a problem you’re trying to solve. Properly leveraging design thinking means truly shifting you and your team’s mindset and re-evaluating the fundamental way in which you solve problems. In many instances, it also means being open to the possibility that the problem you’re trying to solve isn’t actually the right one.</p><p><strong>It’s not something you can rush.</strong> While it’s entirely possible to navigate most of the process in just a few days, the Empathize phase in particular generally takes some time. It’s not always easy to identify a representative subset of your users, and once you do, you then need to schedule some time to talk in-depth with each of them. Mind you, we’re not talking about months here, but it’s not unusual for it to take a few weeks to gather valuable, usable data. And since this data is the basis of everything else you’ll do in the subsequent steps, it’s not something you can skimp on.</p><p><strong>It doesn’t assume any particular solution. </strong>We often see teams who already have a solution in mind — maybe a new technology or tool they’ve come across — and who are working to find a problem to align it with. Design thinking is focused first and foremost on identifying the problem, and only then pivoting to ideas as to what solutions might help to solve it.</p><p><strong>It doesn’t shy away from failure. </strong>Design thinking is an iterative process, meaning the underlying assumption is that you won’t get it 100% right the first time. We sometimes find that teams coming out of one of our workshops have determined that the idea they prototyped and tested isn’t one that ultimately solved the problem. That’s fantastic! Learning that something won’t work is just as valuable as learning that something will — especially when you’ve come to that realization after just two days and a few hundred post-it notes. Think of the cost involved had that idea been fully built and launched before realizing it wasn’t hitting the mark.</p><p>Like Neo, after taking the red pill, there’s no going back to the old way of doing things once you’ve seen the benefit of taking a user-centric approach. The most successful teams put their user at the center of all they do, and ensure that each and every decision that’s made can be mapped back to the problems they’re trying to solve for. It’s truly a way of thinking as much as it is a process, but it can lead to some incredible insights when used properly. It’s just a matter of choosing the right pill.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Fux%2F&amp;image=http%3A%2F%2Fapi.screenshotlayer.com%2Fapi%2Fcapture%3Faccess_key%3Dfe59908dad3baab69ffab249a2224b03%26viewport%3D1024x612%26width%3D1000%26url%3Dhttps%253A%252F%252Fupscri.be%252F50d69a%253Fscreenshot&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/56fab36ee3c7d3f16dadba4f2528828d/href">https://medium.com/media/56fab36ee3c7d3f16dadba4f2528828d/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c8879d7a88ac" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/an-intro-to-design-thinking-c8879d7a88ac">An intro to Design Thinking</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Don’t Aim For Perfect: The Importance Of Iteration]]></title>
            <link>https://medium.com/ux-for-the-win/dont-aim-for-perfect-the-importance-of-iteration-7c78af426af8?source=rss-4ee03e1dcb85------2</link>
            <guid isPermaLink="false">https://medium.com/p/7c78af426af8</guid>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[design-sprint]]></category>
            <dc:creator><![CDATA[Greg Smith]]></dc:creator>
            <pubDate>Fri, 19 Oct 2018 00:51:15 GMT</pubDate>
            <atom:updated>2020-05-12T14:01:07.573Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/676/0*P210IXbtGJykfl6T" /></figure><p>Does the process above look familiar? If you’ve ever had a hand in developing and launching any sort of product or service, it more than likely does. Depending on the size and complexity of the project in question, this process can take weeks or months to cycle through fully, and in the most extreme cases, can take years. Think about that for a second… it can be months (or years!) from the point in time a decision has been made about the direction of a product or service, until the time it’s launched to the market. A lot can happen in that span. For one, the market — which has a tendency to change pretty quickly these days — may very well have shifted in the time you were off building your product. So even if the idea was great to begin with, and your execution in delivering it was flawless, you may have missed your opportunity by the time you actually launch it — either because someone else beat you to the punch or because the problem you originally set out to solve no longer exists.</p><p>And that’s all assuming that the idea was correct to begin with. Unfortunately, an all too common situation is that a company <em>thinks </em>they’ve come up with an idea to address a need in the market, sets out on the long journey of building and launching it, and only then finds out that the idea doesn’t resonate with customers. Maybe it’s because they misunderstood the need itself, or perhaps their execution on the idea simply didn’t make sense to the user, but in either case, the end result is a product or service with no viable market. That’s an expensive mistake to make when you consider the amount of time, effort and money that likely went into creating the solution over those long months or years.</p><p>To be fair, the desire to want to deliver a ‘perfect’ product to customers is entirely understandable. But the reality is that it’s virtually impossible to build the perfect solution right out of the gates, no matter how much research was done in advance, or how meticulous you were in the product development itself. Despite the best planning, you likely won’t know exactly what your customers want or need until they actually start using your product. Things you were certain they would love will be ignored, while seemingly small features will be the ones that they end up depending on most.</p><p>Given that so many of today’s product development methodologies were born out of processes designed around physical products, where quick iteration was not logistically or financially practical, it’s no surprise that many companies still default to a product life cycle that favors a substantial investment in up-front development. But of course, that’s not the world we live in anymore — new digital delivery models have paved the way for quick and continuous iteration. So by shifting the mindset from one of ‘perfection’ to one of iterative improvement, a company can dramatically increase it’s odds for success.</p><p>By quickly getting an early version of the product in the hands of your customers, you’ll be able to capitalize on the current market trends <em>and</em> you’ll get immediate feedback on what features your customers want and need. This allows you to prioritize future development efforts, and ensures your product can mature along with the market itself. So instead of the traditional development cycle outlined above, it can instead look something like this…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/294/0*yRDW9PwWb6nFId-3" /></figure><p>To be clear, I’m not suggesting you build and launch a product without first having validated the need for it, or having done some degree of user testing — I’ve spent plenty of time in the past talking about the crucial importance of both of those things. But all of that can be accomplished in a matter of weeks, <a href="https://medium.com/@gsmth00/seven-people-five-days-one-idea-go-d27d58b4951e">if not days</a>, meaning you can very quickly get to a point where you’re confident in the direction your team is heading.</p><p>The mantra of “failing fast” has become a bit of cliché these days, but for good reason. Better to fail fast and know in the near term whether or not you’re on the right track, then to fail slowly and only come to that realization much later on.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7c78af426af8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ux-for-the-win/dont-aim-for-perfect-the-importance-of-iteration-7c78af426af8">Don’t Aim For Perfect: The Importance Of Iteration</a> was originally published in <a href="https://medium.com/ux-for-the-win">UX for the win!</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design Sprints Can Be Dangerous]]></title>
            <link>https://medium.com/ux-for-the-win/design-sprints-can-be-dangerous-e437118de276?source=rss-4ee03e1dcb85------2</link>
            <guid isPermaLink="false">https://medium.com/p/e437118de276</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[design-sprint]]></category>
            <dc:creator><![CDATA[Greg Smith]]></dc:creator>
            <pubDate>Thu, 20 Sep 2018 12:44:21 GMT</pubDate>
            <atom:updated>2020-02-03T20:16:48.309Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uVJ6rC4ii93q6zWC1FgvDg.jpeg" /></figure><p>As I’ve mentioned <a href="https://medium.com/@gsmth00/seven-people-five-days-one-idea-go-d27d58b4951e">previously</a>, Design Sprints have recently come into their own within the world of product management, and are increasingly being used by companies of all shapes and sizes as a way to jump start innovation and introduce more agile ways of working. As a result, you don’t have to look far these days to find a story extolling the benefits of Sprints, and citing the success of the organizations that use them. It’s no secret that my team and I are big fans of the Design Sprint, and believe wholeheartedly in the outstanding value it provides, but as with any tool, it can do more harm than good when not used properly.</p><p>One of the primary benefits of a Design Sprint is its ability to break a team out of their normal process and give them a means of accelerating their work on a particular project over the course of just a few days. This can help teams push forward an existing project that’s stalled, or kick off a new one altogether, all of which is a huge positive… as long as the direction the team is headed is the <em>right</em> one.</p><p>Unlike Design Thinking, which is focused entirely on ensuring that the team is solving the right problem and for the right user, a Design Sprint makes the assumption that you already know that information, and therein lies the rub.</p><p>If your team doesn’t know who your end user really is, or what problem you’re trying to solve for them, then while a Design Sprint will certainly give you a big boost towards creating <em>a</em> solution, there’s a very real chance that it won’t be the <em>right</em> solution. You’ll have invested a fairly substantial amount of effort over the course of the Sprint only to find that your final output falls flat, because your users don’t actually need it. Or even worse, your testers will respond positively to your prototype — leading you to believe it’s something you should pursue further — only to find out much later that the people you were testing with weren’t representative of your actual users. Imagine the time, effort and money that might be wasted on a project like that.</p><p>We see this situation all the time, and have come to refer to it as a “solution without a problem” — teams creating something based on their own internal assumptions about who the user is and/or what their pain points are, without any real data to back up that point of view. That’s a dangerous situation to begin with, but the potential pitfalls are only multiplied when those assumptions are then fed into an accelerator like a Design Sprint.</p><p>Of course, this isn’t to say you shouldn’t consider using a Design Sprint — because you absolutely should! — just that you need to be careful to ensure your inputs are based on <em>real</em> data. It’s for this reason that we’ve found a Sprint to be the perfect complement to Design Thinking. In the course of a short Design Thinking project, you can identify your users, narrow in on what specific problems they have within a given area, and generate some high-level ideas for how you might solve those. Being able to then feed that into a Design Sprint as a means of accelerating the development of your solution is a natural next step and can be a very powerful thing. So go forth and Sprint! Just do it smartly.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e437118de276" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ux-for-the-win/design-sprints-can-be-dangerous-e437118de276">Design Sprints Can Be Dangerous</a> was originally published in <a href="https://medium.com/ux-for-the-win">UX for the win!</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Customer Experience Has Nothing To Do With Your Org Chart]]></title>
            <link>https://medium.com/ux-for-the-win/the-customer-experience-has-nothing-to-do-with-your-org-chart-48d9229c9da9?source=rss-4ee03e1dcb85------2</link>
            <guid isPermaLink="false">https://medium.com/p/48d9229c9da9</guid>
            <category><![CDATA[customer-experience]]></category>
            <dc:creator><![CDATA[Greg Smith]]></dc:creator>
            <pubDate>Tue, 18 Sep 2018 14:01:17 GMT</pubDate>
            <atom:updated>2020-02-03T20:16:49.976Z</atom:updated>
            <content:encoded><![CDATA[<p>Companies often make decisions based on how their internal teams are organized. It’s an easy trap to fall into, but it can also be a costly one.</p><p>We sometimes forget that <strong><em>we</em></strong> are not our users/customers, and that the things we’re building need to work for <strong><em>them </em></strong>and not <strong><em>us</em></strong>. Beyond that, internal silos — while important for the day to day operations of a company — often come at the expense of a well defined end-to-end customer experience. And the larger an organization is, the more likely it is to suffer from this “organizational blindness”.</p><p>For example, the Marketing team is often charged with filling the top of the proverbial “funnel” through various user acquisition efforts. At that point, it likely falls to the Product team to ensure that the customer’s experience with the website/app/event/etc is a positive one. As a customer moves further down the funnel, the responsibility will transition to a Sales team, whose job it is to convert the lead. Then the Engagement/Fulfillment team takes over and does the hard work of actually delivering on what was promised. At some point, Marketing is likely brought back in, and asked to define the ongoing experience that the customer has in the way of newsletters and other communications. And on and on. Also in the mix are groups like Customer Service/Support, Public Relations, Legal, etc — all of which have an equally important role to play in the customer journey. The same model applies, with slight variations, to every company, regardless of whether they sell a physical product or a professional service.</p><p>Hopefully these groups are talking to one another, and sharing key metrics, in order to constantly improve and optimize, but that’s not enough… without a clear, shared understanding of the <strong>customer</strong> to steer the decisions that each team makes, the result will likely be a disjointed and confusing mess. Each team will find themselves simply executing on their specific objectives, without thinking about the impact to the end user’s overall experience.</p><blockquote><strong><em>Customers don’t care about how your organization is structured. To them, your product or service is one, continuous experience, characterized by a series of touchpoints, many of which take place long before — and after — the traditionally accepted “sales cycle” that we tend to focus on.</em></strong></blockquote><p>The need for organizational structures isn’t going to change, so in order to combat this tendency to make decisions based on internal factors alone, it’s critically important that companies have a ‘user-centric’ mentality in all that they do — a common understanding that each team can rally around as they make decisions. Only then can every team in the organization ensure their actions are having a positive impact on the end user and their experience with the brand.</p><p>This shared knowledge base should include artifacts like personas— which help define who your user is, and what’s important to them — as well as user journey maps, which will provide a shared understanding of where your customer touchpoints are. And while it should go without saying, I’ll say it anyways… these items must all be developed based on <em>actual</em>, <em>objective</em> data you collect about — and from — your users, as opposed to subjective and unsubstantiated <em>opinions</em> of who the user is.</p><p><em>This was adapted in part from an article by @storyalbert, </em><a href="https://medium.com/@storyalbert/one-year-of-design-at-the-worlds-largest-vc-firm-687af67cbb33"><em>here</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=48d9229c9da9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ux-for-the-win/the-customer-experience-has-nothing-to-do-with-your-org-chart-48d9229c9da9">The Customer Experience Has Nothing To Do With Your Org Chart</a> was originally published in <a href="https://medium.com/ux-for-the-win">UX for the win!</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Seven People. Five Days. One Idea. Go!]]></title>
            <link>https://medium.com/ux-for-the-win/seven-people-five-days-one-idea-go-d27d58b4951e?source=rss-4ee03e1dcb85------2</link>
            <guid isPermaLink="false">https://medium.com/p/d27d58b4951e</guid>
            <category><![CDATA[design-sprint]]></category>
            <dc:creator><![CDATA[Greg Smith]]></dc:creator>
            <pubDate>Tue, 18 Sep 2018 13:47:38 GMT</pubDate>
            <atom:updated>2020-02-03T20:17:03.604Z</atom:updated>
            <content:encoded><![CDATA[<p>One of the most challenging things I believe we all face in our day to day professional lives is finding the time to do ‘meaningful’ work. It’s all too easy to spend an entire day answering emails and jumping from one urgent task to the next, only to look back at the end of the day and wonder what it is that you <em>actually </em>accomplished. We’ve all been there.</p><p>It’s for this reason that the concept of true, uninterrupted work seemed so appealing to my team at work — the idea of spending time focused on a single (and meaningful) task. The idea itself isn’t a new one of course. You’ve probably seen it laid out in some form or fashion in any productivity book or blog you’ve ever read. But the concept has recently gained some added traction in the product management world, thanks to a book called <a href="https://www.amazon.com/Sprint-Solve-Problems-Test-Ideas/dp/150112174X/">Sprint</a>, written by <a href="https://medium.com/u/f230699aec44">Jake Knapp</a> and a few other guys from Google Ventures. The concept is simple enough — dedicate five consecutive days to digging into a single problem. The problem itself could be anything… from evaluating a potential new product within an existing business, to validating the idea for an entirely new business altogether. But no matter what the problem is, the goal remains the same: dedicating the time to really and truly exploring it.</p><p>The book is a great read, and I <em>highly</em> recommend it for anyone interested in learning more about Design Sprints, but at a high-level, the process goes something like this…</p><ul><li><strong>Day 1: </strong><em>Map</em> out the specifics of your problem. What’s your long term goal? What are the questions you need to answer in order to be able to get there? Who are the experts that hold knowledge likely to be of value to you?</li><li><strong>Day 2: </strong><em>Sketch</em> out some rough ideas based on the information you’ve gathered during day one</li><li><strong>Day 3: </strong><em>Decide</em> on a particularly promising idea (or two) that you want to build out and explore further</li><li><strong>Day 4:</strong> Build a <em>prototype</em> of the idea(s)</li><li><strong>Day 5: </strong><em>Test</em> the prototype(s) with <em>real</em> users, and synthesize the insights you gain into some actionable next steps</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/716/1*jXhPiKMQr1OBuKVkhFE5dQ.png" /></figure><p>Of course, that’s just a quick outline — there’s a whole book’s worth of detail around each of those steps! — but it gives you an idea of what’s involved.</p><p>Having recently read the book ourselves, our team decided to test the Sprint concept against a problem of our own — building a live chat experience on our company website. Live chat was something we had discussed in the past, but we’d never been able to find the time to take it beyond the conceptual stage. That said, we had reason to believe that live chat would add some real value to the user experience on our site, so there was a definite upside to figuring it out. It was for these reasons we thought it would be a great fit. So we decided on who the right team for the Sprint would be, pulling in a mix of subject matter specialists, and with that, we were off…</p><p>Well, almost. As you can imagine, finding five consecutive days for an entire team to block out their calendars and commit to nothing else but this singular project was tough. We had to look a few weeks out, and even then some of us still needed to move things around. But, we were dedicated and eventually found the time to make it work.</p><p>With that figured out, we turned our attention to the other challenge we knew we were going to be dealing with: the fact that everyone would be remote. Most of the time, these Sprints are done in person, with everyone sitting together in a room somewhere, making particularly heavy use of a whiteboard and Post-it notes. In our particular situation however, that wasn’t going to be feasible, so we had to figure out how to make the process work in a fully-remote and therefore, fully-digital, setting. It took a little ingenuity, a fair amount of work up front, and the use of our favorite digital collaboration tool, <a href="https://mural.co/">MURAL</a>, but we figured out a framework and process that minimized the pitfalls of being remote, while also optimizing the benefits of digital technology, enabling us to do things that wouldn’t have been possible in a physical environment.</p><p>So off we set. And five days later, we were done!</p><p>“<em>Hold on just a minute!</em>”, I hear you saying. “<em>You skipped over the Sprint itself! What gives?!</em>”</p><p>Well, the fact of the matter is that a Design Sprint is really something you need to experience for yourself in order to truly appreciate its power. No blog post would ever do justice to all the ground you cover in the course of those five days — the ‘ah-ha’ moments you invariably have, the disagreement and discussion amongst the team, the feeling of hitting the wall, the feeling of then breaking through said wall, the excitement of watching your prototype — something you built with your own hands! — being put in front of a user and seeing them respond to it. It’s pretty amazing! But with that said, I’ll do my best to capture the highlights…</p><ul><li><strong>Practice makes perfect:</strong> The Sprint went remarkably well. That’s not to say that things went perfectly of course. There was bound to be some issues that cropped up as a result of it being our first time through the process as well as due to the remote/digital nature of it. But as we debriefed after a long couple of days, we were amazed at how much we had accomplished, and frankly, at how much fun we had during the process — it’s pretty exhilarating being able to step back at the end of your week and know that you accomplished something truly meaningful.</li><li><strong>Remote work works:</strong> Conducting the Sprint remotely actually wasn’t that bad. You do lose a little in the way of the energy and focus that comes with having everyone in the same room, but with the right mix of technology, you can more than make up for that. We used Google Hangouts, Google Slides, MURAL and Spotify (gotta have our jams!) throughout the week, and also spent plenty of time jotting down ideas on good old fashioned pen and paper. As long as the team can dedicate themselves to the Sprint, meaning closing email, turning off notifications, silencing their phone, etc, it can be done!</li><li><strong>“The best requirements we’ve ever gotten”:</strong> ← That was an actual quote from the developer we had invited to join our Sprint team. At the conclusion of our week, we had validated some of our ideas around what would work well with a live chat experience, had invalidated others, and had stumbled across new ones that we never would have considered otherwise. We had built a fully functional live chat prototype, and, using the information we had compiled along the way, had basically developed a business case and in-depth requirements document, not to mention gaining buy-in from the various stakeholders, designers and developers that had been a part of the process. We’d also tested the prototype with some real users and so knew what changes should be made as we moved forward with building out a real, functional product. Not bad for a few days worth of work!</li><li><strong>Time well spent:</strong> The value of dedicated, focused work cannot be understated — in fact I’ve found myself incorporating some elements of the Sprint methodology into my day to day process, just to ensure I don’t fall back into the same bad habits of filling my time with unfocused ‘busy work’. It may seem like a big ask carving out five days to focus on one thing, but it’s amazing what you can accomplish when you give yourself the space to really think. Of course, it’s not possible to carve out that much time for each and every thing you have on your plate, nor should it be necessary — a Sprint is best reserved for those big, important ideas that have a lot of upside if you get them right (and a lot of downside if you don’t).</li></ul><p><a href="https://www.amazon.com/Sprint-Solve-Problems-Test-Ideas/dp/150112174X/">The book</a> is an excellent place to start if you’re interested in learning more, but you really should think about doing one for yourself.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d27d58b4951e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ux-for-the-win/seven-people-five-days-one-idea-go-d27d58b4951e">Seven People. Five Days. One Idea. Go!</a> was originally published in <a href="https://medium.com/ux-for-the-win">UX for the win!</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>