<?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 Brian Frank on Medium]]></title>
        <description><![CDATA[Stories by Brian Frank on Medium]]></description>
        <link>https://medium.com/@brian_frank?source=rss-8b56c3ea03a6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*3HFObZzzXPDml7SvXxJhAg.jpeg</url>
            <title>Stories by Brian Frank on Medium</title>
            <link>https://medium.com/@brian_frank?source=rss-8b56c3ea03a6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 05:48:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@brian_frank/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The simplest way to improve user surveys]]></title>
            <link>https://uxdesign.cc/the-simplest-way-to-improve-user-surveys-760bf0149a7e?source=rss-8b56c3ea03a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/760bf0149a7e</guid>
            <category><![CDATA[surveys]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Brian Frank]]></dc:creator>
            <pubDate>Thu, 17 Jan 2019 20:50:03 GMT</pubDate>
            <atom:updated>2020-07-21T02:15:22.578Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Survey on a table with questions crossed out." src="https://cdn-images-1.medium.com/max/1024/0*ulFLmbX2-vIp2sDZ.jpg" /></figure><p>We get asked for user survey advice a lot. We find ourselves offering the same, simple piece of advice: ask more open-ended text (or numeric) questions instead of relying so heavily on multiple-choice.</p><p>This applies especially to surveys done near the start of a research process. We don’t necessarily recommend starting research with a survey (see our post on <a href="https://res.im/blog/ux-survey-design-why-and-when-to-run-a-user-survey/">why and when to run a user survey</a>), but sometimes it’s necessary, like when using a questionnaire to recruit and screen interview participants.</p><p>Multiple choice feels normal because we usually see survey results presented in bar graphs, pie charts, or other formats that require data to be categorized or segmented. But what we don’t see is that those categories are often created after data is analyzed.</p><p>If you start with open-ended responses, you can usually manage to clean, categorize, and simplify your findings later. But you can never extract more precision from ambiguous multiple-choice responses.</p><p>The graph below is from a <a href="https://uxtools.co/survey-2017#demographics">design tools survey</a> done in 2017. A question asked respondents the size of their design team. 66% of respondents identified with the smallest team size (1–10), while only 3% identified with the three largest options combined.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/0*1e8S62SmQ5QCszpm.png" /><figcaption>Graph from a 2017 design tools survey</figcaption></figure><p>This data leaves a lot of uncertainty about the actual distribution of team sizes.</p><p>The <a href="https://uxtools.co/survey-2018">2018 version of the survey</a> was slightly improved (to the designer’s credit). The 11–100 option is split into two smaller ranges, but the majority of responses (59%) are still lumped into a single segment that begs to be broken up.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SflX9c57hFHTUA2G.png" /><figcaption>Graph from the 2018 version of the design tools survey</figcaption></figure><p>This data would be help answer more questions if respondents were asked to simply enter the number of people on their team.</p><p>A bigger concern with the multiple-choice format is the risk of bias. The options you include (or exclude) and how you word them can easily reinforce blind spots and lead people to answer in ways that don’t accurately represent reality. You’re imposing a mental model and vocabulary on respondents rather than learning how to improve your current understanding.</p><p>Try to start with basic text (or numeric) responses as a default. Send the survey to a small, representative sample. If it’s important enough, talk to people as they’re taking the survey, like a usability test. Then use the responses and feedback to design multiple-choice questions — after you become more confident in the options and language you’re using.</p><h3>When to use multiple choice</h3><p>There are valid reasons to use multiple choice. Thousands of open-ended responses can be time consuming to analyze, so multiple-choice questions are usually preferable for large-scale surveys. However, if the questions are poorly designed and the data isn’t useful, then your time (and your respondents’ time) was wasted anyway.</p><p>If participation/completion rate is a major concern, well-designed multiple choice questions can help reduce participant effort, especially for people using mobile or touchscreen devices. On the other hand, poorly designed multiple choice questions actually make the survey more difficult. At minimum people are forced to read and understand a list of options before they can respond.</p><p>Rather than treating multiple choice questions as the default to be used whenever possible, try to use multiple choice <em>only when necessary:</em></p><ul><li><strong>When the responses (or the question itself) would otherwise be ambiguous</strong>, like when asking respondents to describe their current situation or status, or when asking about degree of satisfaction or agreement/disagreement on a (balanced) rating scale.</li><li><strong>When you need to make sure respondents consider specific options</strong> before responding, like when you want to learn about competing preferences or priorities.</li><li><strong>When the options/categories are known with a high degree of certainty</strong> and you want to minimize needless variation, like when asking people which country they live in, or to use logic and branching to tailor the survey to different groups of respondents.</li></ul><p>If you’re really struggling, that may be a sign that a survey isn’t the right method. Surveys are useful for testing well-developed hypotheses, but not as useful for exploring uncertain territory or generating new, rich insights.</p><h3>Don’t be afraid of a little extra effort</h3><p>If the goal of the survey is to produce some charts as quickly as possible, then analysing open-ended responses can be a pain. But if your goal is to deepen your understanding and make better decisions, then open-ended responses can produce some of the most insightful data you get from a survey.</p><p>Basic spreadsheet and qualitative analysis skills will help to tag and analyze responses. Some survey tools include text analysis features to categorize open-ended responses. This process can be time consuming for hundreds of responses, but for smaller samples (or for short screener questionnaires) it might actually be faster and easier than debating multiple versions of the survey before launching it.</p><p>Remember that participants will experience the survey as part of the overall experience of your organization, product, or brand. When starting with a high level of uncertainty, a little bit of preliminary research helps everyone involved.</p><p><em>Originally published at </em><a href="https://res.im/blog/the-simplest-way-to-improve-user-surveys/"><em>res.im</em></a><em>.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fux&amp;image=https%3A%2F%2Fucarecdn.com%2F6e8986c7-e64a-4116-9afb-fd71a476f0a9%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/a19f46680bac3cbdc42953c920d0c104/href">https://medium.com/media/a19f46680bac3cbdc42953c920d0c104/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=760bf0149a7e" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/the-simplest-way-to-improve-user-surveys-760bf0149a7e">The simplest way to improve user surveys</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[Learning from Amazon’s HQ2 Horse Race]]></title>
            <link>https://medium.com/@brian_frank/learning-from-amazons-hq2-horse-race-bdc41c636c3c?source=rss-8b56c3ea03a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/bdc41c636c3c</guid>
            <category><![CDATA[amazon]]></category>
            <category><![CDATA[cities]]></category>
            <category><![CDATA[economic-development]]></category>
            <dc:creator><![CDATA[Brian Frank]]></dc:creator>
            <pubDate>Sat, 09 Sep 2017 16:35:02 GMT</pubDate>
            <atom:updated>2017-09-10T12:49:44.407Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DEOqaaQSQpImdz83VAQiWA.png" /></figure><p>Trying to guess which city <a href="https://www.amazon.com/b?ie=UTF8&amp;node=17044620011">Amazon will pick for its “second headquarters”</a> is kind of futile, but I can’t resist. Nor, it seems, can <a href="http://www.npr.org/sections/thetwo-way/2017/09/07/549255564/amazon-set-to-build-a-second-hq-and-cities-say-pick-me">every North American mayor</a> resist throwing their city’s name into the hat.</p><p>A lot of people will get their hopes up. That’s fine. It’s a chance to learn and improve the odds of attracting (and/or retaining) more realistic opportunities in the future. As an observer it’s also an opportunity to think about how our urban and suburban environments are changing.</p><p>Importantly, Amazon has a knack for anticipating what’s coming and doing things their own way. And they’re ruthlessly pragmatic. They’re not the type of tech company to go in for vanity projects or promote utopian ideals. Their selection will probably influence what other companies will look for and how cities will try to attract them for years to come. (And it won’t be which mayor has the most polished platitudes or <a href="http://www.businessinsider.com/jeff-bezos-email-against-powerpoint-presentations-2015-7">pitch deck</a>.)</p><p>Hopefully the whole thing doesn’t make cities and governments even more acquiescent to corporate whims and demands, especially the more short-sighted, opportunistic ones.</p><h3>What We Can Learn</h3><p><a href="https://www.geekwire.com/2017/six-cities-amazon-consider-second-headquarters/">Brookings Institution’s Richard Shearer</a> (ht <a href="https://twitter.com/stateofthecity/status/906341714973130752">Brian Kelcey</a>) has a good argument why the proposal process for a lot of cities will mostly be a waste of time. Maybe I’m optimistic but I’m hoping it doesn’t have to be a <em>total</em> waste of time.</p><p>Some people are already trying to take lessons from the HQ2 RFP — or at least capitalize on it as a way to promote their existing ideas — e.g. “<a href="https://t.co/x5CkiZLKJb">shoulda voted for transit</a>,” etc. It’s largely speculation at this point as to how much emphasis Amazon ends up putting on things. Even after the decision it will probably be dangerous to read too much into it. Amazon is, after all, a unique company, and this is a unique project, but it does make for some potentially fruitful thought experiments and “what if” discussions.</p><p>A more realistic scenario would be, what if Amazon (or any big tech company) hired someone in our city who wanted to stay? What if Amazon bought a startup in town? Would Amazon have reasons to continue to invest and hire more people? Would they have reasons to turn it into a major centre devoted to some specific aspect of the business, like robotics research, logistics, media production, customer service? These are the types of opportunities that are probably sitting under our noses more often than we realize.</p><p>Let’s not let the circus distract us. If I were a long-shot I’d want my city to approach the HQ2 contest with the goal of ongoing, incremental investment—building on the reasons that companies like Amazon have already set up shop (even satellite offices), continuing to draw other employers looking for the same kind of skills and talent.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vwoTeFkzM4IF7fBOK2TGyw.png" /></figure><h3>Where’s Amazon Now?</h3><p>There are Amazon development offices in <a href="https://www.amazon.jobs/en/locations/?&amp;continent=north_america&amp;cache">well over a dozen North American cities</a> (not including fulfillment/shipping centres and data centres). I figure if Amazon hasn’t already had a reason to stick a few hundred software developers somewhere they’re unlikely to find it much more attractive for tens of thousands (but who knows).</p><p>It’s also worth noting how Amazon used the word “stable” in their RFP. “Stable and business-friendly environment.” “Stable business climate.” What could be more stable than a known entity?</p><p>Apart from its current head office (“HQ1”?) in Seattle, Amazon has software development offices in most of the usual tech/business hubs: the <strong>Bay Area</strong>, <strong>Southern California</strong>, <strong>New York</strong>, <strong>Toronto</strong>, <strong>Boston/Cambridge</strong>, and <strong>Austin</strong>. Any of those cities would meet the basic criteria for HQ2 and could conceivably be contenders, though I suspect there’s not enough elbow room in California or New York, so I’d only look at Toronto, Boston/Cambridge, and Austin.</p><p>Other large cities like Chicago, Dallas, and Atlanta have Amazon offices but zero/few job postings for software developers. Maybe they’re in the running, but I think people are putting more emphasis on the airport requirement than Amazon will. Most major metropolitan areas in North America have an airport that’s adequate for Amazon’s needs. I can’t imagine Atlanta jumping ahead of Toronto, for example, based on the fact that ATL is the busiest or 2nd busiest airport in the world and YYZ is “only” the 16th busiest.</p><p>More interesting to me are Pittsburgh, Minneapolis, Detroit, and Herndon, VA—all places where Amazon already has software development offices.</p><p><strong>Pittsburgh</strong> is a natural satellite office. It has attracted a lot of tech companies recently thanks to the computer science and engineering talent coming from top-ranked programs there. The city has also been accommodating to tech companies (maybe a little too accommodating, as in <a href="https://www.nytimes.com/2017/05/21/technology/pittsburgh-ubers-driverless-car-experiment.html?_r=0">the case of Uber</a>). But Pittsburgh is a little smallish and relatively isolated (compared to, say, Philly, DC, Baltimore, Boston, etc.).</p><p><strong>Minneapolis</strong> might seem even more unusual than Pittsburgh, but Amazon is a retailer and Minneapolis-St. Paul is also the home of Target and Best Buy (and less relevantly, 3M and General Mills). Perhaps most notably, it’s also the home of <a href="https://en.wikipedia.org/wiki/C._H._Robinson">C. H. Robertson</a>, a Fortune 500 logistics company that Amazon <a href="http://tcbmag.com/news/articles/2017/july/amazon,-primed">does a lot of business with</a>. But like Pittsburgh, Minneapolis may be on the small side and even more isolated. If Amazon wanted another northern outpost I’d expect them to go further east and maybe even across the border.</p><p><strong>Detroit</strong> is slightly larger and arguably more connected than Pittsburgh or Minneapolis but like them is a bit of an outpost. The most interesting thing Detroit has going for it is the <a href="https://www.theguardian.com/world/gallery/2013/jul/19/detroit-goes-bankrupt-in-pictures">space available to work with</a>. It’ll depend on how much Amazon ends up emphasizing “think big and creatively when considering real estate options” and how interested Amazon is in company town-building.</p><p><strong>Herndon (in Fairfax County) </strong>is a bit of an oddball in this group but it meets the basic requirements in the RFP. It’s a suburb of Washington, DC (Richard Florida’s <a href="https://twitter.com/Richard_Florida/status/906137004525662210">early pick</a> to win), close to Dulles Airport. They also seem to have been <a href="https://www.bizjournals.com/washington/blog/2013/07/amazons-herndon-employees-will-earn.html">fairly accommodating to Amazon</a> in the recent past, in terms of tax incentives and infrastructure upgrades. Fairfax County is a good reminder not to overlook the suburbs and get too fixated on the major urban centres as options.</p><p>Amazon has offices in a few other places too, like <strong>Phoenix</strong> and <strong>Vancouver</strong>. I know little about Phoenix except that it’s warm and dry (unlike Seattle) and has a lot of space around it for growth. Maybe it’s an option. Vancouver seems too close to Seattle, but who knows.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w3K64QwZmN0mFT5mDH646w.png" /></figure><h3>Last Thought: North American Politics?</h3><p>Toronto is a great choice on paper and a lot of people’s shortlist contender (I like <a href="https://www.geekwire.com/2017/six-cities-amazon-consider-second-headquarters/">GeekWire</a>’s initial take). Toronto meets all of the basic requirements in spades. But a successful bid will depend not just on the site(s) and the incentives in the proposal, and probably on politics.</p><p>It’s a safe bet that Donald Trump will have very strong, very public opinions about the possibility of $5 billion and 50,000 jobs going to Canada. And he has already expressed hostility to Amazon and Jeff Bezos. He has also helped throw buckets of money at companies to stay in the US. So it’s possible that the RFP’s openness to Canada (and presumably Mexico) is largely for bargaining leverage—a way to maximize incentives from all three levels of government and make Trump behave nicely. It could also be political leverage. Bezos could say, “if you want these jobs to stay in the US then we need skilled immigrants, we need DACA, we need visas, we need employees to not be afraid of getting back into the country,” etc.</p><p>Of course it’s also possible that Toronto is already on Amazon’s list as a top 2 or 3 pick from the start, and any potential political sideshow is just coincidental. Though as I write this I’m revisiting the notion of “stable business climate” in international terms…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bdc41c636c3c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Write an “Essential Reading” List]]></title>
            <link>https://medium.com/@brian_frank/how-to-write-an-essential-reading-list-3b8dfb889af0?source=rss-8b56c3ea03a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/3b8dfb889af0</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[books]]></category>
            <category><![CDATA[writing]]></category>
            <dc:creator><![CDATA[Brian Frank]]></dc:creator>
            <pubDate>Thu, 13 Jul 2017 19:50:51 GMT</pubDate>
            <atom:updated>2017-07-13T19:52:11.276Z</atom:updated>
            <content:encoded><![CDATA[<h4>Because we don’t need another list of 50 books every UX designer or product manager must read.</h4><p>Every so often a new list of “books every UX designer must read” makes the rounds. They’re generally either super-long or seemingly arbitrary, or both<em>. </em>Too many seem to include <em>every</em> book the author has read or heard of.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FSJvmoOc21gQ%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DSJvmoOc21gQ&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FSJvmoOc21gQ%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/670213ed6863709fad48e06c40c58c6a/href">https://medium.com/media/670213ed6863709fad48e06c40c58c6a/href</a></iframe><p>Don’t get me wrong. Lists are one of my guilty pleasures. Even the worst list provokes conversations that help build social and cultural connections.</p><p>As a lover of sports and music I spent a lot of my younger days hours in un-win-able debates over who’s the best rapper, guitarist, drummer, NBA point guard, NHL team captain, etc. But as endless and annoying as these exercises may be, they’re not <em>meaning</em>less. They helped me think about what I liked and why. They taught me what mattered to the people and communities around me, and where I stood within those communities (newcomer, insider, or outsider, etc).</p><h4>Tell Us Where You’re Coming From</h4><p>Recommendations are like gifts; they’re a form of social exchange that can say a lot about the giver and their relationship with the receiver.</p><p>Unless you’re generating recommendations with an algorithm or carrying them down a mountain on stone tablets, or literally just throwing together a random list to spam us with content marketing, embrace the personal and subjective side of recommendations. <a href="http://austinkleon.com/show-your-work/">Show your work</a>. Let us recognize and appreciate your quirks and biases. Otherwise we might just make our own guesses as to what those biases are.</p><p><em>Why did you put this reading list together? What kind of readers did you have in mind? How did you find out about your picks? How did your picks influence or help you? How do you think your recommendations will help us?</em></p><p>Examples:</p><ul><li>Josh Seiden’s <a href="https://medium.com/@jseiden/books-for-ux-managers-b0bac248ede0">Books for UX Managers</a> is personalized in a way that feels like casual suggestions from a friend or mentor. Instead of a massive list of “books every manager must read,” we get more modest suggestions of books to “consider,” “the best book on strategy I’ve encountered,” etc.</li><li>Christina Wodtke shared a list of <a href="http://eleganthack.com/drawing-books/">Drawing Books</a> as kind of a working bibliography within her writing process. It’s a fairly long list, but we know to look at most of the books on it as “could reads” rather than a guilt-inducingly long list of “must reads.”</li></ul><h4>Place Things in Relation to Others</h4><p>The American philosopher Richard Rorty described the critic’s task as “placing books in the context of other books.” Almost nobody reads a list of recommendations without any background knowledge. We each have our own influences and favourites. Give us some references to help figure out how closely our knowledge, taste, interests, and needs compare to yours.</p><p><em>What should we </em>not<em> read? How are your picks better than others we might have heard of? Which should we read first? Which could we skip or replace with something else? Which might be interchangeable or redundant?</em></p><p><em>The Wirecutter</em> does a great job of placing things in relation to others. An article might promise to merely tell you “<a href="http://thewirecutter.com/reviews/best-wi-fi-router/">The Best Wi-Fi Router (for Most People)</a>,” and at one level, that’s exactly what it does, but it also tells you how that pick compares to others. They mention niche products like the AirPort Express and Google OnHub. They might also suggest an almost-as-good, cheaper alternative, or a slightly-better, more expensive option. In addition to recognizing that no product is going to be “the best” for every situation, the overall message is, “trust us, we did our homework.”</p><p>Examples:</p><ul><li><a href="https://jasoncollins.org/2017/06/29/a-critical-behavioural-economics-and-behavioural-science-reading-list/">A Critical Behavioural Economics and Behavioural Science Reading List</a> is positioned as building on more popular books like <em>Thinking Fast and Slow</em>, <em>Predictably Irrational</em>, and <em>Nudge</em>. It doesn’t do much more contextualizing than that but at least it provides a bit of a yardstick</li><li><a href="https://www.theatlantic.com/entertainment/archive/2017/04/the-why-of-cooking-samin-nosrat/523923/">The Best Books for Learning How to Cook</a> is more of an article than a list but the links make it easy to scan for titles to turn into a list. This kind of approach is a bit more work (to write and read) but you come away with a better sense of how someone might navigate the landscape of options thanks to insights like, “A book like López-Alt’s is highly valuable to have around once one has confidence in the kitchen, but Nosrat’s seems much more vital for the purposes of getting to that point.”</li></ul><p>As for my own “Essential UX Reading List,” it’s a work in progress. I’ve shared some recommendations privately with people who’ve asked, but that’s it — and there’s a lot I haven’t read yet. Maybe working on a more comprehensive list is a good excuse to look into the rest of everybody else’s recommendations…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3b8dfb889af0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What to Ask Before Building Anything]]></title>
            <link>https://medium.com/res-im/what-to-ask-before-building-anything-39f882d82135?source=rss-8b56c3ea03a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/39f882d82135</guid>
            <category><![CDATA[lean-ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Brian Frank]]></dc:creator>
            <pubDate>Wed, 24 May 2017 18:27:50 GMT</pubDate>
            <atom:updated>2017-05-24T18:27:50.267Z</atom:updated>
            <content:encoded><![CDATA[<h4>Using a Research Mindset to Save Time and Reduce Risk</h4><p><em>This post introduces the thinking behind our </em><a href="https://www.eventbrite.ca/e/workshop-making-user-centred-decisions-tickets-34242663729"><em>1-day UX workshop</em></a><em> on user research and strategy. (An earlier version </em><a href="https://res.im/blog/five-questions-to-ask-before-building-anything/"><em>appeared at res.im</em></a><em> on May 26, 2016.)</em></p><p>The greatest risk in any project isn’t going over budget, delivering late, or changing the scope. The greatest risk in any project is building something people won’t use.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C0-brriPraWzgi24F6Txcg.jpeg" /><figcaption>Car designed by Homer Simpson. 3D model by <a href="https://www.youtube.com/channel/UCyLigAEeH0IN1eYtppfiH9A">Mauricio Sanjurjo</a>.</figcaption></figure><p>This isn’t just a high-magnitude risk, it’s also highly probable. Failure to deliver value to users happens more often than many people realize. When someone does take a more rigorous look at value being delivered they usually find that “<a href="http://mcfunley.com/testing-to-cull-the-living-flower">nearly everything fails</a>.”</p><p>In one <a href="http://www.exp-platform.com/Documents/2015%20Online%20Controlled%20Experiments_EncyclopediaOfMLDM.pdf">internal review</a>, Microsoft engineers found that only about ⅓ of feature ideas had statistically significant positive results when tested with users. Another ⅓ of the ideas had neutral results, while ⅓ of the assumed-to-be-good ideas actually produced <em>negative</em> results.</p><p>Even where Lean and Agile methods are used, it could take months before the product or feature is exposed to users. In the meantime, time and money are spent on assumptions that could easily be refuted or refined with a bit of research or prototype testing.</p><p>Say you’re thinking of adding a new feature to your product or service. You might feel confident based on its popularity in other apps—e.g. chat, “<a href="http://adage.com/article/digital/facebook-adds-stories-main-app-copying-snap/308455/">stories</a>” or photo filters/lenses—but what works for one audience and context might not work for yours.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/823/1*LGhxIf8ekyh0ExYJVzgwnw.jpeg" /><figcaption>Fictional Snapchat-style app that adds mustache filters to videos, from S.3.E1. of Silicon Valley.</figcaption></figure><p>Identifying and testing assumptions doesn’t need to turn into analysis paralysis or months of costly studies. When done well, approaching ideas with a bit of research-style discipline saves more time than it costs.</p><p>Before doing anything, ask a few key questions to get a sense of how risky your assumptions are. This is how we figure out how much research and validation is worthwhile.</p><ol><li><em>Who will use this?</em></li><li><em>When will they use it (or what will cause them to want or need it)?</em></li><li><em>What value or benefit will they get as a result of using this?</em></li><li><em>Is this really the most efficient and effective way to deliver that value?</em></li></ol><p>There’s a fifth question, which might be the most important. It often requires asking a few different ways before getting a good answer.</p><ul><li><em>How do we know these answers?</em></li><li><em>How are we testing our assumptions?</em></li><li><em>What results will tell us we’re right or wrong?</em></li></ul><p>Spending a few hours reframing assumptions as testable hypotheses might mitigate months of uncertainty and disagreement. A few days of guerrilla research might achieve the same clarity and alignment as weeks worth of deliberation. Or a one-week <a href="http://www.gv.com/sprint/">design sprint</a> might lead to a strategic pivot that would otherwise require months of development time.</p><p>Avoiding tough questions only delays inevitable answers. Skipping research doesn’t actually reduce research costs, it turns the whole project into a research cost. When approached openly, early questions and answers lead to more successful products sooner.</p><p><em>Sign up for our </em><a href="https://www.eventbrite.ca/e/workshop-making-user-centred-decisions-tickets-34242663729"><em>1-day UX workshop</em></a><em> to learn more about how to apply these principles to user research and strategy.</em></p><p><em>(An earlier version </em><a href="https://res.im/blog/five-questions-to-ask-before-building-anything/"><em>appeared at res.im</em></a><em> on May 26, 2016.)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=39f882d82135" width="1" height="1" alt=""><hr><p><a href="https://medium.com/res-im/what-to-ask-before-building-anything-39f882d82135">What to Ask Before Building Anything</a> was originally published in <a href="https://medium.com/res-im">Res.im</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 run an automated sports pool in a spreadsheet]]></title>
            <link>https://medium.com/@brian_frank/how-to-run-an-automated-sports-pool-in-a-spreadsheet-43730cb3a375?source=rss-8b56c3ea03a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/43730cb3a375</guid>
            <category><![CDATA[spreadsheets]]></category>
            <category><![CDATA[google-spreadsheets]]></category>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[golf]]></category>
            <category><![CDATA[excel]]></category>
            <dc:creator><![CDATA[Brian Frank]]></dc:creator>
            <pubDate>Sun, 09 Apr 2017 20:37:11 GMT</pubDate>
            <atom:updated>2018-04-06T00:08:28.652Z</atom:updated>
            <content:encoded><![CDATA[<p>Spreadsheets let you do a lot with very little technical ability. This example happens to be a fairly simple Masters pool, but most of these tips/tricks can be used for other sports — NHL &amp; NBA playoffs start soon! — or for doing your own own data analysis, running your own league standings, etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/784/1*sifyfPaej4ofsDpBJXEdLg.png" /><figcaption>The winning picks.</figcaption></figure><h3>The Basics</h3><h4>Setting the Rules &amp; Making Picks</h4><p>There are some different ways you could run the selection and scoring process (search for “golf pool” or “Masters pool”) but a golf pool doesn’t really need to be complicated: pick a bunch of players and whoever’s players get best scores wins.</p><p>The format we settled on for this pool was to each draft 7 players, from which we’d only count the top 4 scores. There were only two of us, and neither of us is a PGA expert, so we had some fun and mixed in a lot of sentimental, half-serious picks. (We also did this very last-minute—Thursday night, actually—so we had the benefit of picking some people who were already playing well.)</p><p>We listed our picks in a very basic Google spreadsheet. I manually entered each of the players’ scores, and used <a href="https://support.google.com/docs/answer/3093669?hl=en">SUM formulas</a> to add them up. Easy enough so far…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*syVK4yad-Mjiw4Ru9lslEA.png" /><figcaption>Our picks as of Thursday night. Don’t judge!</figcaption></figure><h3>Adding More Functionality</h3><h4>Importing Live Scores</h4><p>As simple as the initial spreadsheet was, I didn’t feel like manually updating scores all weekend. Luckily Google Sheets has a bunch of <a href="https://support.google.com/docs/topic/3105411?hl=en&amp;ref_topic=3046366">IMPORT functions</a> that make it fairly easy to pull data in from other sources. Once the live data is in the spreadsheet you can do all kinds of creative stuff.</p><p>The <a href="http://www.espn.com/golf/leaderboard">IMPORTHTML function</a> is what I used here. It might require a little trial-and-error to find a good source, but once you find one it’s an easy way to pull data from another website. In this case the <strong>URL</strong> I used was <a href="http://www.espn.com/golf/leaderboard">ESPN.com’s Masters leaderboard</a>. You also need to know whether you want to pull data from a <strong>table or list</strong> on the page. In this case it’s a table. Lastly, you need a numeric <strong>reference</strong> to the table or list you want to pull from (don’t overthink this one; it’s just a number, which you can guess).</p><p>Just type the IMPORTHTML formula with those three pieces of information — <strong>“</strong><a href="http://www.espn.com/golf/leaderboard"><strong>http://www.espn.com/golf/leaderboard</strong></a><strong>”, “table”, 1</strong>—into a single cell and a whole table or list should <em>magically</em> appear.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y306Tfk-_B28rYkc1M3wZg.png" /><figcaption>This is what showed up after entering =IMPORTHTML(“http://www.espn.com/golf/leaderboard&quot;,&quot;table&quot;,1) into cell B1.</figcaption></figure><h4>Looking Up Individual Player Scores</h4><p>The main thing I wanted to do was use the live data to update the scores for each of our picks. The most common way to do this is the <a href="https://support.google.com/docs/answer/3093318?hl=en">VLOOKUP function</a>. VLOOKUP is one of those things that involves a little more thinking but comes in handy once you get the hang of it. (More advanced users running lookups in large tables can combine INDEX and MATCH for more flexibility and faster processing.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UesX8c8y6XqxHpXcTaz1sg.png" /><figcaption>We imported the data using =VLOOKUP(B3,Data!$D$2:$E$189,2,FALSE) but it’s not quite right yet.</figcaption></figure><p><em>If you’re a spreadsheet novice I encourage you to take full advantage of the tooltips and help available in Google Sheets, and don’t forget to copy or </em><a href="https://support.google.com/docs/answer/75509?co=GENIE.Platform%3DDesktop&amp;hl=en"><em>autofill</em></a><em> it to the other cells.</em></p><p>The <a href="https://support.google.com/docs/answer/3093318?hl=en">VLOOKUP formula</a> above is basically saying:</p><ul><li>I want to find the value of cell <strong>B3 (</strong>“Lee WestwoodL. Westwood”) from within a range of cells…</li><li>The range I want to look in includes the “Player” and “To Par” columns of the data we imported from ESPN.com (in this example that is <strong>Data!D2:E189</strong>)—to which we add dollar signs (<strong>Data!$D$2:$E$189</strong>) to keep it from changing when we copy or <a href="https://support.google.com/docs/answer/75509?co=GENIE.Platform%3DDesktop&amp;hl=en">autofill</a> it to the other cells.</li><li>I want to return the value from <strong>2nd</strong> column of that range (which in the example above is Lee Westwood’s “To Par” score of -1). <strong>FALSE</strong> means that we’re looking for an exact match (don’t overthink this).</li></ul><p>You probably noticed that I had to change the players’ names to the weird format that appears in ESPN’s live data import. That’s easy to change, along with some other things we need to clean up to make the data more accurate and usable.</p><h4>Cleaning Up the Data</h4><p>The biggest issue so far is that the scores aren’t adding up. This is because a lot of ESPN’s data is actually text, so math formulas skip right over it. Specifically, we want to get rid of the “+” sign for over-par scores and change even scores from “E” to the number zero.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_KKD6W8CqJ7y602eZcuYGw.png" /><figcaption>There are a few things happening here: removing text from scores and changing them to numeric values, and adding a column for more readable player names.</figcaption></figure><p>It’s often a good idea to clean up data before doing anything else, but in this case I just focused on the data I was using. The <a href="https://support.google.com/docs/answer/3094215?hl=en">SUBSTITUTE function</a> got rid of the “+” signs and changed “E” to a zero. It took a little trial-and-error to figure out how to make multiple substitutions using a nested formula. Even then, the numbers were still coming out as text, so I added a <a href="https://support.google.com/docs/answer/3094220?hl=en&amp;ref_topic=3105625">VALUE function</a> to convert the scores to numeric values.</p><p>For the player names I simply added new columns and typed them the way I wanted them to appear in our final results, which we’ll get to shortly…</p><h4>Sorting and Adding the Top Scores</h4><p>Remember we only wanted to count the top 4 scores from each team. If we were updating the spreadsheet manually we could select the data we want to sort, click Filter in the Data menu and sort each table. But we’d have to keep doing that every time the scores changed. Fortunately, setting it up to sort automatically is just as easy using (you guessed it) the <a href="https://support.google.com/docs/answer/3093150?hl=en">SORT function</a>.</p><p>The <a href="https://support.google.com/docs/answer/3093150?hl=en">SORT function</a> creates a copy of the designated range/table (e.g. <strong>B3:E9</strong> for Team A) and sorts it by whichever column you indicate (e.g. <strong>4</strong> for the numeric scores in column E). <strong>TRUE</strong> tells it to sort in ascending order, from lowest to highest (which in golf is best to worst).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4qSoyvZrfbJTcuKfgKxXoQ.png" /></figure><p>Once the scores are in order you can use a couple of good ol’ SUM formulas to add up the top 4 scores for each team. I did this by adding new columns and merging cells (select the cells you want to merge and select Merge from the Format menu).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w-hGn3C_BV9J9p5uIJfSTQ.png" /></figure><h3>Making it User-Friendly</h3><p>What we have so far technically does everything we need but it doesn’t look great. It only takes a few minutes of extra work to create a scoreboard that’s actually somewhat ok to look at—and adds a layer of protection over the underlying calculations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H0nkIdMigpZixOme-h4PtA.png" /><figcaption>There are no calculations happening in this tab, just references to cells in other tabs.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yrU57EXwYou10rVZUS5pjA.png" /><figcaption>Don’t forget to protect your sheets!</figcaption></figure><p>It’s generally good practice to separate your scoreboard or “Results” view from the underlying operations and data tables. It gives you a lot more flexibility to play with the the visual design while keeping the Calculations and Data logical and usable in a utilitarian way.</p><p>Notice we’re only showing the normal player names in our Results tab, and the “+” signs and “E”s have reappeared. That’s because the calculations have already been made in another tab, so we’re free to show scores in text format here.</p><p><em>For spreadsheet beginners, if you want cell C6 in the Results tab to display whatever is in cell C13 in the Calculations tab, click on C6 and type “</em><strong><em>=Calculations!13</em></strong><em>”</em><strong><em> </em></strong><em>— or just type “=” and click on cell C13 in Calculations.</em></p><p>A lot more could be said about formatting and visual design, but this example should be pretty straightforward. Visual spreadsheet design might be a topic for a future post.</p><p>Finally, don’t forget to lock the important sheets! Right-click on the tab you want to lock down and choose Protect Sheet. Google Sheets let’s you prevent or warn certain people (including yourself) from making any changes—just like it lets you decide who gets access to view it.</p><p>Check out the live spreadsheet here: <a href="https://docs.google.com/spreadsheets/d/1Mg_3MYJUdFFWTGDp-loZyU2HszQlKyyaXdQmR_D-o-k/edit?usp=sharing">https://docs.google.com/spreadsheets/d/1Mg_3MYJUdFFWTGDp-loZyU2HszQlKyyaXdQmR_D-o-k/edit?usp=sharing</a></p><p>[Update: I’ve had some requests for access to the spreadsheet. If you have a Google account you should (I think…) be able to make your own copy in the File menu. If not, request access and I’m happy to make a copy for you.]</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=43730cb3a375" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why are some doors so difficult?]]></title>
            <link>https://medium.com/res-im/why-are-some-doors-so-difficult-f7aec8b6343d?source=rss-8b56c3ea03a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/f7aec8b6343d</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[usability]]></category>
            <dc:creator><![CDATA[Brian Frank]]></dc:creator>
            <pubDate>Tue, 14 Mar 2017 17:23:57 GMT</pubDate>
            <atom:updated>2017-03-14T17:23:57.854Z</atom:updated>
            <content:encoded><![CDATA[<p>There’s a place near <a href="https://res.im/">ResIM’s office</a> with notoriously terrible doors. Don’t get me wrong, I like this place. Some weeks I go there 2–3 times, maybe more. But the doors. Every time I go I feel a sense of mutual hostility.</p><p>After roughly 15 years of frustration I finally learned that these doors are what some people call “Norman doors,” named after Don Norman, one of the pioneers of user experience design. The first chapter of his classic <em>Design of Everyday Things </em>talks a lot about doors<em>. </em>There’s also a good <a href="http://99percentinvisible.org/article/norman-doors-dont-know-whether-push-pull-blame-design/">video by Vox &amp; 99% Invisible</a> (below). Both are worth your time if you design things or just feel strongly about how things are designed.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FyY96hTb8WgI%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DyY96hTb8WgI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FyY96hTb8WgI%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/e974b06d32234c9584678bfb48176956/href">https://medium.com/media/e974b06d32234c9584678bfb48176956/href</a></iframe><p>Being a UX researcher and usability tester, I wanted to confirm whether other people had the same problem I have with these doors. So I decided to do an informal usability study last September during <a href="http://www.am980.ca/2016/09/07/country-music-week-lineup/">Country Music Week</a>. The event was a chance to observe “new users” from out of town who hadn’t already learned to use the doors “correctly” (though after speaking to more people it seems a lot of us still struggle).</p><p>This was far from a rigorous study, but it only took 15 minutes to convince me that <em>I‘m not the problem</em>, the doors are. It’s a small sample, but the need for more data declines when you watch people struggle with something as basic as <em>pushing a door open</em>. Results were basically 50/50 for push vs. pull—not a great success rate.</p><p>Here are the results from that 15 minutes, watching from a nearby bench:</p><ul><li><em>5 people “correctly” pushed the door open.</em></li><li><em>5 people “incorrectly” pulled the door handle, then figured out to push.</em></li><li><em>2 people grabbed the handle and paused — possibly to read the sign or to pull weakly before pushing the door open.</em></li><li><em>3 people pressed the button that automatically opens the door.</em></li></ul><p>(I should add that vastly more people went through the doors as part of a group or just behind someone else. Counting them would’ve just skewed the results. I didn’t count any of the several dozen people who were near the door while it was already open or in the process of closing.)</p><h3>Key Lessons</h3><h4><strong>Respect standards and norms.</strong></h4><p>Most swinging doors on commercial buildings in this city swing <em>out</em>. We’re trained that when we approach a building from the outside, the door opens toward us—unless it revolves, slides, or otherwise opens automatically.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CaczrTzoi-7cFiJAL-h0zg.jpeg" /><figcaption>Justine demonstrating “correct” use of the doors in question.</figcaption></figure><p>And then there’s the handle. The outer handle on these doors is designed to be pulled. It’s got a good grip. Good leverage. Handles designed for pushing are usually obvious about it—with a flat plate or a horizontal bar. Basically everything about these doors, except the little sign, tells us to pull.</p><blockquote>“Innovate when you know you have a better idea (and everyone you show it to says “Wow!”), but take advantage of conventions when you don’t.” <a href="https://books.google.ca/books?id=g1QBFJxB_eEC">Steve Krug</a></blockquote><h4>Don’t expect people to read.</h4><p>The “Push” sign barely helps. (I vaguely remember the sign being added after the building opened, and thinking, “I guess I’m not the only one who can’t use these doors.”)</p><p>The sign is largely useful for “error recovery.” It keeps us from giving up or breaking things. By the time we notice the sign we’ve started to struggle and feel frustration. It can even make people feel even more annoyed and ashamed. It might as well say, “Push, you dummy.”</p><h4>Don’t make people think.</h4><p>To complicate things even more, immediately beside these doors is a nearly-identical set that opens the other way. If you veer right, the doors <em>open in</em>. If you veer a few feet to the left, the doors <em>open</em> <em>out</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zfQZjfy4aAGaGMbHf9BIeA.jpeg" /><figcaption>The doors on the left swing *out* to open. The doors on the right swing in. Can you tell the difference?</figcaption></figure><p>Maybe this was done to make things easier for people. I can imagine a thought process that goes something like this:</p><ul><li>“Most people walk on the right.”</li><li>“Pushing the door open is slightly easier than pulling.”</li><li><em>“Ergo</em>, let’s make it easier both ways by making it so the doors on the right are always pushed, whether entering or exiting.”</li></ul><p>But logic often backfires when we’re talking about human behaviour. Opening a door isn’t hard for most people. What <em>is</em> hard is learning a new <a href="https://www.nngroup.com/articles/mental-models/">mental model</a> (“bearing right through a ‘main entrance’ = push door”) and trying to remember where and when it applies (interior doors in the same building don’t use the same mental model).</p><blockquote>“There’s great <strong>inertia in users’ mental models</strong>: stuff that people know well tends to stick, even when it’s not helpful. This alone is surely an argument for being conservative and not coming up with new interaction styles.” <a href="https://www.nngroup.com/articles/mental-models/">Jakob Nielsen</a></blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F0rWxKbp4Fjc%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D0rWxKbp4Fjc&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F0rWxKbp4Fjc%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/3b861c693cffce038c2ffa67431d94aa/href">https://medium.com/media/3b861c693cffce038c2ffa67431d94aa/href</a></iframe><h4>Different isn’t always better.</h4><p>The worst that happens when you stick to conventions is you keep the thing boring. It’s probably ok to bore people for a few seconds while they walk through the door — or log onto your website, or open up your app, etc. The real value is what they see and do and feel and remember when they get in.</p><p>Things like doors and login processes are basic or must-have features that don’t increase overall satisfaction on their own. But they can <em>decrease</em> satisfaction when they’re missing or done poorly. This is where the <a href="https://en.wikipedia.org/wiki/Kano_model">Kano model</a> comes in handy.</p><blockquote>“Capabilities that users expect will frustrate those users when they don’t work. However, when they work well, they don’t delight those users. A basic expectation, at best, can reach a neutral satisfaction point where it, in essence, becomes invisible…” <a href="https://articles.uie.com/kano_model/">Jared Spool</a></blockquote><p>Trying to improve basic features can be a dangerous game, usually with high risks and low rewards. <a href="http://www.vox.com/2016/9/7/12822516/apple-iphone-7-headphone">Apple has played this game</a> fairly well over the years, but usually for higher rewards, guided by long-term vision and strategy, not just immediate incremental improvements.</p><p>Even if the risks seem relatively low, people do have a <a href="https://en.wikipedia.org/wiki/Negativity_bias">tendency to notice and remember negative features</a> more than positive ones. People remember feeling stupid. They remember being laughed at—or <em>feeling</em> laughed at.</p><p>That’s why you’re more likely to see a Facebook post calling your doors “the worst” (actual <a href="https://www.facebook.com/groups/2247652968/permalink/10154968072997969/">Facebook comment</a> about these doors) than you are to see posts saying “those doors work great!” Especially when they don’t.</p><p>Change can be great, but count the stakes and make sure it’s actually an improvement. Make it worth the risk.</p><p><em>Originally published at </em><a href="https://res.im/blog/why-are-some-doors-so-difficult/"><em>https://res.im/blog/why-are-some-doors-so-difficult/</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f7aec8b6343d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/res-im/why-are-some-doors-so-difficult-f7aec8b6343d">Why are some doors so difficult?</a> was originally published in <a href="https://medium.com/res-im">Res.im</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Embracing Agility in User Research]]></title>
            <link>https://medium.com/@brian_frank/embracing-agility-in-user-research-2a0a534f5f29?source=rss-8b56c3ea03a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/2a0a534f5f29</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[lean-ux]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Brian Frank]]></dc:creator>
            <pubDate>Thu, 02 Feb 2017 12:17:00 GMT</pubDate>
            <atom:updated>2017-02-02T12:17:00.519Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*73MsWvwjDK_uK46f.jpg" /><figcaption>Photo credit: <a href="https://unsplash.com/@dyaa">Dyaa Eldin Moustafa</a></figcaption></figure><p>Plans have a purpose, but I’m always afraid of being too constrained by them in research, strategy and design work.</p><p>In academic research, plans help to ensure scientific rigor and secure funding, etc. In UX research, plans help manage expectations, coordinate teams, assure the bosses that we’re making good use of time and money, and generally maintain a degree of professional diligence.</p><p>But just as ‘no battle plan survives contact with the enemy,’ research plans have a way of changing once participants get involved. It’s not at all uncommon for interviews to go in an unexpected direction in the first few minutes, even when participants have been carefully screened. The uncertainty is both a bit scary and exhilarating — especially when it plays out in front of clients.</p><blockquote><em>“Everybody has a plan until they get punched in the mouth.”</em></blockquote><blockquote><em>- Mike Tyson</em></blockquote><p>During one session with a couple of continuing education students, it became clear that the participants were much more dependent on the print catalogue than we expected. Most of their comments revolved around making a 200-page PDF easier to find — despite also expressing frustration about it. I thought we’d be getting feedback about the website but they hardly used the site at all. Most of the prepared questions didn’t make any sense in that situation.</p><p>The participants’ fixation on finding the PDF and leaving the site as fast as possible felt like a classic case of “customers don’t know what they want.” The planned discussion was mostly a dead end, but we’d been given an unexpected gift: now we had an opportunity to observe people using the site somewhat naturally but in ways we hadn’t seen, based on real needs, to get deeper insight into the experience. So I turned my laptop around for the participants to use in some unplanned usability scenarios. The unexpected change gave us a better opportunity to see what people really saw and thought while on the site.</p><p>Uncertainty and change don’t just affect individual sessions; the whole process often needs to be open and adaptable to unexpected discoveries.</p><p>If you’re too rigid you often end up missing the best opportunities to learn. Over-planning reinforces biases and assumptions in a closed feedback loop that makes transformational insights harder to get. Rigid plans are often fine for evaluative research, like when you want to know how satisfied people are or whether they know where to click on an interface, but rigidity constricts the exploration and <a href="http://johnnyholland.org/2012/03/finding-empathy-through-generative-research/">generation of new ideas</a>. Transformative discovery is <a href="http://www.laser-community.com/en/eric-mazur-harvard-physics-professor-about-his-career-his-life-and-the-discovery-of-black-silicon/">the art of serendipity</a> — putting yourself in a position to be surprised by new questions.</p><blockquote><em>“Chance favours the prepared mind.”</em></blockquote><blockquote><em>- Louis Pasteur</em></blockquote><p>Planning helps anticipate some of the more predictable surprises. Planning forces you to visualize how an interview or group session or set of survey results might go, then tailor your questions, methods and materials accordingly.</p><p>A while back I started drafting a short questionnaire to recruit and screen participants for a personal project on how people listen to music. In the process of drafting the questionnaire I thought, “wait, what if someone says they ‘listen in the car’ but mainly to news and talk shows?” Podcasts and talk radio often do the same <a href="https://res.im/blog/jobs-to-be-done-in-the-student-journey/">job</a> that music does. “Would the question make sense? Would the answers be credible? And why should this study be limited to music?” It became clear that I needed to do some more open-ended exploration — talking to people — to better understand the scope of the challenge I wanted to address.</p><blockquote>“Plans are worthless, but planning is everything.”</blockquote><blockquote>- Dwight D. Eisenhower</blockquote><p>The plan itself is no guarantee that every contingency is covered, but the <em>planning process</em> helps anticipate problems and opportunities to learn. Planning makes us think carefully about the purpose and goals of our research. What decisions will we inform? What are the underlying questions we need to answer? Those answers then become the pole star we can use to navigate through uncharted terrain.</p><p>The most effective UX research plans, I think, adopt Agile and Lean principles.</p><p>Agile principles dictate that work should be iterative, collaborative, and open to change — with value delivered early and often. You might have a research roadmap (or loose plan) looking months ahead, but the plan is subject to change based on early findings and decisions. Instead of waiting to package everything in one big, hairy deliverable, insights are shared and applied as work progresses.</p><p>Lean principles go a step further and make the process more continuous. In a lean system, generally, work is pulled in small batches in response to demand. Lean research is a response to decisions that need to be made, questions that need to be answered, and assumptions that need to be tested — all of which continue to emerge during and after implementation.</p><p>The most adaptable research is a process of continuous discovery — not as an excuse for bad planning but as a natural response to evolving questions and needs.</p><p><em>Original post: </em><a href="https://res.im/blog/embracing-agility-in-user-research"><em>https://res.im/blog/embracing-agility-in-user-research</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2a0a534f5f29" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Some Lessons Learned Doing UX Research]]></title>
            <link>https://medium.com/res-im/some-lessons-learned-doing-ux-research-b9396cbc03a6?source=rss-8b56c3ea03a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/b9396cbc03a6</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[lean-ux]]></category>
            <dc:creator><![CDATA[Brian Frank]]></dc:creator>
            <pubDate>Thu, 29 Sep 2016 15:45:56 GMT</pubDate>
            <atom:updated>2016-09-29T15:49:35.514Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j0M8N7ODP9cBvtlZS1hsww.jpeg" /><figcaption>#itsametaphor: the UX researcher reflecting on the efficacy of focus groups, and other important questions.</figcaption></figure><h3>Methods and tools aren’t the answer.</h3><p>When I moved into UX research at <a href="https://res.im/">ResIM</a> a little over a year ago it was <a href="https://medium.com/research-things/focus-groups-are-worthless-7d30891e58f1#.1qdeegp1j">cool to hate focus groups</a> and surveys. It’s probably true that they’re used too often, or too often used instead of more appropriate methods. But I’ve found focus group-type sessions to be great for generating a lot of input quickly, and surveys are great for validating initial findings across a larger sample.</p><p>People love to talk about methods and tools in any profession, but sometimes we seem to treat methods and tools like they’re the answers and solutions themselves. We have a very broad and rich <a href="https://www.nngroup.com/articles/which-ux-research-methods/">landscape of UX research methods</a> to work with, each suited to different goals and questions. And each method can be applied a multitude of ways…</p><p>Methods and tools matter, but not as much as actually doing the work, asking the right questions, listening, being critical and exercising good judgement. Sometimes you can do all that just by leaving the building and talking to the first five people you see.</p><h3>Small insights make big differences.</h3><p>For me, this has probably been the most interesting and unexpected lesson learned doing UX research.</p><p>All of our clients have had good ideas and insights before we’re involved. Some have had <em>great</em> ideas, especially when they have their own internal researchers and designers. If we compared snapshots of the lists of ideas before and after our research process they’d often look nearly identical.</p><p>But “ideas” are often where people get stuck. Research grounds ideas in reality to give them traction to move forward. What really changes through the research process isn’t the ideas themselves so much as the degree of clarity, understanding and alignment around them.</p><p>When done well, UX research turns hypothetical visions into stories that move everyone in the same direction, with more urgency and a clearer sense of why and how.</p><h3>Collaboration is everything.</h3><p>If the purpose of research is discovery and learning, then it’s important that we learn together. I’m not adding much value if I spend weeks learning what someone could’ve told me at the kickoff meeting. Research should build on, refine, and share what people already know.</p><p>Likewise, my value is pretty limited if I dump 50–100 pages of findings and recommendations into a report and move on. It’s too much to digest, especially if the questions the report answers aren’t top of mind the day or week it’s delivered. People go back to what they’re doing and forget which proverbial shelf the research is sitting on.</p><p>The delivery of a report is just one milestone in a process of interpreting results and executing on recommendations — many of which are best formed later as more granular questions and constraints emerge. There’s just no way to anticipate every execution-related question that could emerge. Research needs to be responsive to questions.</p><p>Of course I already “knew” this by reading books like <a href="https://abookapart.com/products/just-enough-research"><em>Just Enough Research</em></a> and <a href="http://shop.oreilly.com/product/0636920021827.do?cmp=af-na-books-videos-product_cj_auwidget502_0636920021827_4298217"><em>Lean UX</em></a>, but my appreciation for collaboration has deepened through experience.</p><h3>Knowledge is both useful and dangerous.</h3><p>This is a lesson I learned long ago that continues to be reinforced every day. Knowledge makes us <a href="https://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect">feel smarter than we are</a>.</p><p>On every project I talk to someone who says “everything needs to be within 2–3 clicks.” It’s a widely debunked <a href="http://uxmyths.com/post/654026581/myth-all-pages-should-be-accessible-in-3-clicks">UX myth</a> that people still cling to. It’s not the only one. If we’re not careful, rules are handy ways to unconsciously reinforce biases—whether it’s a stakeholder who wants visibility for their department on the home page or even another designer citing principles that align more with their past experience than the current situation.</p><p>Look at how assumptions about things like <a href="https://www.nngroup.com/articles/flat-design/">flat design</a> or <a href="http://www.lukew.com/ff/entry.asp?1945">hamburger menus</a> have fluctuated. Rules and principles intended to address a specific place and time easily get repeated as misconceptions in other contexts. If <a href="http://www.theatlantic.com/science/archive/2016/03/psychologys-replication-crisis-cant-be-wished-away/472272/">psychology can’t take its past findings for granted</a>, then why would UX research be any different?</p><blockquote>“The days when a researcher could observe a few folks using a website on a desktop computer, crank out an observation like “users hate carousels” and call it a day are so far behind us it’s difficult to make them out in the rearview mirror.” <em>— Matt Gallivan (Airbnb), </em><a href="https://medium.com/airbnb-design/embracing-uncertainty-in-ux-research-973a962b2e8e#.xr4o2f5o3"><em>Embracing Uncertainty in UX Research</em></a></blockquote><p>A better approach is to treat knowledge as living system that continuously evolves or grows from one context to the next—from print to digital, or from web to mobile, wearables, AR/VR, AI and chatbots, etc. Even as I’m writing this I’m trying to be mindful that these lessons learned might have a limited shelf life. The best I can hope is that they lead to better lessons.</p><p>It’s often better to be wrong than vague, so general principles are a good baseline to start from—as long as you stay critical and observant. This is how science works: it’s not a solid edifice built one brick (or principle) at a time, it’s a process of continuous discovery and reformation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b9396cbc03a6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/res-im/some-lessons-learned-doing-ux-research-b9396cbc03a6">Some Lessons Learned Doing UX Research</a> was originally published in <a href="https://medium.com/res-im">Res.im</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design as the New Management]]></title>
            <link>https://medium.com/newco/design-as-the-new-management-2d0b817a2f88?source=rss-8b56c3ea03a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d0b817a2f88</guid>
            <category><![CDATA[gsd-mgmt]]></category>
            <category><![CDATA[design-management]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Brian Frank]]></dc:creator>
            <pubDate>Wed, 20 Jan 2016 03:39:40 GMT</pubDate>
            <atom:updated>2016-11-14T18:18:48.889Z</atom:updated>
            <content:encoded><![CDATA[<h4>Get Shift Done: Management</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xf43Yol9tsOwdo26m8WZgQ.png" /><figcaption>Source: <a href="https://commons.wikimedia.org/wiki/File%3ADesign_thinking.png">https://commons.wikimedia.org/wiki/File%3ADesign_thinking.png</a></figcaption></figure><p>Business gurus love buzzwords. One of the buzzwords that’s got a lot of attention in the past few years is “design,” or more specifically, “design thinking.”</p><p>Even as an admirer of the principles behind design thinking, I expected the hype to peak in the late ’00s. But instead of fading it’s actually finding a wider audience and pushing deeper into more industries and organizations. <a href="https://hbr.org/2015/09/design-thinking-comes-of-age">Harvard Business Review put it on the cover</a> last September.</p><p>So what’s going on here?</p><p>First, I think what we’re seeing is not just some fad but a response to structural shifts in industries and organizations. At risk of oversimplifying it, the rise of design corresponds with the rise of software — especially software as a service — and the gradual and continuous evolution of processes and organizations around it.</p><p>Unlike hardware products, or even packaged software, software provided as a service over a network can be updated and delivered to users on the fly. Over the past decade, companies that figured out how to manage that <a href="https://en.wikipedia.org/wiki/Continuous_delivery">continuous delivery</a> process have had a competitive advantage over those that made customers wait six or eighteen months for improvements. By the time the latter company releases a new version of their product, the former company has already found new things to improve based on customer feedback.</p><p>Meanwhile, companies that weren’t initially in the software business have realized the value and importance of augmenting their products with software and other services. <a href="http://www.bloomberg.com/gadfly/articles/2016-01-15/ge-dumps-past-for-future-more-exciting-than-refrigerators">GE’s launch of a digital division</a> is a prominent recent example. As a result, software (or “technology”) is no longer “an industry” in quite the same way that it was at the dawn of the PC era, so much as it’s a whole layer spreading out across virtually every other industry. Transportation, retail, hospitality, education, and entertainment have all been transformed (or “disrupted”) by software companies, and the incumbents have been forced to follow.</p><p>And all of that stuff needs to be designed — and I don’t just mean making surfaces pretty and usable but making sure these increasingly complex systems work together to serve increasingly nuanced needs. And those systems aren’t just the products and services themselves but the processes, teams, organizations, and business models around them. These need to be designed and redesigned as well.</p><p>We could quibble over what’s really “design” vs. what’s “architecture” vs. what’s “management” or whatever else, but any form of <em>deliberate change</em> is within the dictionary definition of design. Let’s not overthink it. More time and energy is lost arguing about the definition of design than will ever be lost misapplying it.</p><p>So now I look at it this way. What if management as a practice isn’t just temporarily borrowing from design, but some large part of it is actually becoming [or being displaced by] design? I don’t mean that everybody is a designer, but that a growing number of people in organizations are spending more of their time doing design activities. Calling a few of them designers is less weird or inaccurate than what most are already called, whether it’s something generic like manager, analyst or strategist, or something more contrived.</p><p>Management as a practice only really emerged after industrialized organizations demanded large numbers of managers simply to operate. Now we have <a href="http://secondmachineage.com/">another sort of industrial revolution</a> that’s automating a lot of the work managers have traditionally done, like monitoring, reporting, coordinating, and even low-level decision-making. Needs are changing.</p><p>In the future we’ll spend a smaller proportion of time managing these systems and more time designing them. We might not call the people who do this “designers,” but in an important way design is slowly becoming the new management.</p><p><em>Get stories like this one delivered to your in-box weekly: </em><a href="https://newco.co/newsletters/gsd/?utm_source=Medium%20links&amp;utm_medium=NewCo%20Shift%20on%20Medium&amp;utm_campaign=GSD%20email%20newsletter%20sign%20up%20campaign"><em>Subscribe to the GSD newsletter</em></a><em>.</em></p><p><strong>The GSD Management channel is brought to you by Work Market, the leading labor automation platform. Work Market empowers businesses and skilled professionals to unlock new levels of productivity, engagement and growth across the entire lifecycle of work. Learn more at </strong><a href="https://goo.gl/bD2GPz"><strong>www.workmarket.com</strong></a><strong>.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d0b817a2f88" width="1" height="1" alt=""><hr><p><a href="https://medium.com/newco/design-as-the-new-management-2d0b817a2f88">Design as the New Management</a> was originally published in <a href="https://medium.com/newco">NewCo Shift</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why (Oh Why) Must Awesome Products Die?]]></title>
            <link>https://medium.com/@brian_frank/why-oh-why-must-awesome-products-die-a2178e812609?source=rss-8b56c3ea03a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/a2178e812609</guid>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[rdio]]></category>
            <category><![CDATA[music]]></category>
            <dc:creator><![CDATA[Brian Frank]]></dc:creator>
            <pubDate>Thu, 19 Nov 2015 00:26:19 GMT</pubDate>
            <atom:updated>2015-11-19T00:26:19.573Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/986/1*veSfTDHC9F3fKGN-Giby9Q.jpeg" /></figure><h4>Before I Get Into Rdio…</h4><p>Last week Sony announced the <a href="http://arstechnica.com/gadgets/2015/11/sony-finally-kills-betamax-13-years-since-it-last-made-a-player/">last-ever Betamax cassette</a> will roll off the production line in March 2016 (which means someone, somewhere, has actually been using them all these years).</p><p>Legend has it that Betamax was better than VHS. The reality is a bit more complicated. Original Betamax tapes were only an hour long, i.e. not long enough to record or distribute a standard movie, which in hindsight is obviously a major shortcoming. VHS tapes had twice the capacity, partly due to their makers’ willingness to make them larger and more unwieldy. Most <a href="http://www.theguardian.com/technology/2003/jan/25/comment.comment">consumers didn’t care about unwieldy</a>. Sony eventually extended their tapes’ capacity, but so did VHS makers. With VHS you could tape <em>two</em> movies, then eventually three or four. In 1993 you could tape two Blue Jays World Series games on one tape (or if you’re my mom, a whole week of your favourite soap).</p><p>The history of technology is full of stories like this. My elementary school had an underutilized Apple in 1985 and that was pretty much the last time I touched one until the mid ’00s. I believed that Apple computers were better in some ways that appealed to me but the uncertainty and cost of switching was always just high enough to keep most of us stuck with Windows.</p><p>A product’s own technical capabilities and quality aren’t all that matter when history decides whether it will prevail. It also takes timing, business savvy, good branding and strategy, and understanding what most people want (or guessing, unwisely). Sometimes it requires the ability and will to sell at a loss or throw money at it until attrition catches up with competitors.</p><h4>We Know, But It Still Sucks</h4><p>It hurts to be on the losing side, even if you’re only a consumer. Great products inspire love. They become part of people’s daily lives, part of our thought patterns and identities. Sometimes this is especially true for underdog products. Maybe it’s a kind of “<a href="https://en.wikipedia.org/wiki/Florence_Nightingale_effect">Florence Nightingale effect</a>.” We become more personally invested when we sense even a tiny bit of ourselves shaping a product’s survival or success. And for products we really love, our life stories can literally intertwine; we lose a little piece of ourselves when the product does.</p><p>It might seem like hyperbole but I thought about and felt some of these things this week when Rdio announced they’re shutting down.</p><p>Rdio might be my favourite service of any kind, and has been since I signed up five years ago. I looked forward to checking the new releases every Tuesday. Most of my favourite albums of the past five years I discovered through Rdio (a lot of them serendipitously via friends’ activity). Before I went on trips I always made sure my Rdio playlists and downloads were set up for the right soundtrack. <a href="http://www.theatlantic.com/technology/archive/2015/11/a-eulogy-for-rdio/416310/">Robinson Meyer’s eulogy for Rdio</a> made me realize how good the community was on there.</p><blockquote>People left comments on albums, and, lo and behold, the writing was <em>good and interesting. </em>Strangers constructed playlists that pulled from artists and albums you’d never heard of, but without the performative high/low-ness that afflicts so much online music talk.</blockquote><p>It might seem weird to say, but I have a lot of warm memories associated with Rdio, in the same way that I look back nostalgically at discovering music in record stores, at concerts, and in friends’ physical collections.</p><p>Sadly, Rdio wasn’t for everybody. Outside of a small group of like-minded people, nobody I knew stuck with it (despite my best efforts). Meanwhile the same people who didn’t stick with Rdio raved about services like Songza and Spotify that emphasized the kinds of passively consumed, curated experiences that feel overmediated and just unpleasant too me.</p><p>Spotify seems to have improved in the direction I want it to but I definitely feel like I’m not the target Spotify user. There’s a bit of clumsy industry cruft to navigate around before finding the experience I’m looking for. (Picking a category before I browse feels unnatural. And after telling Spotify I’m a 37-year-old male and listening to one metal album, its top radio station recommendations for me are Drake, Justin Bieber, and One Direction?) Same thing more or less goes for Apple Music.</p><p>According to a <a href="http://www.theverge.com/2015/11/17/9750890/rdio-shutdown-pandora">story on it at The Verge</a>, Rdio’s downfall can be partly attributed to too much focus on product details that too few people would appreciate, and not enough effort to market to the mass fixation on “free.”</p><p>Rdio was elegant and pure compared to everything else. I’d go as far as to <a href="https://twitter.com/brian_frank/status/23868423492">say it was damn near perfect</a> for a brief moment (notwithstanding the limited selection, especially in the early days). This is why Rdio inspired love and influence that went well past its modest mass market penetration, as <a href="http://www.theverge.com/2015/11/17/9750890/rdio-shutdown-pandora">Casey Newton pointed out</a> in that Verge piece:</p><blockquote>Among its subscribers were a small legion of user interface and user experience designers — one reason you see little touches of Rdio everywhere you look.</blockquote><p>The things that product designers care about aren’t the same things that most consumers care about. Just as people embraced unwieldy VHS cassettes and endless Windows popups over more elegant alternatives, people embraced familiar music industry cruft for the sake of getting a good enough, free-for-most service. By the time Rdio started to respond, the outcome was already well in motion.</p><h4>So What’s To Be Done?</h4><p>But I don’t think the takeaway should be to cynically steer every product toward the lowest common denominator of consumer preferences. After all, Apple eventually thrived, as did Pixar, another company Steve Jobs nurtured through a formative phase in which high product standards put the business at risk. (We could add NeXT to the list and argue that without it, present-day Apple and the Internet would both be very different. That must count for something.)</p><p>There’s a whole list of “failed” products in recent years that we could say were “<em>successful at being awesome</em>,” which inspired some of what came next. Google Wave and FriendFeed are among the others that got me excited but didn’t win the popularity contest (I worry about Twitter ending up on this list soon).</p><p>Sometimes it can start to feel unrealistic to want to create something we’re proud of that’s also economically viable, like at some point there’s going to be a fork in the road and we can only pick one way: creative pride vs. commercial profit. A middle way is there, it’s just tougher to find; it requires comfort moving in either direction and the ability to switch at the right time.</p><p>And I keep in mind that companies that pick the cynical, profit-maximizing route at the expense of quality and love often fail too. They still need to do everything else right or risk coming away without even so much as a decent story to tell. And creating great stories is what it’s all about, isn’t it?</p><p>If instead we err the other direction and create something we’re proud of and it touches people’s lives and changes the future even just a little, well that’s definitely not nothing.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a2178e812609" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>