Written by Lidia Vijga
Founders, let me emphasize that user testing is a critical tool for developing exceptional products people actually want. But here’s the thing – it’s tricky enough to do quality user testing in person, let alone remotely when your team is distributed across the globe. Get it right, and you gain invaluable insights to create a product people truly want. Mess it up, and you risk building something no one needs or wants. In my view, with the right preparation and testing tools, remote user testing can be even more effective than in-person.
Just imagine being able to gain real-time user feedback on your product without costly travel or long planning. What if you could identify major usability issues before launch and validate product-market fit from anywhere? With remote user testing, you can do exactly that. But only if you avoid common remote testing mistakes.
In this guide, I’m sharing field-tested techniques to nail remote usability testing and validate your product assumptions, so you can build a winning product your customers love.
Table of Contents
- What is Remote User Testing?
- Benefits of Remote User Testing
- Types of Remote User Testing: Moderated Vs. Unmoderated Vs. Crowdsourced Testing
- When to Conduct Remote Usability Testing
- The Importance of Remote User Testing at Different Stages
- How to Plan a Remote User Test
- Top Tips for Conducting Successful Remote User Testing Sessions
- Common Mistakes to Avoid During Remote User Testing
- Final Thoughts
What is Remote User Testing?
Remote user testing is the ability to test your online or digital product with users that are globally distributed anywhere in the world. Imagine if you’re building a new mobile application from the US, and can gather feedback from people who live in Australia, Germany, and Canada all on the same day.
Benefits of Remote User Testing
As a fellow startup founder trying to disrupt an industry, I know how tempting it is to fast-track product development. But take it from me, skipping user testing early on is one shortcut you’ll really regret down the road.
I learned this lesson the hard way back when I founded my first startup Briefbid, an RFP procurement platform that connected buyers and sellers in the media space. Eager to launch quickly, my team skipped testing our flow with real users first. Long story short – it completely bombed and we wasted months building features users didn’t even want.
After that epic fail, I vowed never to skip user testing again. But I didn’t want the high costs and slow speed of in-person testing to stall our agile development cycles. That’s when I discovered the massive advantages of remote user testing for startups like ours. Here are the major benefits I’ve seen first-hand from taking our testing remotely.
Remote testing is super fast
Remote testing sets a new bar for agility. You can gather feedback on concepts or prototypes in just days without any travel time. Speed is oxygen for startups, and rapid testing fuels faster iteration. Compared to traditional in-person testing, it’s incredibly fast for three key reasons:
- No travel logistics: With remote tests, you avoid all the time-sucking planning of transporting team members or users to a central location. No travel eats into your agile development cycles.
- Recruit globally: Casting a wide net, you can find test participants matching your user demographics within days versus weeks or months. The global talent pool expedites recruiting.
- Rapid iteration: As soon as you need feedback, you can start testing with qualified participants. Design iterations happen at lightning speed. Bugs can be identified and fixed promptly.
In my current startup, this acceleration helped us revamp our entire UX/UI much quicker than we expected. We were able to test and refine our onboarding flow multiple times in a single week. The velocity let us launch a polished user experience months faster than usual.
Remote user testing has much higher success rates
One of the main advantages of conducting remote testing is the higher success rates it offers. This is because people can easily participate from the comfort of their own homes, or even while in-between work meetings or other life commitments. This ease and convenience of participation can lead to more opt-ins and a greater chance of gathering a larger sample size for your research or survey. Additionally, online participation can also lead to more honest responses as people feel more comfortable answering sensitive questions in a private online environment.
Remote usability testing is capital-efficient
In my current startup, we have a bootstrapped mentality, which means we try to do as much as we can with limited resources.
Transitioning our user testing from in-person to remote has yielded huge cost savings. Before we pivoted to Decklinks, we used to pay for participants’ travel plus incentive gifts and meals. Now our incentives are smaller since we only cover their time, and remote users are often more willing to test for less since they incur no travel costs.
Cutting these costs resulted in nearly 60% of testing budget savings for our startup. This cost reduction means we can test 5x more concepts without inflating the budget. Our product also improved much faster with more frequent user feedback. While it does require an initial investment in remote testing tools and moderators, this pays dividends long-term with higher testing velocity and savings.
Types of Remote User Testing: Moderated Vs. Unmoderated Vs. Crowdsourced Testing
From my experience taking multiple startups through product-market validation, it boils down to just 3 primary types of remote user testing to focus on initially: Moderated, Unmoderated and Crowdsourced. I’ve tried all 3, and based on my experience, I’ve put together a list of pros and cons for each method.
Moderated remote user testing
Moderated remote testing enables live engagement with test participants. In these interactive sessions, a moderator guides the user through a series of planned tasks or scenarios. The moderator can share their screen to display prototypes, collaborate in real-time, and step through flows together.
Moderated tests are typically conducted over video chat so the moderator can observe the user’s body language and facial reactions. These sessions are recorded and transcribed so the team can revisit the qualitative feedback multiple times. The live interaction allows the moderator to probe deeper into emotional responses and pain points as they arise during the test. This real-time qualitative feedback combined with user behavior data makes moderated testing invaluable for understanding usability issues and gauging genuine reactions.
As a founder strapped for time, I know moderated testing may initially seem overwhelming. But don’t let that stop you from the incredibly valuable insights it provides. In my experience, the upfront effort to plan and run moderated remote tests pays back tenfold in accelerated learnings about real user needs and behaviors.
Here’s what works well for making moderated testing successful:
- Limit sessions to 60-90 minutes max. Longer and users disengage. I like 30-45 minutes best.
- Give users specific activities and scenarios that mirror real-world product use. Avoid loose, open-ended tasks.
- Have the moderator guide users through thinking aloud as they complete tasks. This surfaces how users expect things to work.
- Use the moderator to probe deeper into emotions and pain points when users get stuck or frustrated. Uncover the root issues.
- Make sure to leave 10-15 minutes post-test for open Q&A and feedback. Pose follow-up questions on key learnings.
- Record sessions to review body language and interactions multiple stakeholders may have missed live.
- Schedule debriefs right after testing to discuss results and translate findings into actionable next steps while the sessions are fresh.
Yes, running moderated tests requires planning and resources. But the effort gives me confidence I’m building the right solutions for my users. The constructive feedback I get in 45 focused minutes would take months to gather passively.
Advantages:
- While you’re conducting the session, you can make changes and build upon the learnings.
- Observe user reactions in real-time through video and guide the conversation to uncover deeper emotions and pain points as they arise.
- Probe on user feedback with follow-up questions to better understand hesitations, doubts and thought processes.
- Redirect users if they get off track to keep testing sessions focused and aligned to key goals.
- Build rapport with test participants to create a comfortable environment where they openly share uncensored feedback.
- Review session recordings multiple times to notice subtle facial expressions and cues you may have missed live.
- Uncover valuable qualitative data beyond just task success rates, like emotional sentiment and perceptions.
- Assess designs collaboratively by sharing screens and walking through workflows together with users.
- Cover more ground by rapidly pivoting session activities based on initial feedback to probe deeper.
- Make quick live adjustments to test scenarios if initial assumptions are invalidated and you need to explore new directions.
- Debrief with observers immediately after to interpret findings while session details are still fresh.
Drawbacks:
- Preparation takes time. Crafting a discussion guide and training moderators requires an upfront effort that I sometimes underestimated. Build in adequate ramp-up time for your first few tests.
- Schedule challenges. With multiple busy participants, finding a time is tougher than unmoderated tests. I try to provide wide availability windows when recruiting to maximize options.
- It needs more resources. From sourcing real users to writing scripts and moderating, it requires hands-on work. I invested in building a streamlined process to scale sessions efficiently.
- Analysis takes longer. With hours of video and transcripts to comb through, deriving insights is more intensive than quick questionnaire reviews. Take notes live to speed this up.
Unmoderated remote user testing
Unlike moderated tests, unmoderated sessions don’t require a facilitator to guide users in real time. Instead, participants independently work through predetermined tasks on their own time with instructions provided upfront.
Usually, I give testers access to a prototype link and an online guide outlining specific scenarios to complete. As they navigate the workflows, they share feedback verbally, with annotations, ratings, and through post-task questionnaires.
The testing platform records everything behind the scenes – their interactions, emotions, pain points, and ratings. I then review these session replays asynchronously to uncover insights.
The unmoderated approach makes coordination easy since no one has to connect live. I can run tests simultaneously with participants across different time zones to accelerate learning.
While I don’t get the deep interactive probing of moderated tests, the rapid pace and quantitative data from unmoderated testing allow me to validate product direction and catch major usability issues economically.
Advantages:
- Scale and Broader Reach– Tests can be distributed to a large panel of geographically dispersed users.
- Flexible Scheduling – Users can participate whenever it fits their schedule since there is no moderator. This leads to higher participation rates.
- Minimal Tester Bias – The lack of direct interaction with a moderator results in more organic and unbiased behavior.
- Time – You don’t have to conduct the sessions yourself, so you can save a lot of time and do other tasks in parallel.
- Rapid Iteration – Tests can be set up quickly and run frequently to collect feedback across iterations.
Drawbacks:
- Lack of Guidance – Without a moderator, users may get confused but have no one to help guide them.
- Limited Engagement Data – You miss out on visual cues and emotions that on-site moderators can observe. You reply only on recordings for analysis.
- No Clarification of Feedback – Since you can’t interact directly with users, their feedback can’t be further probed.
- Low Data Quality – Without moderation, some users may not take the tasks seriously.
- No personal connection – You don’t connect with users on a more personal level since they cannot see who you are.
Remote crowdsourced testing
Remote crowdsourced testing allows startups to quickly and cost-effectively gain valuable user insights. But how does it work exactly?
With crowdsourced testing, tasks and instructions are distributed to a diverse, global pool of remote test participants. Rather than relying on a small sample of localized users, startups can leverage the perspectives of people from varied demographics and backgrounds.
You’re probably wondering – how do I recruit such a large and diverse testing panel? Well, you partner with a crowdsourcing platform that maintains its own pool of pre-screened participants. This gives you instant access to thousands of remote testers from different countries and cultures.
I know what you’re thinking – if these participants are totally anonymous, how do I ensure data quality? Reputable crowdsourcing platforms rigorously vet their testers and have mechanisms to detect untrustworthy results. The platforms also allow screening based on demographics, technical aptitude, language skills, etc. This helps startups target more relevant panels.
Here’s a key question – what types of tests can I run? Crowdsourced testing is highly flexible. You can have participants review designs, clickable prototypes and live websites/apps. Tests can range from first-click tests evaluating intuition to navigational tests assessing findability.
Now, you may be wondering – how fast can I get results? One major perk of crowdsourced testing is speed. You can launch the remote usability test in hours and start seeing responses within days, if not sooner. By running tests in parallel across global time zones, data can be collected 24/7.
I’m sure you want to know what insights you actually get. Platforms allow you to see participant responses, feedback, recordings and analytics. This quant and qual data helps uncover usability issues and opportunities. You gain actionable findings to drive design and development decisions.
Advantages:
- Rapid Recruitment – You can quickly access a large, diverse pool of test participants across demographics, locations and cultures. No lengthy recruiting process is needed.
- Cost Effective – Leveraging pre-screened participants from crowdsourcing platforms is much cheaper than recruiting and incentivizing users yourself.
- Faster Results – By tapping into a global community, tests can be run 24/7 allowing you to collect data rapidly.
- Broader Perspectives – The diversity of the tester panel provides more varied feedback compared to small in-person tests.
- Flexible Testing – You can assess designs, prototypes, live sites, apps, videos and more. The testing methodology is adaptable.
Drawbacks:
- Less Personal Interaction – Since tests are remote and self-moderated, you lack in-person connections with users.
- Demographic Limitations – Available participant demographics depend on the crowdsourcing platform’s pool. Niche users may be hard to find.
- Data Reliability Concerns – Steps must be taken to detect low-quality or fraudulent responses from unchecked anonymous testers.
- Harder to Ask Follow-up Questions – Clarifying feedback can be difficult without direct communication.
When to Conduct Remote Usability Testing
Deciding when to run remote usability tests is crucial – get the timing right and you’ll uncover insights that can profoundly impact product success. But when exactly should you schedule testing? Let’s discuss some optimal moments.
I always recommend making remote testing a regular habit throughout the development process. Begin in the prototype stage with concepts and wireframes to gather initial reactions and identify major usability issues early.
As the design evolves, periodically conduct tests to gain feedback from a broad spectrum of target users. This allows you to iterate based on real user data vs assumptions.
Make sure to test again once you have a high-fidelity prototype or beta version. Dig deeper into usability pain points and identify areas for refinement before launch.
You should also consider testing after launch. Ongoing tests give insights into new user onboarding issues and changing needs. They show where your product is succeeding or lacking from an end-user perspective.
The key is to integrate testing into your regular product development cycles, not just conduct it occasionally. Quick remote sessions allow for frequent feedback without disrupting work.
Make a habit of setting specific testing goals and KPIs too – this keeps the insights actionable. For example test login flows, ease of checkout, task completion rates etc.
The Importance of Remote User Testing at Different Stages
As I mentioned earlier, it’s vital to leverage remote usability testing at all stages of your product development to drive decisions through an outside-in, user-centric lens. This increases the likelihood of product-market fit and user adoption.
Pre-Product Stage
The pre-product stage is a pivotal moment in implementing remote testing. Why? Because this is when you can gather unbiased user feedback on initial concepts without much investment.
I recommend starting tests as early as the wireframing phase. Have a diverse range of target users review draft designs and flows. The goal is to identify your ideal customers and areas of confusion.
For example, you may discover the navigation doesn’t align with user mental models. Or that certain buttons or icons are unclear. Catching these UX problems early prevents wasted dev time and resources.
Pre-product testing also gives you an early pulse on product-market fit. You can assess whether the proposed solution resonates with target audience and actually solves their needs.
In short, here is why you need to run remote usability testing at the pre-product stage:
- Identify and discover your ideal customer profiles
- Test early concepts and wireframes to understand initial perceptions.
- Identify major usability flaws and areas of confusion.
- Gather feedback to refine designs before dev investment.
Validation Stage
The validation stage is when you have a working prototype ready for initial testing. This is the time to start conducting frequent remote usability tests.
Again, the key is to not just test once, but integrate testing into your regular agile sprints. Biweekly remote sessions provide continual validation that you are headed in the right direction.
In my practice, regular remote testing during the validation stage prevents wasting resources on features users neither want nor can use. Because at this stage you are essentially validating your solution and ensuring that you are solving the right problems for the right customers. When I conducted usability testing during this stage at my current startup DeckLinks, I noticed that the feedback providers that fit our customer profile often became our early adopters and converted into paying customers later on. That’s another reason why you should do user tests more often.
Here is what you can achieve if you make remote testing with users a habit during the validation stage:
- Uncover usability issues with clickable prototypes.
- Iterate UI/UX based on user data.
- Confirm you are solving real target customer problems.
- Use this opportunity to turn feedback providers in to leads and potential paying customers
Go-to-Market Stage
The go-to-market stage is crucial for final optimization before launch. Remote testing helps polish UX to maximize adoption and confirm product-market fit across user groups before release.
I recommend rounding up a diverse mix of your target users for testing at this stage. Get feedback from each of your core buyer personas to uncover any outstanding pain points or adoption barriers.
Testing at this stage ultimately helps you deliver engaging first experiences out of the gate. And we all know that in SaaS business you rarely get a second chance at a first impression. Leaving new users frustrated from the start damages brand affinity and leads to churn.
Instead, remote testing helps you identify and eliminate pain points in critical user journeys to delight rather than disappoint. Users will share positive experiences, not rants about their struggles.
But don’t stop remote testing once you’ve launched either. Use it to keep gathering insights over time to spot emerging user needs and issues. This allows you to continually evolve the product experience to keep attracting and retaining happy customers.
Here is what you will accomplish by conducting remote user testing at the Go-to-Market Stage:
- Test the final product with broad user groups to surface adoption barriers.
- Optimize onboarding and user flows for first impressions before launch.
- Test your messaging and refine it accordingly so it resonates with your target audience.
- Figure out the most enticing price point to bring in customers and understand their decision-making process
- Set post-launch testing cadence to keep improving.
- Monitor KPIs to ensure the product meets target audience and market needs.
How to Plan a Remote User Test
Conducting a successful remote user test doesn’t happen by accident – it requires thoughtful planning. To help you get started, let me share our proven step-by-step guide.
1. Develop goals and questions
Defining your key objectives and KPIs is the first step to designing targeted test tasks. Make sure to be specific in your approach – for instance, you can evaluate checkout completion rates. Avoid taking on too much in one go and instead focus on the next key decision that will have the greatest reach and impact.
To conduct effective remote testing, it is important to create research questions that align with your goals. Brainstorm these questions with your team and create a test script that guides the user through the tasks. I’d advise to timebox every section to ensure that you cover all the necessary steps and that every user gets a chance to complete them.
2. Recruit Participant
The next step is to carefully recruit a diverse group of users that match your target audience and demographics. Try to avoid skewed samples.
You can develop screening criteria to ensure that the participants match your requirements. The criteria can be specific, such as job title, demographics, location, or behavioral screening questions. For instance, you can ask “When was the last time you traveled outside of North America?” to screen potential participants.
Recruit via social media or affordable platforms like Lightster which allows you to build your own user communities for free.
I really like that Lightster also allows you to evaluate user interest in your product. This provides more valuable insights to evaluate your product-market fit, beyond the formal test data. The platform allows you to view users who have expressed interest in your product so you can connect with them directly.
3. Craft a test scenario
Once you decide on the user testing method, you can start crafting a concise yet insightful test scenario and realistic set of tasks based on how users interact with your product.
Make sure to use best practices for remote testing setup – clear instructions, realistic prototypes, and remote observation capabilities.
4. Preparing test materials
Prepare any necessary materials for your remote usability test – interactive prototypes, Figma mockups, designs, task outlines, scripts, survey questions etc.
Here is a list of assets that will assist you in having a smooth experience:
- Prototypes – Have any wireframes, mockups, or clickable prototypes ready for users to interact with. Be sure they are realistic and representative of the actual product. Prepare backup options in case of tech issues.
- Test Tasks Outline – Write out the key tasks and scenarios you want users to attempt during the test. Prioritize tasks that align with your defined goals and KPIs.
- Facilitator Guide/Script – If you choose to run moderated user testing, then create a script for moderators to ensure consistent test facilitation across users. Include prompts for follow-up questions.
- Surveys/Questionnaires – Craft pre- and post-test surveys to capture user feedback. Use rating scales, multiple choice and open-ended questions.
- Participant Instructions – Provide clear guidelines for users on the test process and goals to set expectations. Give step-by-step guidance on required tasks.
- Recordings & Analytics – Make sure your testing platform has capabilities to record user sessions and capture interaction data.
- Incentives – Determine appropriate incentives for participation. Gift cards, cash bonuses and donations are common options.
5. Choose a remote testing platform
The right remote testing platform is essential for smooth sessions and impactful insights. But with so many options, where do you start?
Depending on the methodology you choose – moderated, unmoderated, or remote crowdsourced testing, choose the platform that supports all your needs.
You’ll also want robust participant management and screening tools to recruit the right users.
Easy test facilitation, recording and data analytics capabilities are a must-have too.
Prioritize platforms with flexible prototype integrations, customizable surveys and detailed reporting.
Don’t forget reviewer collaboration features like comment tools so your team can observe together.
Make sure participant privacy is protected as well – this is crucial for ethical testing.
Finally, look for reasonable pricing models without rigid contracts. The most expensive option might not necessarily be the best alternative for you, especially if you end up paying for features that you don’t need. You can always scale up your needs as you grow.
Top Tips for Conducting Successful Remote User Testing Sessions
Ready to run your first remote usability test? Here are my top tips for productive sessions:
- Test your setup ahead of time. Confirm that all your prototypes, audio, video and tools work seamlessly.
- Send calendar invites, or if you’re using a platform like Lightster, your sessions can automatically scheduled based on available time slots.
- When participants join, explain the goals and their role clearly. Set expectations upfront. For unmoderated remote testing, make sure you communicate all this asynchronously.
- If you choose to conduct moderated user tests, act as a facilitator, not just an observer. Ask probing questions and dig into the responses.
- Encourage thinking aloud – this provides context into pain points as they occur.
- Ask “why” and “how” questions, and avoid making statements to bias the user’s perspectives.
- Simulate a natural environment. Avoid overly scripted language, let conversations flow organically.
- Take thorough notes on verbal reactions, emotions and body language in addition to task success.
- Thank participants and ask for any final suggestions post-test. Their feedback can uncover fresh insights.
- Ask the participants if they would like to stay in touch with you or if they are interested in being a part of your product development efforts in the future. You can use platforms like Lightster to stay in contact with each person you speak to.
Common Mistakes to Avoid During Remote User Testing
When we first started conducting remote usability testing at my previous startup, we made a few mistakes that we learned from. Some of the most common mistakes we made were not setting clear expectations with participants, not having a backup plan in case of technical difficulties, and not analyzing the data thoroughly. But the biggest mistake we made was asking leading questions aimed more at confirming our assumptions rather than uncovering true user perspectives. Through these early challenges, we learned what not to do and were able to develop a more streamlined and effective process for running our remote usability testing.
- Choosing the wrong remote testing platform – Select one aligned to your methodology, analysis needs, integrations etc. Don’t just go for the cheapest option.
- Not defining clear goals and success metrics – Have specific KPIs so you get targeted, actionable insights vs vague feedback.
- Skewed participant recruitment – Ensure your testers represent real target audience. Avoid sampling bias.
- Asking leading questions – Don’t just confirm assumptions. Keep questions open-ended to uncover true user perspectives.
- Not letting conversations flow naturally – Balance structure with flexibility. Don’t over-script – keep it casual.
- Focusing only on task success – Observe behaviors and listen to feedback as much as test completions.
- Not summarizing key takeaways with users – You may miss context without wrapping up with their final thoughts.
- Failing to iterate after testing – Don’t just conduct one test. Continually test and refine over time.
Final Thoughts
Conducting insightful usability test can be challenging even in person, and more so with distributed teams. However, with proper planning and preparation, remote user testing can generate feedback that is just as valuable as feedback obtained during in-person sessions.
The difference between building a product users embrace versus one they ignore often comes down to test findings. By strategically planning your remote usability tests, selecting the right platform, preparing engaging materials, and facilitating insightful sessions – you can uncover key insights that directly fuel product success. Remember to incorporate testing at every stage of the product journey – from initial prototypes to post-launch iterations. Consistent user testing keeps you on track to build products that your users love, leading to increased engagement, loyalty, and satisfaction.
I hope this guide has demystified remote usability testing so you can harness its advantages and build the products users want and value.