<?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 John Rimmer on Medium]]></title>
        <description><![CDATA[Stories by John Rimmer on Medium]]></description>
        <link>https://medium.com/@john.rimmer?source=rss-7292f71f2f9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*M_X7UJiOY9SQtvPrJaOV9Q.jpeg</url>
            <title>Stories by John Rimmer on Medium</title>
            <link>https://medium.com/@john.rimmer?source=rss-7292f71f2f9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 08:41:07 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@john.rimmer/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[Why the state of the industry is set up for UX and CX.]]></title>
            <link>https://uxplanet.org/why-the-state-of-the-industry-is-set-up-for-ux-and-cx-b7cfba8047ca?source=rss-7292f71f2f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/b7cfba8047ca</guid>
            <category><![CDATA[digital]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[digital-marketing]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[customer-experience]]></category>
            <dc:creator><![CDATA[John Rimmer]]></dc:creator>
            <pubDate>Tue, 18 Sep 2018 19:43:34 GMT</pubDate>
            <atom:updated>2018-09-18T22:24:55.182Z</atom:updated>
            <content:encoded><![CDATA[<p>A succinct argument for the state of the digital industry and it’s future reliance on User and Customer Experience.</p><p><strong>Firstly, why are there often question marks around UX and CX?</strong></p><p>This is my take on the lack of understanding around the roles and need for UX and CX within companies.</p><p>UX takes ownership of the roles and responsbilities that developers should be doing anyway. Research, Design Iteration and Validation are sensible steps which should be undertaken by anyone wanting to create a useful, usable products regardless of the medium they’re designing them in.</p><p>However, UX has advanced these roles and made them a specialism by becoming more expert in each and adding real value as a result, similar to Project Managers. You wouldn&#39;t expect to start a design sprint without a Project Manager, but then you wouldn’t exactly <strong><em>not</em></strong> start to speak with your team or order your backlog just because a PM didn’t exist. Similary to UX Designers, Projects Managers have specialised the art of organising and informing development teams.</p><p>Customer Experience on the other hand is an expansion of User Experience in many respects. It considers the customer journey across multiple touchpoints. A great example for me would be the Post Office. An in-store, online and mobile presence, which needs to communicate to its users across all touchpoints, but with a binding narrative that provides a quality experience at each stage.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/566/1*SYlTyyPQLrGhRHSNPgOI1g.png" /><figcaption>User Experience, a ‘sub-set’ of the overarching Customer Experience.</figcaption></figure><p><strong>So,why is the state of the industry set-up for UX and CX?</strong></p><p>We live in an age now of disruptors coming to market and smaller scale start-ups wanting to elbow their way in past the competition and for many, they haven’t looked back. However here’s the issue…</p><h4>A lot of these business models are solely online in terms of their relationship with their customer:</h4><ul><li><em>Finance</em>: Think challenger banks like Starling and Monzo who are “mobile-only” with an online focussed customer interaction.</li><li><em>Retail</em>: Think online clothing retailers such as ASOS and BooHoo, who have made a hugely successful impact on the market since arriving with no ‘bricks and mortar’ (physical) outlets.</li></ul><p>Although some start-ups might provide telephone assistance should things go wrong for the customer, online chat mediums still seems to be the strong preference due to cost, whilst the point of sale is still crucially <strong>online</strong>.</p><p>The one thing these business have in common is their reliance on an exceptional User Experience if they’re to persuade potential customers away from the competition. As online-only, B2C companies, they need to provide an aesthetically pleasing UI, teamed with an exceptional User Experience. For the likes of HSBC, RBS or Bank of America, they have thousands of in-store customer service teams, established call-centres and years of customer service experience in their favour when looking to retain their customers or gain new ones. For any new start-up coming to market, they’ll likely have less financial power and experience and so their USP needs to be an outstanding quality of experience, in order to gain that trust from a user when building a lasting relationship.</p><p><strong>How does UX and CX benefit from this?</strong></p><p>UX Design is the essence of how a potential customer should feel about your online service. This may be working with others to create visually pleasing, accessible and intuitive experiences, using language which is fit for context and easy to understand. There is no doubt that if such business want to create these sorts of environments to help drive their business objectives by attracting and retaining customers, then UX must be pivotal in their thinking.</p><p>However, providing more attractive and engaging experiences which customers will love is something that all companies should strive for, regardless of which space they operate in. For larger scale, non-online only companies (e.g. Amazon, HSBC) who are able to provide users with multiple touch points through their journey (in-store UI, desktop website and mobile app all working together), then these such business require a clear Customer Experience (CX) Strategy. Ensuring a consistent and reliable experience at each step, which will help to meet their customers’ needs. Amazon are excellent in delivering a clear CX approach from the moment you click online to door step delivery; and as CEO Jeff Bezos (aka newly crowned world’s richest man) is famously quoted as saying:</p><blockquote>“Obsess over the customer, not the competition.” — Jeff Bezos</blockquote><p><strong>The importance of Trust</strong></p><p>One of the key factors that make up a user’s overall perception of product or service is <strong>trust</strong>. With regards to e-commerce trust is an important indicator for intention to transact as shown in Pavlou’s Trust model (2003). Not only is it shown as having a <em>significant</em> direct effect on the user’s intention to transact, but also as having a <em>highly significant</em> effect on other factors which effect intention to transact.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yNAgzyBWkGcNFkWLuw_jug.png" /><figcaption>Pavlou’s Trust model, 2003</figcaption></figure><p>Being able to convey trust and building up good relationships with users is what helps to turn them in to customers and encourage repeat trade. Through considered UX and CX, we can design for trust by providing a quality aesthetic, an intuitive and easy-to-use interface and easily understood language to name a few. Although many web-users of today have grown up ‘digitally-native’, this doesn’t take away from the need to be perceived as a trustworthy business who can be relied upon.</p><p>Sometimes it’s not enough to simply have a great product or service, but instead the way that is translated to your potential customers through something they’re able to connect with and emotionally invest, which may late transpire to something they will physically invest in. To use an analogy, when buying a sports car costing a lot of money you want it to meet an array of needs in terms of its looks, the performance, its usability, but importantly <strong>how it makes you feel:</strong> <em>proud, trusting, confident, luxurious</em> etc. It’s imperative that any new service or product coming to market really understands this need to connect with their audience emotively.</p><p>Therefore, as long as there’s a need to attract users through digital mediums, there’ll inevitably be a need for UX and CX.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fb3e808%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Fb3e808%2F&amp;image=http%3A%2F%2Fapi.screenshotlayer.com%2Fapi%2Fcapture%3Faccess_key%3Dfe59908dad3baab69ffab249a2224b03%26viewport%3D1024x612%26width%3D1000%26url%3Dhttps%253A%252F%252Fupscri.be%252Fb3e808%253Fscreenshot&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href">https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b7cfba8047ca" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/why-the-state-of-the-industry-is-set-up-for-ux-and-cx-b7cfba8047ca">Why the state of the industry is set up for UX and CX.</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Alternative User Research Methods — Part 2]]></title>
            <link>https://uxplanet.org/alternative-user-research-methods-part-2-4f5b73fb39df?source=rss-7292f71f2f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/4f5b73fb39df</guid>
            <category><![CDATA[user-testing]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[user-experience-design]]></category>
            <dc:creator><![CDATA[John Rimmer]]></dc:creator>
            <pubDate>Mon, 10 Sep 2018 08:41:27 GMT</pubDate>
            <atom:updated>2018-09-10T08:48:33.238Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*hN9ihNL5buNlnYtTh21Svw.png" /></figure><p>After the undoubted worldwide success of last month’s blog on Alternative Research methods (*<em>jsut kidding. See — </em><a href="https://bit.ly/2Q8aAUK">https://bit.ly/2Q8aAUK</a>), this blog is a follow-on from that topic to delve into more alternative methods to get the proverbial juices flowing for conducting research when working in Agile.</p><h3>1) Color by Emotion</h3><p>This one is similar to Part 1’s ‘Colour by Importance’. However, the clue is in the title in terms of the difference. This technique can be used with either visual layouts of the product you’re testing or specific pieces of text which you would like to understand a bit more about in terms of what effect it is having on the user.</p><p>You can do this many, many different ways, however here we’ll discuss two. The first way is to give your participant a few different colored highlighters (3 will do). Attribute an emotion to each of the different colours, (confidence, frustration, trust etc — just try to be balanced in the variety of emotions you select) or alternatively you can select one emotion (such as trust) and attribute the colors to the 3 varying degrees of this emotion (strong to weak).</p><p>Ask the participant to go through the layout or text and highlight the parts which they believe makes them feel the differing emotions by using the attributing highlighter, some parts may have conflicting emotions, but don’t worry that’s fine. Once you’ve gone through this technique with a number of users you can start to build a literal picture of which areas are creating certain emotions by looking at the color combinations that are starting to build up (tracing paper is good for this). If you have time, try to follow-up the highlighting task with each of the participants by asking them ‘why?’ they chose to color the text/image in such a way to help uncover their reasoning.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*npUJjHVPjsHqBmUN" /><figcaption><em>Example of a highlighted page from </em><a href="https://www.nhs.uk/conditions/hay-fever/"><em>https://www.nhs.uk/conditions/hay-fever/</em></a></figcaption></figure><p>The second method is very similar, however, allows the user to select their own emotion/s they would like to apply to the different colors for what it is you’re testing. This method does not put any undue bias by potentially using emotions you would expect them to feel rather than what it is they might truly feel about the product. Again, follow-up by asking why it is they chose the color they did in order to gain reasoning behind your participant’s actions.</p><p><strong>Example User Comments:</strong></p><p><strong>Low Trust &gt;</strong></p><p>“Some of the language was ambiguous and therefore did give me feeling of trust in what was being said.”</p><p><strong>High Trust &gt;</strong></p><p>“The text was clear and concise and written in a way which I could easily understand which helped me feel more trusting towards the site.”</p><p><strong>When should it be used?</strong></p><ul><li>Use it to help validate the design</li><li>Use it to benchmark against competitors</li></ul><p><strong>What are the key outcomes?</strong></p><p>Qualitative user feedback in the form of paper artifacts which can be used to help create something visual to present back to teams such as a heatmap of their emotions as well as verbal feedback. User’s comments on the different aspects of what they have highlighted will help to support your artifacts and give context to why they have colored in such a way.</p><p><strong>How do I implement this?</strong></p><p>You will need to use printouts of your product or text in order to test with the user. You may also want to consider using tracing paper to lay over an original of the text/product and that way you may find it easier to begin to build up a picture. Be sure to note which section the user was discussing when collecting any comments as a part of your qualitative feedback, this will help for reference when you may later require looking back through the testing.</p><p><strong>What are the benefits vs traditional methods?</strong></p><ul><li>Able to understand users’ complex and often conflicting emotions about the same product page or piece of text. Often it is not always <strong>one</strong> solitary emotion and this method helps to unpack this.</li><li>Can be used for text or screenshots of the different product pages.</li></ul><h3>2) The Comparable Experience</h3><p>User Experience is about creating exactly what it says on the tin, an <em>Experience</em>. Sometimes when researching this can be a difficult notion to capture when it comes to testing users due to the multiple facets that can go into an overall experience as well as the difficulty it can be to eloquently articulate just what exactly our experiences felt like. It can, therefore, be better to tap into a User’s comparable experience in order to allow them to tell you about a similar event or interaction they’ve experienced.</p><p>This technique is similar to asking the well-used research question — “Tell me about a time when you…” or “Describe to me the last time you…”. However, this technique asks of the participant to describe a similar experience to one they have had after using the product, in order to attribute certain discernable characteristics from the experience which they found particularly comparable as well as why.</p><p>Ask the participant to use the product or site you are testing, preferably with a specific task to resolve that you may want to focus on. After completing the task as them to discuss their experience before highlighting a similar experience they would say it is like. This does not need to be a digital experience and can be good or bad. It is simply asking the user to think a little more abstractly about the product they have just encountered and to unearth some of the emotive feelings that they may want to see in the product. Again you can follow up with probing questions as to why it is they feel such a way or how they might want to feel in the given scenario.</p><p>This type of technique is used to get people to think about the product or experience at a level they can easily connect with and recreate themselves, which will help draw out rich information in terms of the wants and needs from the user for that product. It doesn’t need to necessarily be an experience per se, but maybe a photo which could help to represent an experience in order to get them to think about how the product made them feel.</p><p><em>Example from Survey Monkey</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_g6opeAGOadd-Dvh" /><figcaption><a href="https://www.surveymonkey.com/curiosity/give-your-surveys-a-visual-touch-with-image-answer-options"><em>https://www.surveymonkey.com/curiosity/give-your-surveys-a-visual-touch-with-image-answer-options</em></a></figcaption></figure><p><strong>When should it be used?</strong></p><ul><li>Use it to learn more about why your users are or are not engaging with the product either in initial user research or for validation purposes</li></ul><p><strong>What are the key outcomes?</strong></p><p>Understand at a deeper level the experience felt by your user and as well as one they might want to feel.</p><p><strong>How do I implement this?</strong></p><p>You may choose to have a deck of images at hand, similar to the image form survey monkey in order to inspire the users or simply allow the user to explain back to you from their personal preference.</p><p><strong>What are the benefits vs traditional methods?</strong></p><p>Simply asking “Tell me the last time” is a good way to understand the various stages of how a user may interact with a product, but may not get to the cause of the experience they currently feel or one they might want to experience. The benefit here is being able to tap into that comparable experience which is well established and use it to leverage the plus points or negatives which you can bring in or try to reduce from your product.</p><h3>3) Filter Method</h3><p>Often when completing user testing participants can feel compelled to finish tasks set by the researcher, whether through politeness, the fact they have been reimbursed for taking part or any other reason, when in reality they are free to leave without reason at any point during the test. Conversely, this method asks users to stop at the point in their journey when they feel they would no longer continue. Users may choose to follow through the journey all the way to the end, however, it’s important to understand where and importantly Why users are dropping off which you wouldn’t be able to get from tracking online statistics.</p><p>Choose a task you would like to hone in on and consider the various different stages of the journey that are necessary to complete the overall task. Get the user to run through the journey as they would normally, with consideration for the fact that they might choose alternate methods. Get the user to think aloud as they run through their tasks, analyzing their journey and ask them before they look to move off the page/or leave the site why it is they would want to make that decision. Should they choose to leave, make a note of where and why, whilst you may want to time the user-test for additional information on how long they spent and when the user dropped out. Essentially, this is analyzing when/where and how many users are deciding to ‘drop-off’ with the benefit of being able to as <em>Why</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CwWQvDEeqMTFBJCa" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Jiu41UqUQIwDUeoD" /><figcaption><em>An example screen for the task of buying milk from Tesco: </em><a href="https://www.tesco.com/groceries/en-GB/shop/fresh-food/milk-butter-and-eggs/milk"><em>https://www.tesco.com/groceries/en-GB/shop/fresh-food/milk-butter-and-eggs/milk</em></a></figcaption></figure><p><strong>When should it be used?</strong></p><ul><li>Use it to help validate the design</li><li>Use it to benchmark against a competitor where tasks are similar</li><li>Can be conducted remotely</li></ul><p><strong>What are the key outcomes?</strong></p><p>Understand the specific problem areas faced by users when trying to complete tasks with your product. Help to understand the dropout rate at the various stage of your product and reasoning from the user as to why this is happening.</p><p><strong>How do I implement this?</strong></p><p>Choose your medium which you would like to test on (Desktop, Laptop, mobile etc.) and have a task sheet for the user to complete. Mark at which stage they decided to stop (if they did) with their reasoning why, even if they completed the tasks all the way to the end.</p><p><strong>What are the benefits vs traditional methods?</strong></p><p>Typical online testing which may be able to capture the statistics for users using your site or product are great — should you have the means. For those that don’t, this is not only a cheap and easy alternative but one which is also able to gain from the user ‘Why?’ they chose to drop out when they did. Conducted with around 20 participants it will help to give a good steer on the problem areas and reasoning (Qualitative Data) although more participants would be wanted to gain any substantial quantitative data which might give a truer reflection of the bounce rate at different pages.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fb3e808%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Fb3e808%2F&amp;image=http%3A%2F%2Fapi.screenshotlayer.com%2Fapi%2Fcapture%3Faccess_key%3Dfe59908dad3baab69ffab249a2224b03%26viewport%3D1024x612%26width%3D1000%26url%3Dhttps%253A%252F%252Fupscri.be%252Fb3e808%253Fscreenshot&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href">https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4f5b73fb39df" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/alternative-user-research-methods-part-2-4f5b73fb39df">Alternative User Research Methods — Part 2</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Confidence is Key and 10 other useful tips for User-Testing]]></title>
            <link>https://uxplanet.org/why-confidence-is-key-and-10-other-useful-tips-for-user-testing-aa80ab459efa?source=rss-7292f71f2f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/aa80ab459efa</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-testing]]></category>
            <category><![CDATA[usability]]></category>
            <dc:creator><![CDATA[John Rimmer]]></dc:creator>
            <pubDate>Tue, 04 Sep 2018 15:52:04 GMT</pubDate>
            <atom:updated>2018-09-05T08:16:34.702Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*fZZKzrpRWuoPmtVOwFvjXQ.jpeg" /></figure><p>For anyone about to embark on User-Testing, firstly, good-luck, it’s daunting. There’s plenty of niches and learning that you really wouldn’t have expected for something that on the face of it seems like a very simple task, to get information, from people. So here are 10 pieces of advice i’ve put together from my experience which hopefully you can take away and use to avoid any undue pain.</p><ol><li><strong>Be confident yet humble</strong></li></ol><p>This isn’t contradictory. You can be confident in the work that you’re doing and humble enough to listen and value people’s views at the same time. I believe it’s very important to give off a confident persona even if you’re not exactly exploding with self-belief. What’s important is that they (the participants) believe you and have confidence in you and for that you need to be confident in yourself. So whatever the user-test, however sophisticated (or lack thereof) your workstation and equipment may look, just be honest with yourself about the aims of the session and make sure you put your best foot forward. If you’re not, this may set alarm bells ringing in the participant, set yourself off track and potentially have a knock on effect on the quality of the session, so if you can, deep breath and think positive. If you are confident, make sure this isn’t too overbearing on the participant either. Being a good-listener is an undervalued quality in many aspects of life, but hugely important to User Research. Make them feel comfortable, promote a chatty environment and let them waffle on, remembering bring the conversation back on track when needed. Structuring the conversation will help you to not take up too much time ‘off-topic’, but if they should stray, you can always pick out the key bits of what they’ve said in the analysis after.</p><p><strong>2. Don’t be leading and don’t assume</strong></p><p>‘Leading the witness’ as people like to say generally evokes the response you want to hear, not the one you need to hear if you’re going to improve your product. Have a few key phrases at hand to help push the participant along if they need it, but don’t ask a leading question as to guide their train of thought. For example “When was the last time you ….X? What do you think of ….X? You said X can you explain why?”. Try to prompt the user, then let them do the talking. Imagine it as a conversation with a friend who’s just come back off holiday, let them get it of their chest, it’s your job to listen.</p><p><strong>3. Remember that it’s their first time every time</strong></p><p>If it’s your last participant of the day you’d be forgiven for being a little bit lethargic, a little bit fed-up possibly and generally just wanting to go home. However, people are giving up their time and it’s important to respect that, especially if you want them to come back in the future, which you might. Don’t make assumptions (as mentioned) because of what you’ve heard from participants earlier in the day and treat each person like a new customer coming to your business. It’s their first time, so make them feel comfortable and valued.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*t4Zrim8nqPqdtvlj7UUdtQ.jpeg" /></figure><p><strong>4. Allow time in-between for participants</strong></p><p>There’s no point having a rushed, uncomfortable researcher and similarly, there’s no point having panicked, rushed participants, it’ll only end in a worse quality of results. Put plenty of time between participants, people will frequently be late, no matter how much faith you might have and sessions may naturally run over. So just try to err on the side of caution and give yourself and them a little buffer to stay on track.</p><p><strong>5. Have a back-up (and then maybe a backup of that)</strong></p><p>Things go wrong, things get lost, issues occur (see Murphy’s Law). Just make sure you have a back-up. Make sure your laptop and/or phone is fully charged, that you’ve got the charger as well just in case. Make sure you’ve access to WIFI, know where the toilets are etc. and be sure to print off or have to hand more than is necessary of any items you’re planning on giving to users in case any might get ruined or lost and need replacing.</p><p><strong>6. Get participant’s contact information (before the test)</strong></p><p>Sound simple, i’ve made the mistake plenty of times. Email, phone number, whatever its is, make sure you get it off them when they sign-up and give them a gentle reminder perhaps the morning of the user-testing session. If one person is late and you’ve set an ambitious number of people to trial during the day, then any set-back can have a undesirable effect on your next sessions for that day. People forget things, so just try to mitigate it by being on top of who’s next and give them a little nudge if needed.</p><p><strong>7. Expect Drop-outs</strong></p><p>If you’ve never had a drop-out to your session, well done you. Unfortunately i’ve always found this to be par for the course, but you can help to mitigate this by giving people the gentle reminders (with the contact info). With this in mind you may want to try recruit more than is necessary (e.g. + 5 to 10% of your target) depending on your total. This is especially important for those conducting quantitative research and require a threshold level to get any statistical significance as dropouts may mean you don’t have enough to ascertain statistical significance even with strong results.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/0*tiIYcyqryEBUkx1h" /></figure><p><strong>8. Try to be focused in the research</strong></p><p>Trying to get as much information as possible back from the participant can often make it hard for you as the researcher to capture and also difficult for the user to articulate their feedback if there’s lots to consider. If possible, try to be focussed in an area you want to know about or test and break it down in to more easily tested chunks. You’ll be able to get really riched informed information on the aspect you do chose to test. However, there is certainly a different benefit in testing something as the sum of its parts rather than individually. If this is the case, think thoroughly about what it is you’re wanting to test and ask and ensure that these key issues items are tested and not missed amongst the general patter of the user-testing conversation.</p><p><strong>9. Don’t do user-testing with a working prototype which only has low functionality</strong></p><p>This might sound unusual, but i’ve learnt from experience on this one. I’ve found it’s always better to test early in terms of fidelity for a few reasons. The first two being cost and time, it’s obviously easier to knock-up a sketch, wireframe or interactive prototype then one which has been fully coded by the developer, besides any changes needed you’ll be able to make yourself when iterating. Secondly and probably more importantly is people’s expectation levels. It’s genuinely astonishing how much this matters when you give someone a working live environment, which has been developed, but is missing a lot of future functionality which will be created in future sprints (for example). You can preface it to the participant, however there is every chance you’ll end up with them pointing out issues, which you believe you are awaiting development, or criticisms which are fair, but are born from issues which would otherwise be not existent in a fully-working model. You may spend too much time on these issues, not where you want to focus and probably already have one-eye (as a team) on fixing the issue anyway. It can put the whole session out of sync and probably isn’t presenting the user with a fair representation of the product anyway, even when looking at a small area as they could well be off put by what they’ve seen. Low-fidelity helps to shape their expectation. Sketches and wireframes remain malebale in their minds and they’re more likely to understanding that the product is ‘in development’.</p><p><strong>10. There’s always qualitative data to be gathered (or almost always)</strong></p><p>In essence, if you’re speaking to someone and getting them to go through a user-test to collect quantitative data, then it might be a missed opportunity for you to get their thoughts and opinions (qualitative data). If they’re rating, or completing a task which is being measured, chances are they’ll be talking to you about it, so don’t miss the opportunity to note this down. Qualitative data ultimately helps to tell us the ‘Why is X happening?’ to the Quantitatives ‘What is happening?’. Even if it means a dictaphone to record what’s being said, just to be sure to obviously get their permission. If speaking or note taking from the participant may actually be a confound, either obstructing the user or biasing the results, then you will obviously want to avoid this, but it’s worth asking the question when you are creating your user-test.</p><p><strong>11. Always run a pilot test!</strong></p><p>…and finally, this will help to iron out any inevitable bumps or kinks in the test, remind you of anything you forgot and potentially make you rethink the approach completely if you find it doesn’t actually work. Plan it in as an essential part of the user-testing so that a pilot test doesn’t go uncompleted. Completing one beforehand is invaluable, as will be known by anyone who has conducted a user-test before.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fb3e808%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Fb3e808%2F&amp;image=http%3A%2F%2Fapi.screenshotlayer.com%2Fapi%2Fcapture%3Faccess_key%3Dfe59908dad3baab69ffab249a2224b03%26viewport%3D1024x612%26width%3D1000%26url%3Dhttps%253A%252F%252Fupscri.be%252Fb3e808%253Fscreenshot&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href">https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aa80ab459efa" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/why-confidence-is-key-and-10-other-useful-tips-for-user-testing-aa80ab459efa">Why Confidence is Key and 10 other useful tips for User-Testing</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 Alternative User Research methods for Agile development]]></title>
            <link>https://uxplanet.org/3-alternative-user-research-methods-for-agile-development-43073a70871d?source=rss-7292f71f2f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/43073a70871d</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[user-testing]]></category>
            <dc:creator><![CDATA[John Rimmer]]></dc:creator>
            <pubDate>Wed, 29 Aug 2018 09:04:32 GMT</pubDate>
            <atom:updated>2018-08-29T12:31:23.658Z</atom:updated>
            <content:encoded><![CDATA[<p>Well-structured, orthodox user research no doubt has its place. The ability to target and test specific areas of a product using eye-tracking, Likert scales or gauging opinion through structured Q&amp;A can yield important insights for companies and academics alike. However, sometimes all those great techniques just simply aren’t possible and occasionally may not be necessary or the right approach when trying to learn more about your user.</p><p>Research is all about asking the right questions for the right reasons and being able to reflect honestly on the Pros and Cons of the research you’ve conducted in order to infer actionable outcomes. The following Alternative Qualitative Research methods are not without their limitations in terms of what they might tell us about the user, however, when applied correctly, they are a great way to provide the user with an engaging and interesting session, which can give your product team valuable and intriguing insights in to how your users feel about your product.</p><h3>1) The Emoji Journey</h3><p>Take a user that reflects one of your key personas through the use case scenario you’re wanting to gain insight in to. Have a set task/s that you’d like them to complete in order to satisfy the use case. E.g 1) Search for product, 2) Refine search, 3) View product details etc. For each of the steps, ask the user to select one of the emojis to describe how they’re feeling towards the product at that point in time. Once they’ve selected their emoji, ask them whether they can expand on this and explain why it is they feel this way. Next, take the use through the journey again, but this time asking them to select an emoji to demonstrate how they would like to feel for each task. This technique allows the design/develop team to then bridge the gap between what the user currently feels (As Is) and what they expect from the product (To Be).</p><p>Emojis are a great way to communicate things which we often find hard to put into words, especially when user testing. Whilst having something physical gives them an option to choose and get the figurative ‘ball rolling’ with their thought process. Try laminating a range of emojis from the internet and use a grid to allow users to stick them on and fill in their reasons. Physical props are always a great way to engage with users who may need encouragement in buying-in to the session.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*yrEhSMMD-oK2RF-z" /><figcaption><em>Emojis added to show “How I feel” and “How i’d like to feel” .</em></figcaption></figure><p><strong>When might it best be used?</strong></p><ul><li>Initial Research looking at As Is and To Be scenarios</li><li>Use it to benchmark against either a competitor by modifying slightly</li><li>Use it to help validate the design</li></ul><p><strong>What are key outcomes?</strong></p><p>Allows the researcher to understand a user’s overarching emotion at the different stages of the user journey as well as how they would want to feel at this stage with reasoning. Armed with this information, your product team can then look to implement changes which look to improve the experience for your users overall and not simply implementing direct individual feedback from users which may be without context.</p><p><strong>How do I implement this?</strong></p><p>Paper, pens, printouts, get creative. Arrange for participants to test as normal. Consider the use case or scenario you would like to use then simply take them through the process. Allow them to lead you when providing their reasoning and insights.</p><p><strong>What are the benefits vs traditional methods?</strong></p><ul><li>Looks to infer what their emotion towards the stage with reasoning over direct questioning which can often result in users becoming critical of specific features rather than the experience as a whole</li><li>A creative and informal approach which can help to obtain more honest and less sensitive feedback, whilst also being cheap and engaging</li><li>Selection of an emoji helps to reduce some of the ambiguity in responses from the user</li></ul><h3>2) Colour by Importance</h3><p>This technique can be used as a piece of initial user research to understand the needs and wants of users and in particular their mental mapping, as a validation piece following design iterations to to understand the degree to which the users may place emphasis on different aspects of the product, or even within your own product teams. This technique can help your team to visually see what each others’ perception of the product is and what it’s key characteristics are.Regardless of when you choose to implement this, the general format remains the same, just that the outcomes will differ.</p><p>As an example, allow your users to familiarise themselves with the product, this may simply be context around what the product is trying to achieve, viewing current designs or playing with a working prototype, maybe 5 minutes or so, before asking them to recreate it by drawing. Give the participant 3 pens in 3 different colours (e.g. Blue, Red, Yellow), for 3 minutes (1 minute per colour) and ask them to start sketching out the product.</p><p>For the the first minute have them use only the Blue pen, then for second minute the Red, the third minute using the Yellow. Ask them to start sketching what they would like the product to be and how it should be laid out etc if in <em>discovery</em> or when <em>validating</em>, ask users how they remember the product to be. This technique allows the researcher to subtly infer what the user feels are the most important aspect of the product to them. Restricting time pushes them to sketch without too much conscious thought and will help to push them towards adding the finer points of detail at the end i.e. the elements of secondary/tertiary importance.</p><p>In the first minute (Blue) the user will hopefully sketch out elements they feel are of greatest importance/prominent, with the second minute showing secondary (Red) then (Yellow) tertiary importance. It’s important to remember this is only a guide to the user’s thought process and you may want to retrospectively ask for their reasoning behind how they constructed their product. If needed this technique can be extended to try with consecutive pages of a product, for example giving 3 minutes on each page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*p8OQoRSQfcaiYUbQ" /><figcaption><em>Example of a banking app asked to be recreated by the user changing colours every 30 seconds(Left). Why not use templates and get the user sketch different steps of the journey? (Right)</em></figcaption></figure><p><strong>When might it best be used?</strong></p><ul><li>With internal Product teams</li><li>Initial User Research</li><li>Validation of Design</li></ul><p><strong>What are key outcomes?</strong></p><p>The research is able to infer what are the most primary, secondary and tertiary components to the user, whilst follow up questions help to validate any assumptions as to why the user has sketched their product in such a way.</p><p><strong>How do I implement this?</strong></p><p>Very simply. Get 3 pens of different colours, which contrast of course, a bit of paper and you’re away! (Oh and a few participants)</p><p><strong>What are the benefits vs traditional methods?</strong></p><ul><li>Doesn’t ask direct or leading questions, reducing bias</li><li>Users able to visualise their thoughts which can be provide invaluable insight</li></ul><h3>3) The Love letter/ Break-up letter</h3><p>This one’s nice and simple. Get the user to consider what they either love or hate about your product (or both) then ask them to write the product a letter to tell it how they feel. Putting it down in words will help to identify what they think is really important to them and isn’t too taxing from a user-testing perspective. This method helps to tap in to more emotive feeling towards your product and can provide really rich information which would be otherwise difficult by asking “What did you like/dislike about the product?”.</p><p>You can even try a modern-love technique for remote users and send the product out online, asking them to send in their love/break-up letter via email. The beauty of this method is that it’s short and concise, requiring less from the user. The informal approach will also help the user to be more honest about their feelings when being critical/praising of the product, which can be hard in a face-to-face user session when being asked by someone who they will invariably assume is involved with the design of the product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/654/0*MnoJyHi5VrmZlqej" /><figcaption><em>Love letter to eBay .</em></figcaption></figure><p><strong>When might it best be used?</strong></p><ul><li>Validation after a design iteration</li></ul><p><strong>What are key outcomes?</strong></p><p>This technique provides rich insights into the most important thoughts and feelings of your users good and bad.</p><p><strong>How do I implement this?</strong></p><p>Ask people who have previously used the product or allow time for a user to play around with the product before getting them to pen a letter. Don’t skimp on the lined paper and make sure you tell them to be as open and candid with their feelings, honesty is always the best policy — even in a breakup (ish).</p><p><strong>What are the benefits vs traditional methods?</strong></p><ul><li>Rich information</li><li>Allows participants to be open and honest</li><li>Cheap and easy to set-up</li><li>Able to be completed remotely</li></ul><p><strong>N.B.</strong> These techniques can and should be changed depending on the need of your research, context and constraints. What’s important is the right research technique being used for the right reason. Don’t have the right equipment? — Use a close alternative you can find. Seem to be running out of time with participants? Reduce your time slots. It’s about being sensible and transparent with the results in respect to what was conducted. As product owners, we will know the direction and restrictions of the product we are developing. It’s important to understand the goals and frustrations of the user, but not take their lead on what they want the product to be, that’s our job as a development team.</p><p>If you’re wanting to hear more about our research methods and how we can help you undertake these, please get in touch at <a href="https://www.answerdigital.com/">Answer Digital</a> to start gathering reliable insights on your customer.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fb3e808%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Fb3e808%2F&amp;image=http%3A%2F%2Fapi.screenshotlayer.com%2Fapi%2Fcapture%3Faccess_key%3Dfe59908dad3baab69ffab249a2224b03%26viewport%3D1024x612%26width%3D1000%26url%3Dhttps%253A%252F%252Fupscri.be%252Fb3e808%253Fscreenshot&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href">https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=43073a70871d" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/3-alternative-user-research-methods-for-agile-development-43073a70871d">3 Alternative User Research methods for Agile development</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>