<?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 Iain Kerr on Medium]]></title>
        <description><![CDATA[Stories by Iain Kerr on Medium]]></description>
        <link>https://medium.com/@iainkerr?source=rss-cfa40c45583e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*DvGL0RYMKHwFt1RQ.</url>
            <title>Stories by Iain Kerr on Medium</title>
            <link>https://medium.com/@iainkerr?source=rss-cfa40c45583e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 19:46:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@iainkerr/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 key to taking a good note]]></title>
            <link>https://medium.com/fanduel-life/the-key-to-taking-a-good-note-365bdc0b64c6?source=rss-cfa40c45583e------2</link>
            <guid isPermaLink="false">https://medium.com/p/365bdc0b64c6</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-and-design]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[notes]]></category>
            <dc:creator><![CDATA[Iain Kerr]]></dc:creator>
            <pubDate>Fri, 29 Nov 2019 12:48:24 GMT</pubDate>
            <atom:updated>2019-11-29T14:20:04.619Z</atom:updated>
            <content:encoded><![CDATA[<p>Product design and development moves fast. It can cause decisions to be made without an understanding of who your users are and what they need.</p><p>At FanDuel we move as fast as we can, and to make sure we inform our decisions with user research we involve as many disciplines as possible in attending research sessions. Over time we’ve found that getting the wider teams involved in note taking is a great way to ensure focus; it forces you to really listen and observe. But, at first, not everyone knows what they should be taking note of and what they should avoid.</p><figure><img alt="Observer notes on our user research tool, Lookback" src="https://cdn-images-1.medium.com/max/1024/1*1Esrw-L9N0vFiu4tOkrSxg.png" /><figcaption>Observer notes using our user research tool, Lookback</figcaption></figure><p>Here is some guidance we’ve put together for colleagues who participate in user research sessions and take notes.</p><h3>What makes a good note?</h3><p><strong>Observations</strong>: What the user actually does, or did.</p><p>Focus on the actions the user takes, for example: “hovered over the deposit button, then scrolled down the page. Clicked on the learn more link and read the information”</p><p><strong>Quotes</strong>: What the user actually said</p><p>It’s really important to record exactly what the user says. This means that the note contains the quote in the users own words — which is really key to understanding the user’s goals, motivations, and frustrations.</p><p><strong>Context</strong>: Where the user is in the flow</p><p>When reviewing the notes, if they contain the location/screen of where the user is when they say or do something it makes it much easier to know if this is what you’re looking for. So make sure there’s context on your notes.</p><p><strong>Succinct details</strong>: Keep notes brief, but useful</p><p>This one takes practice, but the notes should give enough information to get some value from them on their own.</p><h3>What makes a bad note?</h3><p><strong>Paraphrasing</strong>: Don’t put words in the user’s mouth</p><p>Paraphrasing will cause the notes to be less accurate as they could contain your own views or biases. It’s easy to just record exactly what the user says, so do that.</p><p><strong>Vagueness</strong>: Keep them useful</p><p>A vague note is a waste of a note. It’ll either go in the bin, or someone will have to watch the clip back and take the note again themselves.</p><p><strong>Solutions</strong>: Now is not the time</p><p>Focus on the user’s goals and pain points, don’t assume that you know what would fix the problem when making notes.</p><h3>What makes a good note-taker?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FShNhUWuThZQEb5KZmkMYg.jpeg" /><figcaption>Sticky notes (a researcher’s best friend)</figcaption></figure><p><strong>Remove distractions</strong>: Put phones and laptops away. Put all of your attention into the research session.</p><p><strong>Listen and watch objectively</strong>: record things as they are</p><p><strong>Write your own questions</strong>: they can be passed to the researcher or discussed afterwards.</p><p><strong>Using sticky notes (a researcher’s best friend): </strong>we all know researchers love a sticky note, at FanDuel we’re no different. However, we do try and follow some simple rules when we use them during any research session:</p><ul><li>Written clearly — ALL CAPS is a good approach</li><li>Use a bold, black marker</li><li>Keep it succinct, but not vague</li><li>One note per sticky</li><li>Label it with the participant number and the identifying part of the flow</li></ul><p>If you put these tips into practice the next time you’re involved in user research, you’ll find that it’s all quite straight forward. Get involved in the analysis and you’ll see how impactful it is too — there’s no better way to learn or improve your skills than by doing.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=365bdc0b64c6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fanduel-life/the-key-to-taking-a-good-note-365bdc0b64c6">The key to taking a good note</a> was originally published in <a href="https://medium.com/fanduel-life">FanDuel Life</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I became a better UX researcher, by becoming a research participant]]></title>
            <link>https://uxdesign.cc/how-i-became-a-better-ux-researcher-by-becoming-a-research-participant-20dfc5e48874?source=rss-cfa40c45583e------2</link>
            <guid isPermaLink="false">https://medium.com/p/20dfc5e48874</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[design-research]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Iain Kerr]]></dc:creator>
            <pubDate>Thu, 21 Feb 2019 13:41:08 GMT</pubDate>
            <atom:updated>2019-02-22T04:37:14.427Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kZC5jDjv8iwKgE9nZ_tOfQ.jpeg" /></figure><p>I became a remote user research participant and did usability tests and interviews to get a wee bit of extra cash, to learn how other companies approached research and to think about how I could improve my approach based on what I experienced.</p><p>It might seem like an odd thing, a researcher masquerading as a participant, but your profession doesn’t stop you from being a beginner or from providing honest answers to tasks and questions that can be of value.</p><p>When I first started in UX I was often told that my screener should exclude anyone that worked in a related field. Design, Marketing, Research and so on.. And that made complete sense to me. I was told that these types of users wouldn’t give a fair account as they’re often experienced in issues, will know how to resolve mistakes or don’t check their ego and offer up unwanted opinions.</p><p>But, now I can tell you, I think the opposite is true. In fact, I’d argue that you’ll get super valuable insights from these types of people — as long as they fit the target audience you’re looking for. Need people that have never used your software before? It doesn’t matter if they’re a researcher. Need people that are experts with your software? It doesn’t matter if they’re a researcher.</p><p>What matters most is that you put time in to think about what users will give you the most valuable insights and then target them. Makes sense, right?</p><h4>Becoming a participant</h4><p>To become a participant I signed up with usertesting.com — I filled in my details and completed the trial session. I got some feedback on how to improve and then I was ready to go. My dashboard started to fill with tests I could complete and it was as easy as that. Most tests come with a screener, so more often than not I find that I’m not who they’re looking for.</p><p><em>It’s worth being explicit here that I never lied or hid my profession when taking screeners or in interviews. Some of the tests excluded me, but enough didn’t to make it worth while. Everything was above board.</em></p><p>Oh, and why did I decide to do this? 3 reasons.</p><ol><li>I wanted to learn how other companies and researchers were working, what questions they asked and how they designed their studies.</li><li>I wanted to have a better experience of what it was like as a participant, what worked well and what was awkward.</li><li>The incentives for taking part could allow me to treat myself to some new shoes.</li></ol><h3>Key insights from my experience</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9N3RZIwgO8kH50BHN8M0nA.jpeg" /></figure><p><em>Or, some tips for creating a good remote research session.</em></p><h4>1. Don’t waste the user’s time</h4><p>Often tasks will repeat themselves. As a user I’ll read what I need to do, make sure I understand it and be ready to start — but then, it’s been designed that I need to click through repetitive content and tasks. This just disrupts the flow of using the site and takes away focus.</p><blockquote>For example, the 1st thing I read will be ‘You’ll see a website and we want to know your first impressions’. Okay cool, I’m ready — I hit start and then I get another message. ‘For this task we want you to browse the homepage and share your thoughts’ — Yes I know. I’m ready to do it , just show me the thing. Steve Krug might advocate that number of clicks doesn’t matter, but maybe this is an exception. I found myself frustrated when I was prevented from getting going due to the design of the test/things I had to click through.</blockquote><h4>2. Keep tasks clear and simple</h4><p>This follows on nicely from the above. Just state in layman’s terms what you want me to do and leave me to it. Don’t be overly wordy, don’t ask too much, but be specific. At the same time, don’t patronise either. It’s a fine line, but a good one to be walking.</p><p>Icons can be confusing. It might seem like a great idea to include a black star or a smiley emoji as a way of communicating to the user they’ve reached the desired page. But honestly, it’s confusing. Instead, include splash pages with the instructions on them. Such as a plain white page, with some text stating — “great, you’ve finished this task — check task #2 before continuing”</p><p>It communicates to the participant that they’re on the right track and keeps them focused on what you need. I often found myself unsure if I was doing the right thing when icons were used or instructions were vague.</p><h4>3. Use consistent language</h4><p>This is easy. If you tell someone that they should go through the task until they get to the profile page, or the completion page, or the WTF question — make sure that the intended point is labelled as you described it.</p><p>It’s confusing when you think you might be at the right place, but it has a different name from what you were expecting or from what you were told.</p><h4>4. Do a run through of your test before you share it</h4><p>Maybe this is the solution to the 3 points above. Go through your test as if you were a participant, ask a colleague to trial it. Then iterate on your test until it works as intended — this will help make sure that you get the best results. For unmoderated research, there’s nothing more you can do once the test goes live. Do everything you can to get it right first time.</p><h4>5. Prompt users or be specific if you need certain data</h4><p>If something is really important to your research, then make sure you ask about it. Did the user notice something on a page, or did they understand what they’ve just signed up for — don’t assume the user will know to talk about this, or that they will do it naturally. So think about prompts or follow up questions to make sure you cover everything you need to.</p><p>You don’t want to get the results back and realise that you didn’t get the information you needed, because the test could’ve been designed better.</p><h4>6. Don’t ask users about what they would do or what would convince them</h4><p>It’s one of the hardest questions to answer “what would convince you to sign up for this?” or “What would you do when this happens”?</p><blockquote>Important: users can’t predict their future — so always focus on past behaviour or experiences</blockquote><p>I never truly understood just how difficult this type of question is to answer until I was asked it. I found myself just trying to come up with some random suggestion, so that I answred the question — but really that isn’t helping anyone. So don’t do it, there’s nothing of value to be found here.</p><h4>7. Don’t ask people the ‘magic wand’ question</h4><p>I’m gonna go out on a limb here and say that no one gets much value from this. It gets asked a lot and honestly, I always feel like it should be clear from the discussion or feedback as I’m going through tasks what felt like an important change. When this comes up it just feels a bit strange and difficult, there must be far better questions you could ask to get valueable information here</p><blockquote>Some ideas: Can you talk about another website you’ve used like this that you really enjoy using and why? Can you talk about the last sign up process you completed and what convinced you to sign up? Does our website remind you of any other websites and how would you compare them?</blockquote><p>I don’t have the right answer, but stop with the wizard stuff.</p><h4>8. Try and leave feedback</h4><p>It might take a bit of extra time, but if you don’t think the user was a 5 star recruit — let them know why. I got a couple of 4 star reviews and it would’ve been really helpful to know what was missing so I could improve for next time. In the long run, this helps everyone.</p><h4>9. If you’re not doing it — try it</h4><p>For how fast it is and how cheap it is, you’re crazy not to try it. I’ve worked in places that spend £3k-£4k on going to research labs to sit with users and do tests in person. If you’re doing that, check out the remote stuff and see what you think.</p><p>You could do more research, with more iterations, with more users and create a better product if you start doing more remote research.</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=20dfc5e48874" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/how-i-became-a-better-ux-researcher-by-becoming-a-research-participant-20dfc5e48874">How I became a better UX researcher, by becoming a research participant</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[The importance of finding the right users (and how to do it)]]></title>
            <link>https://uxdesign.cc/the-importance-of-finding-the-right-users-and-how-to-do-it-a5603bab19ff?source=rss-cfa40c45583e------2</link>
            <guid isPermaLink="false">https://medium.com/p/a5603bab19ff</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[usability-testing]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[Iain Kerr]]></dc:creator>
            <pubDate>Tue, 21 Aug 2018 15:07:22 GMT</pubDate>
            <atom:updated>2018-08-23T10:56:28.367Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*x4noYDgPTT3vfRbz0zdDIA.jpeg" /></figure><p>Choosing your users is one of the most important elements of user research and time and again researchers and designers fall into a bit of complacency when it comes to choosing the participants. It’s often talked about designing with accessibility at the start, or working on edge cases — but it’s challenging and everyone can succumb to the easy option now and then.</p><p>The problem with this is that you may miss some really important insights, or you may make false assumptions about your product. Users that have a sense of familiarity with digital products, simply won’t give you the same amount of value or insight into how something works. These users have their experiences with other apps to guide them and can work their way around problems; which might not always be apparent to you when observing.</p><p>If you want to get the maximum value from your research then you need to give a lot of thought into who you should research with. Look for users that have learning difficulties, accessibility needs, language differences. This is where you can really put your design to test.</p><p>Let’s say that you’re working on a new app for NIKE — it might make sense to do some quick pop up testing with young people in the street or a cafe and sure, you’d learn a few interesting things. But chances are, these people already have a good understanding of how apps like this work. So are you really testing the product, or just looking for validation it matches conventions?</p><p>What if, instead we..</p><p>What if we took the app to people who have never used a sports app on their phone? What if we looked for people that don’t use their phone for shopping? What if we worked with people who’re still on an outdated smart phone? Or what if we looked for people who don’t use a smart phone, or own one at all? It’d be harder to find them, but how much could that tell us about how intuitive our app is. How much could we learn about the way people understand our app and how we can make it easier and more effective.</p><p>The solutions to any of the problems you identify will likely benefit all of your users. Making something more usable shouldn’t be exclusive to a particular user group.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wSuQcIZu-5Cti_UhaJ4V3g.jpeg" /></figure><p>So what’s a good way of finding the right users?</p><p>Think about what the important characteristics of your ideal users are and use this to create a robust screener. Then work with the resources you have to get in touch with some people who may or may not use your product, here’s 3 tips to keep in mind.</p><ol><li>Focus on the behaviours of your users as opposed to demographics. Think about the specific behaviours that would help identify someone you could get a lot of value from. For example, if you’re working on Amazon’s Alexa, find people who’ve never voice technology before. Find users who have used a competitor’s like siri. Find people who’ve tried one of the products then stopped. And find people who use this technology all the time. Doing it this way will help to make sure you get a robust set of data and begin to understand the problems users face at the different levels of engagement.</li><li>Find people who have a lot to say. It’s no use having the right person if they don’t like to talk much. So ask them a few opened ended questions. i.e Tell me about how Alexa fits into your life? — From this you will be able to identify if this person is going to have a lot to say and will be worth following up on. If they have a lot to tell you about, these are the people you want to spend your time with.</li><li>Make it worth their while and do it on their terms. Be flexible. You’ve identified these really high value users, so do your best to make sure you can meet them. The last thing you want is to put all this effort in and they don’t show. So work with the user, agree a location that suits them or make sure the location your using is easily accessible. Offer them a good incentive and just be a good host. Treat people like you would like to be treated. It can be overstated enough how important this is.</li></ol><p>If you start doing this, you’ll get better insights and your research will hold have far more value. In turn, it’ll make you a better researcher and a better designer.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%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/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a5603bab19ff" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/the-importance-of-finding-the-right-users-and-how-to-do-it-a5603bab19ff">The importance of finding the right users (and how to do it)</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How you write User Stories doesn’t matter — so stop wasting your time]]></title>
            <link>https://medium.com/@iainkerr/how-you-write-user-stories-doesnt-matter-so-stop-wasting-your-time-5de7e5141db7?source=rss-cfa40c45583e------2</link>
            <guid isPermaLink="false">https://medium.com/p/5de7e5141db7</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[user-stories]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Iain Kerr]]></dc:creator>
            <pubDate>Thu, 31 May 2018 12:33:50 GMT</pubDate>
            <atom:updated>2018-05-31T12:33:50.357Z</atom:updated>
            <content:encoded><![CDATA[<p>When I first started working in Agile I loved that everyone was spending so much time working on user stories. Writing them, prioritising them, creating digital and paper versions, sticking them up, taking them down. Great.</p><p>But the one thing that remained a slight mystery to me was what were people actually doing. No one was talking about them or what was on them. A new bunch of stories would be added to the backlog — so what? What stories? Tell me about them.</p><p>I didn’t say anything though. I was new and I assumed this is just how shit was done and I couldn’t articulate why it didn’t make sense to me.</p><p>But here’s some things I observed:</p><ol><li>People fret so much about the user story format. Nitpicking on details and worrying about it sounding like a real user.</li><li>People were prioritising them in isolation. Product owners would take on this task to divvy up the work and then the rest would follow suit.</li><li>Discussion would revolve around what work was being done on that particular story.</li><li>Sometimes it wouldn’t even be clear to half the team what certain stories were for or why they were doing this piece of work.</li><li><a href="https://www.gov.uk/service-manual/agile-delivery/writing-user-stories">So much guidance and information focuses on how to write and record user stories. Not on how to use them.</a></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/983/1*h38kBeXVEt4-khwUujlTaQ.png" /><figcaption>Common user story searches</figcaption></figure><p>So what have I learned?</p><p>User stories need to involve discussion to be useful. They’re not just a record of work being done or acceptance criteria. If you want your team to be engaged, understand and most importantly have some input into the work then use the user story to start a discussion.</p><p>Acceptance criteria will form based on an understanding of the problem to be solved and by working out how big a problem it is, together, it can be prioritised with the knowledge and input of many people.</p><p>By doing this, it creates greater understanding among the team, a better working environment and higher engagement when it comes to things like user research, workshops and planning.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5de7e5141db7" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>