<?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 Milos Danilovic on Medium]]></title>
        <description><![CDATA[Stories by Milos Danilovic on Medium]]></description>
        <link>https://medium.com/@milosdanilovic?source=rss-bd7e7040344a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*6y4--3XAMjtJON6l1dpwaA.png</url>
            <title>Stories by Milos Danilovic on Medium</title>
            <link>https://medium.com/@milosdanilovic?source=rss-bd7e7040344a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 23:23:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@milosdanilovic/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[Running a remote user research study]]></title>
            <link>https://uxdesign.cc/running-a-remote-user-research-study-981251fc5379?source=rss-bd7e7040344a------2</link>
            <guid isPermaLink="false">https://medium.com/p/981251fc5379</guid>
            <category><![CDATA[user-testing]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[remote-user-research]]></category>
            <category><![CDATA[remote-user-testing]]></category>
            <dc:creator><![CDATA[Milos Danilovic]]></dc:creator>
            <pubDate>Fri, 18 Feb 2022 11:04:03 GMT</pubDate>
            <atom:updated>2022-02-18T11:04:03.275Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ucdhJKV1sZvXecE3" /><figcaption>Image courtesy of <a href="https://designstripe.com/">designstripe</a></figcaption></figure><p>Whilst in-person interviews continue to be the gold standard in conducting user research interviews, simply because human beings are naturally wired to communicate in-person rather than through screens, the current climate in the world (Coronavirus) has required us to adapt and pivot to doing user research studies remotely.</p><p>There are some great advantages that come with doing user research interviews remotely. These include opening your pool of potential participants, saving time and cost on travel, and increasing chances of participation since the participant can be anywhere.</p><p>Although a lot of the following tips can be applied to in-person user interviews as well, this guide will give you some things to look out for and help you be more prepared for your next remote user research study.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0rwFD25Fgt_QRBEU" /><figcaption>Image courtesy of <a href="https://designstripe.com/">designstripe</a></figcaption></figure><h3>Plan ahead</h3><p>Like that saying goes “If you fail to plan, you are planning to fail” and it’s no different when it comes to running remote user research sessions. While it may require a bit more work, preparation is vital to ensure your user research studies are as successful as possible.</p><p>So then, how do you best plan ahead? Here are some tips that are worth considering when planning your next session.</p><h4>Create a research plan</h4><p>Writing up a test plan will help you get your thoughts onto paper and make sure you have a clear idea of what it is you’re looking to achieve with the user research. It will also help you decide on what type of user research you need to do.</p><p>Some high level things you may want to cover off in your research plan are:</p><p><strong>Context<br></strong>Provide a brief overview of why this research needs to be done and how it will help with the work you’re currently doing</p><p><strong>Research goal</strong><br>What is the purpose of this research and what are you hoping to validate, uncover or learn</p><p><strong>Assumptions<br></strong>What are some assumptions the team currently has that you’re looking to validate</p><p><strong>Who, what, when, how<br></strong>Who are the right type of users you want to interview <br>What type of research are you hoping to do <br>When do you need to do it<br>And how are you planning on doing it</p><p><strong>Questions<br></strong>What questions do you want to ask, how should you phrase these questions (super important), are there any follow up questions you should consider</p><p><strong>Tasks<br></strong>If you’re doing usability testing, you want to know what tasks you’ll be asking participants to do and how to best phrase those tasks to avoid giving too many hints away which may bias the results you get from the test.</p><h4>Share with your team</h4><p>Once you’ve got your plan in a good place, it’s wise to share this with the wider team. Sharing with your team at this stage ensures that everyone is aligned on what the purpose of the research is before any interviews are started.</p><p>This will save you time in the long run, avoiding the potential disruption of mixed opinions once you’ve already started with user interviews.</p><p>The team may also be able to help you recruit the right participants that you want to reach out to for your user research.</p><h4>Test your interview setup</h4><p>If you’ve ever tried to demo something to your colleagues, you’ll know how easily things can go wrong at the worst possible time. Test your setup with a colleague, preferably someone who doesn’t know the project well so as to remove any potential bias. Testing your setup will help you identify any issues that might arise and will reduce the potential for future embarrassment when it finally comes time to doing the session with a customer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9UqjPHmiEgXX4Gyt23X99Q.png" /><figcaption>Image courtesy of <a href="https://designstripe.com/">designstripe</a></figcaption></figure><h3>Organise the interview</h3><p>On the surface, organising the interview might come across as self explanatory. There are however a few small things to remember which improve the chances of a successful user interview and a positive experience for everyone involved.</p><h4>Recruit participants</h4><p>One of my favourite methods of recruiting participants is to simply email them. Emailing your potential participants is a great way to find out who is interested in participating in the study, while also giving you the opportunity to give them some context.</p><p>In your email, try using common language by avoiding the use of terminology that may only be known internally or that could be considered industry jargon.</p><p>Also, consider including some of the following:</p><ul><li>Brief introduction of who you are and what you do</li><li>Short description of why you’re reaching out to them and how it will benefit them</li><li>An idea of how long the session will be</li><li>A link to your calendar (can use tools such as calend.ly)</li></ul><p>The above ensures that the participants will have all the vital information before making their decision to participate in the study. The link to your calendar is optional, but it will save you and the participants a lot of time on scheduling ping pong, trying to find a time that works for everyone.</p><h4>Invite a teammate</h4><p>Ask a colleague to join the interview as an observer and note taker. This leaves you fully focused on listening to the participant and asking good follow up questions.</p><h4>Send a follow up email</h4><p>You’ve sent your emails out and the customers have accepted your meeting invitations. You can choose to do a couple things, wait until the interview and hope for the best, or send a follow up email as a confirmation.</p><p>A follow up email the day before or the morning of the interview can act as a good reminder for the following:</p><ul><li>Session start time and how long the interview will be</li><li>Apps or tools that will be used like Zoom have been installed</li><li>Devices or equipment needed for the interview are ready</li></ul><p>This saves you from jumping into an interview, spending interview time on setting up or waiting around for 15 minutes, only to find out the participant won’t be joining.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Lo0t_l9ERcIxMds8" /><figcaption>Image courtesy of <a href="https://designstripe.com/">designstripe</a></figcaption></figure><h3>Run the interview</h3><p>Finally, you’re ready to conduct the interview. Although we have a clear goal in mind for our interview, it’s also a great opportunity to get to know the end users better.</p><p>Here are some tips that will help you run a smooth interview.</p><h4>Welcome participants</h4><p>When the participant joins the call, welcome them, thank them for their time and introduce yourself and your teammates. Ask them how their day is going before jumping straight into the interview process.</p><p>Give the participant a brief overview of what you’ll be covering in the interview. If you’re doing a usability test, run them through the process. A lot of people have never heard of or been through a usability test. It’s good practice to remind participants that there are no right or wrong answers and that we’re here to listen to all feedback.</p><p>If you’re thinking of recording the interview, ask the participants for permission before hitting the record button. For a usability test, you’ll want the participant to share their screen before you start the test.</p><h4>Ask better Interview questions</h4><p>Start with warm up questions that are easy to answer before you delve into the more specific questions. People tend to be more open about answering questions in more detail once you’ve established a rapport with them.</p><p>Some examples of warm up questions are:</p><ul><li>Could you please describe your role?</li><li>What does your business do?</li><li>Could you walk us through your average work day?</li><li>What other apps or software do you use on a regular basis?</li></ul><p>Once you think the participant is comfortable, you can start with some of the more involved questions. Remember to phrase these as open ended questions to encourage participants to give you more detail than you would otherwise get with closed-ended (yes/no) questions.</p><p>Here are some examples of how a closed question can be turned into an open question:</p><p><strong>Closed questions → Open Questions<br></strong>Do you use this feature? → How do you use this feature?<br>Do you like this feature? → What do you think about this feature?<br>Have you done this before? → Describe your experience with this<br>Was that difficult? → How was your experience with that?</p><h4>Usability tasks</h4><p>Being remote means there might be plenty of distractions for the participants as they go through your usability test. This sometimes makes it hard for the participant to stay focused on the task at hand.</p><p>Reading the task out loud to the participants is a good way to get them actively thinking about what it is that you would like them to do. It’s also useful to give participants the ability to refer back to the task if they need to be reminded of what they need to do. An easy way of providing that is sending a written version of the task via the chat feature in zoom.</p><p>If a participant gets stuck or confused midway through the task, try using facilitation methods such as echo, boomerang and Columbo to avoid giving away hints or asking leading questions.</p><p>Here’s a brief example of each of these methods:</p><ul><li><strong>Echo<br></strong>When a participant says something like “Interesting…” you might follow up with “interesting?” inviting the participant to elaborate further</li><li><strong>Boomerang<br></strong>When a participant asks something like “Do I have to login first?” you can deflect with “How would you normally do it?” so as to not give away the answer</li><li><strong>Columbo<br></strong>In an inquisitive manner you might say to the participant “you were hovering your mouse in this area…?” waiting and hoping that they might fill in the blanks</li></ul><p>Finally, when writing your tasks, try to avoid using any terms that will appear in the user interface. This ensures that you’ve removed any hints that the participant might not get in a real life scenario if they were to attempt the task by themselves.</p><h4>Finish the interview</h4><p>If you’ve asked all your questions and or gone through all your tasks with some spare time leftover, it could be a great opportunity to ask the participant if they have any general questions or feedback. You’d be surprised at how much useful information you can gather with this broad question. It’s also a good opportunity to ask if the participant would be interested in any future studies.</p><p>Once you’re all done, thank the participant again for their time and inform them that their feedback is critical to shaping how the feature or product turns out.</p><p>Ask your teammates to stay behind for a debrief to share and discuss notes. It’s best to do this right after the interview while it’s still fresh in everyone’s minds.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4DzPAq1p9OKW9ZcR" /><figcaption>Image courtesy of <a href="https://designstripe.com/">designstripe</a></figcaption></figure><h3>Reflect &amp; analyse</h3><p>You’re done with the interview and you’ve had a chance to debrief with your team to collect their notes. Now you need a way to share it with the relevant stakeholders in a digestible format.</p><h4>Find a home for your research</h4><p>It’s a good idea to keep all your research in one place. I personally love using <a href="https://dovetailapp.com/">Dovetail</a> as my home for all things user research. Dovetail makes it super easy to analyse, synthesise and extract insights from your user research interviews.</p><h4>Share with stakeholders</h4><p>Once you’ve synthesised all the notes into common themes and takeaways, collate all of it into a digestible format that can be shared with the team. A short report with a brief summary of key takeaways and next steps is usually popular with stakeholders.</p><h3>Additional Resources</h3><ul><li><a href="https://www.nngroup.com/articles/which-ux-research-methods/">When to Use Which User-Experience Research Methods</a></li><li><a href="https://www.nngroup.com/articles/task-scenarios-usability-testing/">Task Scenarios for Usability Testing</a></li><li><a href="https://www.nngroup.com/videos/remote-usability-test-part-1/">Running a Remote Usability Test, Part 1 (Video)</a></li><li><a href="https://www.nngroup.com/videos/user-testing-facilitation-techniques/">User Testing Facilitation Techniques (Video)</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=981251fc5379" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/running-a-remote-user-research-study-981251fc5379">Running a remote user research study</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[Building a usability lab that works offline]]></title>
            <link>https://uxdesign.cc/build-a-usability-lab-that-works-offline-2f2d39cbaf47?source=rss-bd7e7040344a------2</link>
            <guid isPermaLink="false">https://medium.com/p/2f2d39cbaf47</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[usability-testing]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Milos Danilovic]]></dc:creator>
            <pubDate>Sun, 06 Sep 2020 12:14:35 GMT</pubDate>
            <atom:updated>2020-09-08T12:00:43.345Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A person using a touch device at their desk with their laptop in the background" src="https://cdn-images-1.medium.com/max/1024/0*bNgvfqi283PQbXZV" /><figcaption>Photo by <a href="https://unsplash.com/@bugsster?utm_source=medium&amp;utm_medium=referral">Taras Shypka</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Usability labs are a great tool to gather customers&#39; feedback on flows, user interface design, and logic of a feature that is currently being built, or is in the early prototype phase (recommended).</p><p>Once you’ve run some usability tests, they’re also a great tool for sharing that feedback with the wider team as it demonstrates the customer&#39;s perspective in a more digestible form.</p><h3>Why use this tool</h3><p>The key advantage of a usability test over some other forms of feedback lies in the fact that you’re not just collecting the screen, or sound and the screen, but most importantly you get the customer&#39;s natural body language reactions to what they’re seeing on the screen.</p><p>This is vital as users will often say one thing, but do something completely different e.g. “oh yeah! this is easy” (a clear sign of confusion on their face).</p><blockquote>As a bonus, this setup doesn’t require an internet connection to run the usability lab.</blockquote><h3>What you’ll need</h3><p>Ideally, with any usability test you’ll want to record three key things:</p><ol><li>The screen the user is looking at</li><li>How the user interacts with the device</li><li>The users face for their reactions</li></ol><p>To do this you’re going to need the following:</p><figure><img alt="Top view of a MacBook pro laptop, an ipad table, two adapters, an ipad charging cable and a USB camera" src="https://cdn-images-1.medium.com/max/1024/1*tDBgFRCvXUsmMUMs7QO-EA.jpeg" /><figcaption>The items you’ll need for this setup.</figcaption></figure><ol><li>Visualizer app (<a href="https://apps.apple.com/au/app/visualizer/id1296177026?mt=12"><strong>download from app store</strong></a>)</li><li>Quicktime app</li><li>2 x laptops (preferably 1 older MacBook with USB ports)</li><li>Laptop charger</li><li>2 x USB adapters / or USB hub (new MacBooks don’t have USB ports)</li><li>The device you’ll be testing on (in this example an iPad on adjustable stand)</li><li>USB charging cable for iPad</li><li>USB camera</li><li>USB mic (<strong>optional but recommended</strong>) — you’ll need an extra USB port for this</li></ol><h3>Setting up</h3><p>There are a few things to keep in mind when you’re ready to start setting the lab up. While you’re organising when and where you’ll do the test, keep in mind that you’d preferably want somewhere that doesn’t have too much background noise and is well lit. These play a big factor when going back to the recordings to analyse the feedback.</p><blockquote>It’s always a good idea to test the setup before you head out so there are no surprises when you’re on-site with the customer</blockquote><p><strong>Below is an example of what you’re trying to achieve on your laptop screen:</strong></p><figure><img alt="A screen with a camera feed of a user interface, a person sitting down and the device the person is looking at" src="https://cdn-images-1.medium.com/max/1024/1*gEoyD4c38IP9qu_wIn0Y8A.jpeg" /><figcaption>What your recording laptop screen should look like</figcaption></figure><h3>Step 1 — Connect the hardware</h3><p><strong>With an old MacBook</strong></p><ol><li>Connect the USB camera into one of the USB ports on your laptop</li><li>Using the USB charging cable, connect the iPad to the second USB port on your laptop</li></ol><p><strong>With a new MacBook</strong></p><ol><li>Connect one adapter on each side of the laptop</li><li>Connect the USB camera into one of the adapters</li><li>Using the USB charging cable, connect the iPad to the second adapter</li></ol><h3>Step 2 — Download app</h3><p>Download the <a href="https://apps.apple.com/au/app/visualizer/id1296177026?mt=12">Visualizer app</a> from the Mac AppStore. This app will allow you to display all the camera feeds on your laptop screen. This makes it super easy to keep all things synchronised without any video editing software.</p><h3>Step 3 — Visualizer app setup</h3><p>Now that you have the app downloaded, you’ll need to get familiar with a few key features which you’ll need to achieve the desired result. Highlighted below are the three key features:</p><figure><img alt="The visualizer app user interface with camera, frame, and window icons circled" src="https://cdn-images-1.medium.com/max/910/1*w9BnV6Gc6tZoSMZKEKeGCw.jpeg" /><figcaption>The Visualizer app settings you’ll be using</figcaption></figure><p><strong>Top left — camera icon<br></strong>Choose which camera feed you want to show up in the app window</p><p><strong>Bottom left — resize the frame<br></strong>Resize the windows to your liking</p><p><strong>Top right — the + window icon<br></strong>Add a window to show a different camera feed</p><ol><li>Add the 2 windows that will be showing the face and device feeds on your laptop screen by clicking the top right +window icon twice.</li><li>Click the resize icon &gt; choose custom &gt; resize windows to have one sit on top of the other</li><li>Click the camera icon and choose the MacBook camera for the face window</li><li>Click the camera icon and choose the USB camera for the device window</li></ol><h3>Step 4 — QuickTime setup</h3><p>Start the QuickTime app and ensure you have the iPad connected to the laptop with the iPad USB charging cable. Follow the steps below:</p><figure><img alt="A screenshot of the quicktime app window with a drop down showing device names" src="https://cdn-images-1.medium.com/max/680/1*Lz4cKWmzSIEpyoVRFLtbZA.jpeg" /><figcaption>Setting up Quicktime</figcaption></figure><ol><li>Go to File &gt; New movie recording</li><li>Click the little down arrow next to the record button</li><li>Find the devices name and click on that e.g. My iPad</li><li>You should now see the devices screen on your laptop in the quicktime window</li></ol><p>If you do not see your device showing up in the menu, <a href="https://help.usertesting.com/hc/en-us/articles/360015651091-Connecting-Your-iPhone-or-iPad-to-Your-Mac-via-QuickTime-Player"><strong>follow these troubleshooting tips</strong></a>.</p><h3>Step 5 — Final touches</h3><p>As mentioned above you want to capture the screen on the iPad, the facial reactions, and how the user interacts with the screen. For this you need to do the following:</p><ol><li>Point the laptop camera in the direction where you anticipate the participants face will most likely be</li><li>Fix USB camera to the top of the second laptop screen and get a good angle of the device</li><li>Go to Quicktime app, Click file &gt; New screen recording</li><li>Click down arrow next to record and ensure your mic is on</li><li>If you’re happy with the setup hit Record</li><li>Turn the brightness down to 0% so that the participant doesn’t get camera shy</li></ol><p>This is what your setup should look like once you’re done:</p><figure><img alt="A person sitting down at a desk using a tablet with one laptop in front of them and one on their left side" src="https://cdn-images-1.medium.com/max/1024/1*rB5_bDEE0wJUpZSTaYixZA.jpeg" /><figcaption>Roughly what the final setup should look like</figcaption></figure><p>You may notice the second laptop is being used as a stand for the USB camera. This can be replaced by any item you can use to hold the camera up so that you can get a good angle of the testing device.</p><p>A big shout out to my ex-colleague <a href="https://twitter.com/Lifeofmle">Michael Le</a> who helped coming up with and testing this setup. If this article was useful, <a href="https://twitter.com/MikiDanilovic">follow me on Twitter</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/94/0*sa4HX3MjBlk7DG_l" /><figcaption>The UX Collective donates US$1 for each article published in our platform. This story contributed to <a href="https://www.bayareablackdesigners.com/">Bay Area Black Designers</a>: a professional development community for Black people who are digital designers and researchers in the San Francisco Bay Area. By joining together in community, members share inspiration, connection, peer mentorship, professional development, resources, feedback, support, and resilience. Silence against systemic racism is not an option. Build the design community you believe in.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f2d39cbaf47" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/build-a-usability-lab-that-works-offline-2f2d39cbaf47">Building a usability lab that works offline</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>
    </channel>
</rss>