<?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 Tara Mason on Medium]]></title>
        <description><![CDATA[Stories by Tara Mason on Medium]]></description>
        <link>https://medium.com/@tara.mason?source=rss-1397e0691bb5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*YD__S8GXejugP6Wa</url>
            <title>Stories by Tara Mason on Medium</title>
            <link>https://medium.com/@tara.mason?source=rss-1397e0691bb5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 01:14:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tara.mason/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[A Simple(ish) Game Plan for User Testing]]></title>
            <link>https://medium.com/@tara.mason/a-simple-ish-game-plan-for-user-testing-54f269ab8d59?source=rss-1397e0691bb5------2</link>
            <guid isPermaLink="false">https://medium.com/p/54f269ab8d59</guid>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Tara Mason]]></dc:creator>
            <pubDate>Wed, 12 Dec 2018 00:13:57 GMT</pubDate>
            <atom:updated>2019-06-12T17:28:47.742Z</atom:updated>
            <content:encoded><![CDATA[<h3>A Simple(ish) Game Plan for User Testing (Part II)</h3><blockquote>“Any intelligent fool can make things bigger and more complex, but it takes a touch of genius, and a lot of courage to move in the opposite direction.” — Einstein</blockquote><p>Hi! This is step two Making a Case for User Experience. We will briefly outline how to go about actually implementing user testing! If you would like something more in-depth, and would like some super helpful checklists, I HIGHLY recommend purchasing <a href="http://sensible.com/">Steven Krugs</a> book “Rocket Surgery Made Easy”. Really. He makes it easy.</p><p>Decide what type of testing to do –</p><p><strong>Guerilla</strong> <strong>“extreme minimal approach” </strong>— Approach people in a coffee shop, park, etc. and offer to buy them coffee/muffin in exchange for performing a few tasks on your website. Observe in person only.</p><p><strong>Steven Krug</strong> <strong>“minimal/medium diy approach”</strong> — Set up your own simple “studio”, ask people to perform tasks, ask them how it was. Pay them for their time. Record audio and computer screen.</p><p><strong>Fancy “high-end approach” </strong>— Set up the ultimate “bug free” studio with dedicated computer system, control of system requirements, video of users as well as screen capture, specific user profiles for test participants, very specific tasks asked of participants.</p><p><em>(More detailed information about carrying out each approach is below.)</em></p><p>More in depth explanation of how to go about specific types of user testing:</p><h3>PART I:</h3><p><strong>Guerilla</strong> “extreme minimal approach” -</p><p>This approach is recommended when time is very scarce, your are in the beginning stages of product development, or you are okay with validating (or invalidating) <em>critical assumptions</em> about your product. While user testing is always recommended as early in product development as possible, this type of testing is often used when a product is in its infancy. It requires minimal planning, and the product can be as simple as sketches on a notecard (especially helpful for low-level interactions &amp; site mapping).</p><p>The main things to keep in mind for this type of testing are:</p><ul><li>What should we test?</li><li>Where?</li><li>With whom?</li><li>How?</li></ul><p><strong>What should we test?</strong> Since this is a minimal approach where we are asking users for around 10 minutes of their time, we should keep the tasks simple and low-level. Tasks such as <em>“find _x_ product and add it to your cart”</em>, or <em>“find where your account profile is located” </em>would be appropriate tasks, to maintain the allotted time that you requested of the participant.</p><p><strong>Where? </strong>Guerrilla tests are often performed in coffee shops or other public spaces (keep in mind wifi needs if you need internet to perform the test.)</p><p><strong>With Whom?</strong> This simple approach is best for testing on products that do not require the user to have specific prior knowledge or technical skills. Ideally, you would be able to target pretty much any friendly-looking person in a coffee shop.</p><p><strong>How?</strong> It is important to start with very open-ended questions that don’t lead. (SEE STEVEN KRUG APPROACH BELOW). Try to keep it casual and be aware that we will be bringing our own biases with us, especially if we worked on the product (try to keep those biases to yourself!). Make sure the user knows you are not testing <em>them</em>, rather you are testing the product, and they can’t do anything “wrong”. One of the most important elements is to capture the actual screen and the user while testing. Capturing both on video is ideal, but just capturing the screen and audio of the user would be minimal.</p><p><a href="https://medium.springboard.com/a-guide-to-the-art-of-guerrilla-ux-testing-69a1411d34fb">https://medium.springboard.com/a-guide-to-the-art-of-guerrilla-ux-testing-69a1411d34fb</a></p><p><a href="http://www.uxbooth.com/articles/the-art-of-guerrilla-usability-testing/">http://www.uxbooth.com/articles/the-art-of-guerrilla-usability-testing/</a></p><p>Simple example: <a href="https://medium.com/bridge-collection/a-guerilla-usability-test-on-dropbox-photos-e6a1e37028b4">https://medium.com/bridge-collection/a-guerilla-usability-test-on-dropbox-photos-e6a1e37028b4</a></p><h3>PART II:</h3><p><strong>Steven Krug</strong> <strong>“minimal/medium diy approach” –</strong></p><p><strong>Rule #1: Test Early and Often —</strong></p><p>One reason why people don’t do usability testing is because they think it will take too much time and is very complicated. Steve advises you to start user testing as early in product development as possible, and continue to commit to monthly testing (as long as the changes from the first testing has been implemented). Once you have everything in place, it is not very difficult or time consuming to conduct one set of three tests per month.</p><p><strong>#2: Recruit Loosely and grade on a Curve —</strong></p><p>Unless your app or website requires specific knowledge to use (it probably doesn’t. Your audience is probably more diverse than you think), it is important not to obsess over your users background and technical expertise. Ideally, your product should be easy to use regardless of background. Finding users with specific background can be expensive and very time consuming.</p><p>There are only a few rules:</p><ul><li>Don’t use people from your office (unless it is only an internal tool)</li><li>Don’t have the marketing department choose the users (yes, the book actually says this!)</li></ul><p>How to recruit:</p><ul><li>Put out an invitation. This can be on your website (as a popup), on announcement boards, on Social Media, etc. Consider friends, family, and neighbors.</li><li>Screen possible users. Make sure they are available. Make sure they meet the qualifications you’ve decided to have them meet. Tell them what to expect, explain compensation. Decide if they seem good (do they seem like they will be good at thinking out loud? Are they articulate?</li><li>Three users per round is enough. (The first three users are very likely to encounter many of the most significant problems. There are diminishing returns on having a lot of users. The more users you watch, the fewer new problems you see. It is much more important to do more rounds of testing than to do a lot of testing at once.)</li><li>Follow up. Right after you confirm the testing date and time, send them a confirmation of what, when, where.</li><li>Have a backup user or two. Things happen.</li><li>Don’t reuse your users (they already know too much), unless you have a completely different product to test them on.</li></ul><p><strong>#3: Decide what to include in the tests —</strong></p><ul><li>Get a team together to brainstorm. Have them privately and individually write down what they think the 5 most important things your website must do. There will be many overlaps, this is good.</li><li>Decide which ones to focus on in next round of testing.</li></ul><p>Take the final tasks and turn them into scenarios.</p><ul><li>“So, you’re a ____ and you’d like to apply to the ____ program…”</li><li>Make it clean, unambiguous and easy to understand.</li><li>Their only rules are: you can’t use the “Search” bar, and you can’t use another website. This is not a race, but a test as to the usability of <em>this</em> site…</li></ul><p><strong>#4: Have a Checklist for the actual testing session —</strong></p><p>Yes, you will forget to turn on the screen capture at some point. There is a list in the book...</p><p><strong>#5: How to run a test —</strong></p><p>Have a testing area set up (https://medium.com/@AukeMolendijk/create-your-own-professional-usability-lab-16987ac0bb2).</p><p>Yes you kind of have to be a therapist. The most important thing is to leave your biases at home, and don’t lead the User. These d<em>etails should be studied in the book</em>.</p><p><strong>#6: Get Everyone to Watch —</strong></p><p>No, not in the same room as the user, you will have screenshare set up in another room.</p><p>Why do we want people from the office to watch? In the words of the infamous Steve Krug, because “people often go in skeptical, and come out… well, changed.” Enthusiastic, you might even say!</p><p><em>(Somehow, we all think that everyone is like us, and if we can navigate the site perfectly well, so can everyone else. People will realize everyone is not just like you, and it is much more pronounced when they attend the live session.)</em></p><p>How do you get them to show up?</p><ul><li>Provide snacks</li><li>Make it as easy as possible to just “drop in”</li><li>Advertise</li><li>Make the rule that you can’t participate in deciding what we will fix next unless attend (obvs this is optional, but a great idea to get people to attend)</li></ul><p><strong>#7: Debrief —</strong></p><p>As a group, come up with a list of the most serious problems, then narrow those down to the problems that can/will be fixed before the next testing session.</p><p><strong>#8: Fix the problems!!</strong></p><h3>PART III:</h3><p><strong>Fancy</strong> <strong>“high-end” dedicated studio approach —</strong></p><p>This approach would take some serious research, time, money, and space. If you’re thinking about doing this, you should probably just hire a professional.</p><p>Thank you!</p><p>(Please clap for me if you enjoyed this!)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=54f269ab8d59" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Making a Case for User Testing In Software Development]]></title>
            <link>https://medium.com/@tara.mason/making-a-case-for-user-testing-in-software-development-db37e7571457?source=rss-1397e0691bb5------2</link>
            <guid isPermaLink="false">https://medium.com/p/db37e7571457</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-testing]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Tara Mason]]></dc:creator>
            <pubDate>Sun, 28 Oct 2018 22:09:21 GMT</pubDate>
            <atom:updated>2019-06-12T17:28:16.587Z</atom:updated>
            <content:encoded><![CDATA[<h3>Making a Case for the User in Software Development — Part I</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/450/1*tDOIKCCYV9F-SpOZc-bUYA.jpeg" /><figcaption>Hmmmm…..</figcaption></figure><p>“We will flee what is unpleasant and distasteful, while the promise of delight will draw us like moths to a flame.” <a href="#_ftn1">[1]</a></p><p>People expect pleasant, if not delightful user experiences these days. When they are unable to accomplish their goals, frustrated by the process, or worse yet — they completely forget about you because your product is boring, competition is only a few clicks away. On the other hand, by incorporating user input into your design process, you’ll have the tools to create remarkable experiences. Investing time and resources into good UX can help you create brand advocates — loyal fans who not only use your product, but sing your praises to their friends, family and colleagues. <a href="#_ftn2">[2]</a></p><p>“Usability” is a very old concept… From clay pots with narrow necks that make them easier to hold, to our modern-day “electronic devices”, most items that we use have undergone rigorous “user studies” and redesigns. Even da Vinci was known to implement extensive analysis prior to implementing commissions as simple as a kitchen design. If he hadn’t tested some of his products and forced his users to try them, he probably wouldn’t be the infamous household name he is today. Even though some of his designs were less than effective <a href="#_ftn3">[3]</a>, it is safe to say that he would not have been as successful as he was if he had not consulted his users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*IZChyhmu1oeowS4beJ-R_g.jpeg" /><figcaption>NBD…</figcaption></figure><h3>What user?</h3><p>As the internet has grown, so has it evolved. At the beginning of the advent of the internet, there used to be this sense that all you had to do was “just make it work”. User experience was hardly taken into consideration. I have images in my head of holy software engineers scoffing at people who couldn’t figure out how to use their “genius” product. However, the tech has evolved to a point that “just making it work” is not enough anymore. People not only have other options, they have <em>many</em> other options. As a product owner, you are faced with the task of making your product look credible and create an experience that is enjoyable and streamlined. How? What does the user know anyway?</p><p>It is my hope that this article will help you make a case for user testing if you find yourself in a situation where you know it should be implemented, but can’t find the support to carry it out. Part 2 will outline the steps involved in actually conducting user testing. Lets go!</p><h3>The Million Dollar Button</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/630/1*adfcNrdf234s1Nj7OKIA2Q.jpeg" /><figcaption>No, not that button…</figcaption></figure><p>The creators of a large website (rumored to be Amazon) assumed that people coming to their website would be more than happy to simply enter an email address and password and create an account prior to placing an order. What could be hard about that? After all, it should make future purchases much faster and more streamlined.</p><p>Through some testing, the company figured out that many users were just ditching the site at the checkout page. People simply did not want to be forced to register. This might seem obvious today, but it was not then. Others couldn’t remember what their email or password was for the account, so they set up new accounts every other time they ordered, and often had up to 10 different accounts.</p><p>This was obviously a problem.</p><p>The site was redesigned so that the user could continue to checkout without creating an account. They were then informed that they could register, but were not forced to. This one small change increased in the company’s revenue by 45% in the first month, which turned into $300 million in the first year. If it wasn’t for user testing, it might have taken <em>years</em> to figure this out OR we might all still be forced to create an account for, like, everything… (shudder…) <a href="#_ftn4">[4]</a></p><p>However, every situation is different, and the same problem could require a completely different solution.</p><p>For example, a number of years ago, Twitter redesigned their signup page and implemented what is now called “gradual engagement”, a process that gave users a chance to experience the service and why they should care about it instead of just making them sign up. This change, <strong><em>which actually made the signup process many steps longer,</em></strong> increased signup completions by 29%.<a href="#_ftn5">[5]</a></p><p>But how can you do this yourself? Isn’t user testing expensive and time consuming?</p><p>Not anymore! Not too long ago, modern user testing <em>was</em> complicated and expensive. It required a lab with two-way mirrors, multiple observers, a expensive multi-camera setup, a facilitator, finding and arranging the right testing participants (with the right demographics) to come to you, finding and hiring experienced professional usability practitioners to make recommendations for changes, and a lot of money. This dated scenario is what a lot of people think of when you say “user testing”.</p><p>It can be much easier today.</p><p>Setting up your own user testing “lab” can be as simple as watching someone maneuver your app from your phone in a coffee shop, or as simple as recording via a screen-sharing app while asking a user to perform a set of tasks. You can also install software that will help you see where people are clicking the most (very helpful in finding out if people are clicking on things that aren’t even links!) The observations made during these sessions are always eye opening, to say the least. Issues are often easy to research and improve quickly, then validated in another round of testing.</p><p><strong>A quick note:</strong> While there is a place and a time for finding the perfect users with “just right” demographics, this article is written to inspire people to get up and running with user testing quickly and easily. It has been said that 85% of usability issues can be found by testing with 5 users...</p><h3><strong>If You’re Not Already Convinced</strong></h3><p>You might think, after month or even years of developing your app or website, you have addressed every flaw in your design. I mean, who could know it better than the people working on it?? <em>When you’re too close to your work, it’s impossible to look at it without bias.</em></p><p>Until you receive actual feedback, and talk to a user while using your product, you may realize you had no idea how users are perceiving and using your design.</p><p>Errors often uncovered during User Testing are often:</p><p>-Incorrect assumptions about user behavior.</p><p>-Features that nobody cares about.</p><p>-Confusing navigation.</p><p>-Buttons that don’t work correctly.</p><p>-Text or images that appear to be a link but are not.</p><h3>Time === $$</h3><p>In a report by <em>Human Factors International</em>, an estimated <a href="http://www.usability.gov/what-and-why/benefits-of-ucd.html">50% of engineering time</a> is spent doing rework that could have been avoided. The cost of fixing an error after development is estimated to be 100 times more expensive than if it had been fixed before. <a href="#_ftn6">[6]</a></p><p>Time is expensive. If you don’t test early and often, you could be spending your resources developing features that are broken or difficult to use, when you could have found those issues early on and addressed them to create and iterate on features that not only function well, but that your users love and will recommend to their friends.</p><blockquote><em>Investing in UX research has proven to give companies a large advantage. According to the Harvard Business Review</em>, <strong>“10 years of research shows that companies who put human-centered design methods at the core of their growth strategy see a </strong><a href="https://hbr.org/2014/04/design-can-drive-exceptional-returns-for-shareholders/"><strong>228% higher ROI than the S&amp;P 500</strong></a><strong>… The bottom line is that companies who focus on design strategically grow faster and have higher margins than their competitors… And thanks to the exemplar companies… consumers now recognize, expect, and will pay for good design.”</strong> <a href="#_ftn7">[7]</a></blockquote><p>Paying your developers is expensive. As a developer myself, I would rather make it the right way, the first(ish) time. If you could save hundreds of engineering hours and thousands of dollars by doing UX research before you start building, while making products that users enjoy, why wouldn’t you?</p><p>If you enjoyed this, please do me a favor and give me a clap. Or two. You’re the best.</p><p>Not sure where to start? Check out: <a href="https://medium.com/@tara.mason/a-simple-ish-game-plan-for-user-testing-54f269ab8d59">Part II, outlining how to get going with User Testing,</a> but your best bet is to buy these books by the unofficial usability guru, Steve Krug. The best part is that they are short and fairly enjoyable to read. (Go figure! :-)</p><p>PART II : <a href="https://medium.com/@tara.mason/a-simple-ish-game-plan-for-user-testing-54f269ab8d59">A Simple(ish) Game Plan for User Testing</a></p><p>If you want some more resources, I highly recommend the following:</p><p><a href="https://www.youtube.com/watch?time_continue=454&amp;v=-O5kNPlUV7w">This video</a> to get an idea on why humans like beautiful things.</p><p><a href="https://www.amazon.com/gp/product/B00HJUBRPG/ref=dbs_a_def_rwt_hsch_vapi_taft_p1_i0">Don’t Make Me Think</a>, by Steve Krug (An overview on good User Experience)</p><p><a href="https://www.amazon.com/gp/product/B002UXRGNO/ref=dbs_a_def_rwt_hsch_vapi_taft_p1_i1">Rocket Surgery Made Easy</a>, by Steve Krug (A step by step approach to User Testing)</p><p><a href="https://www.amazon.com/Things-Designer-People-Voices-Matter/dp/0321767535">This book</a> that outlines some amazing things about people and their behaviors that can help guide your design.</p><p><a href="https://www.amazon.com/Design-Everyday-Things-Revised-Expanded/dp/0465050654/ref=pd_lpo_sbs_14_img_0?_encoding=UTF8&amp;psc=1&amp;refRID=80JDND5151KVWNWD4MEF">This amazing classic</a> that basically started the whole thing.</p><p><a href="#_ftnref1">[1]</a> New York Times best-selling author <a href="https://twitter.com/robertgreene">Robert Greene</a></p><p><a href="#_ftnref2">[2]</a> <a href="https://www.usertesting.com/blog/2015/04/14/4-reasons-why-you-should-user-test-your-product/">https://www.usertesting.com/blog/2015/04/14/4-reasons-why-you-should-user-test-your-product/</a></p><p><a href="#_ftnref3">[3]</a> In this project, he is attributed to creating the first conveyer belt and fire sprinkler system, both of which miserably failed initial testing.</p><p><a href="#_ftnref4">[4]</a> <a href="http://blog.uxeria.com/en/a-short-history-of-user-experience/">http://blog.uxeria.com/en/a-short-history-of-user-experience/</a></p><p><a href="#_ftnref5">[5]</a> <a href="https://www.lukew.com/ff/entry.asp?1128">https://www.lukew.com/ff/entry.asp?1128</a></p><p><a href="#_ftnref6">[6]</a> Susan Weinschenk, Ph.D. Chief of U Strategy, Human Factors International, I highly recommend watching a short YouTube video about user testing and research: <a href="https://www.youtube.com/watch?v=O94kYyzqvTc#t=11">https://www.youtube.com/watch?v=O94kYyzqvTc#t=11</a></p><p><a href="#_ftnref7">[7]</a> Harvard Business Review: <a href="https://hbr.org/2014/04/design-can-drive-exceptional-returns-for-shareholders">https://hbr.org/2014/04/design-can-drive-exceptional-returns-for-shareholders</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=db37e7571457" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>