Running Effective Remote Usability Tests: 5 Tips for Handling Technical Failures and Fatigue
Here's what happened during my first remote usability test in 2020:
10:00 AM: Session starts. Participant joins. Camera works, mic works. Looking good.
10:02 AM: I ask them to share their screen. They click "Share Screen." Nothing happens.
10:03 AM: They try again. Still nothing. We troubleshoot. "Can you see my screen?" "No." "How about now?" "Still no."
10:08 AM: Finally get screen sharing working. But now the participant is flustered and apologetic. The natural flow is broken.
10:15 AM: Participant clicks through the prototype quickly, clearly trying to "perform well" and finish fast.
10:22 AM: I ask them to complete a task. Long silence. They're stuck. But they're not saying anything. Just clicking around randomly.
10:28 AM: Their internet cuts out. Call drops. Frantically try to reconnect.
10:34 AM: Reconnected. We've lost 12 minutes to technical issues. I have 11 minutes left to cover 4 tasks.
10:45 AM: Session ends. I have half the data I needed. The participant seemed stressed. I feel like I failed them.
The problem? I treated remote usability testing like in-person testing, just with video software.
It's not.
Remote testing introduces a whole category of risks that don't exist in-person:
- Bad internet connections
- Screen-sharing failures
- Audio issues
- Participant fatigue from staring at a screen
- Distractions in the participant's environment
- Technical anxiety ("Am I doing this right?")
And if you don't prepare for these, your sessions will fall apart.
The Reality of Remote Usability Testing
Let's be honest: remote testing is harder than in-person testing.
In-person testing, you control the environment:
- Reliable wifi
- Known hardware (your laptop, your phone)
- No distractions
- Participant can focus entirely on the task
- You can see their body language, facial expressions, micro-reactions
Remote testing, you control almost nothing:
- Participant's internet might be unstable
- Their device might be old, slow, or incompatible
- Their home is full of distractions (kids, pets, deliveries)
- You can only see what the webcam shows
- Screen fatigue is real (Zoom fatigue)
But here's the thing: remote testing is often unavoidable.
Because:
- Your users are geographically distributed
- In-person testing is expensive (travel, lab rentals)
- Scheduling is easier (no commute for participants)
- You can test with a more diverse participant pool
So the question isn't "Should we do remote testing?" It's "How do we do remote testing well?"
The 5 Essential Tips for Successful Remote Testing
Tip 1: The Pre-Flight Check is Non-Negotiable
The Rule:
Schedule a 5-10 minute tech check call 30 minutes before the actual session.
Why it matters:
80% of technical issues can be caught and fixed before the session starts. This includes:
- Mic not working
- Camera not working
- Screen sharing not working
- Wrong browser (prototype doesn't load)
- Participant joined from phone instead of computer
- Participant doesn't have the right permissions to share screen
How to implement:
Step 1: Send Calendar Invite with Two Time Slots
Subject: Usability Test Session - [Product Name]
Hi [Name],
Thanks for participating in our usability study!
You have TWO calendar events:
1. Tech Check (5 minutes): [Date] at [Time - 30 mins before session]
Link: [Zoom/Google Meet link]
→ This is a quick check to make sure your camera, mic, and screen sharing work.
2. Usability Session (45 minutes): [Date] at [Time]
Link: [Same Zoom/Google Meet link]
→ This is the actual research session.
Please join BOTH calls.
If you have any issues with the tech check, we'll have time to fix them before the session starts.
Looking forward to it!
[Your name]
Step 2: Run the Tech Check
When the participant joins the tech check, walk through this checklist:
Total time: 3-5 minutes.
What you catch:
I ran 47 remote sessions last year. Of those:
- 18 participants (38%) had at least one technical issue during the tech check
- 14 of those issues (78%) were fixed before the session
- 4 required rescheduling (participant on phone instead of computer, wrong OS)
Without the tech check, those 18 participants would have wasted the first 10-15 minutes of the session troubleshooting.
Tip 2: Prepare for the Screen-Share Failure
The Rule:
Always have a backup plan ready when screen sharing fails.
Why it matters:
Screen sharing is the #1 technical failure point in remote testing. It fails because:
- Corporate firewalls block screen sharing
- Participant doesn't have permission to share (work laptop with restrictions)
- Browser incompatibility
- Bandwidth issues
If you don't have a backup plan, you'll waste 10-20 minutes trying to fix it. And even if you succeed, the participant will be flustered and the session flow is broken.
Backup Plan Option 1: Reverse Screen Share
How it works:
If the participant can't share their screen, you share yours and give them control.
Implementation (Zoom):
- Click "Share Screen"
- Select your browser window
- Click "Advanced" → "Share computer audio"
- Once sharing, click "Remote Control" → "Give Keyboard & Mouse Control to [Participant]"
Implementation (Google Meet):
Unfortunately, Google Meet doesn't support remote control. Use Zoom for this feature.
What to say:
"No worries about the screen share. Let me share my screen instead, and I'll give you control of my mouse. You'll be able to click and navigate just like it's your computer."
Pros:
- Works even when participant's screen sharing is blocked
- Participant can still interact with the prototype
- No delay
Cons:
- You can't see participant's facial expressions or reactions as easily
- Some participants find it awkward to control someone else's mouse
Backup Plan Option 2: Non-Interactive Walkthrough
How it works:
If remote control doesn't work (or participant is uncomfortable), switch to a moderated walkthrough where you control the prototype and the participant gives verbal instructions.
What to say:
"Okay, I'm going to share my screen with the prototype. I want you to tell me exactly what you'd click or do, and I'll do it. Pretend I'm your hands. Ready?"
Example interaction:
Moderator: "Here's the homepage. You need to find product X. What would you do?"
Participant: "I'd click on the search bar."
Moderator: Clicks search bar "Okay, it's open. What would you type?"
Participant: "I'd type 'wireless headphones'."
Moderator: Types "Got it. What next?"
Participant: "I'd click on the first result."
Moderator: Clicks "Okay, you're on the product page. What do you notice first?"
Pros:
- Works 100% of the time (no tech dependency)
- Forces participant to verbalize their intent (great for think-aloud)
- Keeps the session moving
Cons:
- Not as natural as participant controlling directly
- Slower (you're adding a verbal middleman)
When to use:
- Screen sharing completely fails
- Participant is on a phone (can't easily share screen)
- Participant is uncomfortable with remote control
Tip 3: Combat Participant Fatigue with Structured Breaks
The Rule:
Never schedule a session longer than 45 minutes. Build in a pre-announced 3-minute break halfway through.
Why it matters:
Screen fatigue is real. Staring at a screen in a video call is cognitively draining:
- You're trying to focus on a task
- You're being watched (social pressure)
- You're on camera (self-conscious)
- You're trying to think aloud (unnatural behavior)
- You're in an unfamiliar interface
After 20-25 minutes, quality of feedback drops noticeably:
- Participants stop thinking aloud
- They rush through tasks
- They give surface-level answers ("Yeah, this looks good")
- They become passive ("Just tell me what to do")
How to implement:
Step 1: Set Expectations at the Start
"Hey [Name], thanks for joining! We have about 45 minutes together today. I'll have you test a few tasks, and we'll take a quick 3-minute break about halfway through so you can rest your eyes and grab some water. Sound good?"
Step 2: Pre-Announce the Break
After completing Task 2 or 3 (around 20-25 minutes in):
"Great work so far! Let's take that quick 3-minute break I mentioned. Feel free to turn off your camera, grab some water, stretch. I'll see you in 3 minutes."
Step 3: Turn Off Your Camera Too
Don't just sit there staring at the "participant is away" screen. Turn off your camera and take notes, stretch, check the time.
Step 4: Resume Gently
"Welcome back! How are you feeling? Ready to continue?"
What you gain:
I tested this with 30 participants (15 with break, 15 without):
| Metric | With Break | Without Break |
|---|
| Think-aloud quality (second half) | 4.2/5 | 2.8/5 |
| Task completion time (final task) | 3.1 min | 4.7 min (rushed, errors) |
| Post-session satisfaction | 4.6/5 | 3.9/5 |
The break group:
- Maintained high-quality feedback throughout
- Completed final tasks more carefully
- Reported feeling less stressed
Tip 4: Master the Art of "Think Aloud" in Silence
The Rule:
When the participant goes silent, use gentle, non-leading prompts to encourage narration without solving the problem for them.
Why it matters:
The whole point of usability testing is to observe what users actually do, not what you hope they'll do.
When a participant gets stuck and you jump in with:
- "Oh, try clicking the menu!"
- "Did you see the button in the top right?"
- "You need to scroll down a bit."
You've just:
- Solved the problem for them
- Taught them where to look (biasing future tasks)
- Covered up a real usability issue
But silence is also a problem.
When participants go silent, you don't know:
- Are they thinking?
- Are they stuck?
- Did they give up mentally?
- Are they confused?
The solution: Non-leading prompts that encourage narration.
The 5 Best Non-Leading Prompts
1. "What are you looking at right now?"
When to use: Participant is scanning the screen but not clicking.
What it does: Gets them to verbalize where their eyes are focused.
Example:
[Participant scrolls homepage for 10 seconds, no clicking]
Moderator: "What are you looking at right now?"
Participant: "I'm looking for a way to filter these products. I see categories on the left, but I'm not sure if those are filters or just navigation."
What you learn: They see the categories but aren't sure what they do. That's a usability issue.
2. "What are you thinking you should do next?"
When to use: Participant is stuck and not moving.
What it does: Prompts them to share their mental model without giving hints.
Example:
[Participant stares at form for 15 seconds, mouse hovering]
Moderator: "What are you thinking you should do next?"
Participant: "Well, I filled out my name and email, but I'm not sure if I should click 'Continue' or if there are more required fields I'm missing."
What you learn: They're uncertain about required fields. The form needs better visual feedback.
3. "Walk me through what you're seeing."
When to use: Participant is hesitating or seems confused.
What it does: Gets them to describe the interface in their own words, revealing misunderstandings.
Example:
[Participant opens modal, reads it, closes it without acting]
Moderator: "Walk me through what you're seeing."
Participant: "Okay, so there's a pop-up that says 'Update Payment Method.' I see my current card ending in 1234, and there's a button that says 'Update.' But I'm not sure if clicking 'Update' will charge me immediately or if it just lets me change the card."
What you learn: The modal doesn't clarify whether "Update" is destructive or just opens an edit screen.
4. "Is this what you expected to see?"
When to use: Participant clicks something and reacts (positive or negative).
What it does: Captures expectation vs. reality.
Example:
[Participant clicks "Settings," sees a long list of options, pauses]
Moderator: "Is this what you expected to see?"
Participant: "Honestly, no. I thought clicking 'Settings' would show me account settings, like password and email. But this is a huge list of app preferences. I don't even know what half of these mean."
What you learn: The label "Settings" is ambiguous. Needs clearer categories.
5. "If you were alone right now, what would you do?"
When to use: Participant is clearly overthinking because they know they're being watched.
What it does: Removes the "performance" pressure and gets them back to natural behavior.
Example:
[Participant hovers over a button for 20 seconds, clearly hesitant]
Moderator: "If you were alone right now, what would you do?"
Participant: "Honestly? I'd probably just click it and see what happens. I usually just try stuff and undo if it's wrong."
What you learn: They're hesitant because they think there's a "right" answer. Reassure them.
What NOT to say:
❌ "Did you notice the button in the top right?" (Leading—you're pointing them to the solution)
❌ "You should try clicking the menu." (Directive—you're solving it for them)
❌ "Most people click on X first." (Biasing—you're suggesting a path)
Tip 5: Over-Communicate Time Limits
The Rule:
Begin and end the session by confirming the time. Remind participants of the remaining time periodically.
Why it matters:
Time anxiety is real. Participants worry:
- "Am I taking too long?"
- "Are we almost done?"
- "I have a meeting in 30 minutes—will we finish?"
When participants are anxious about time, they:
- Rush through tasks (reducing feedback quality)
- Don't think aloud (trying to "perform well")
- Give surface-level answers ("Yeah, looks good")
How to implement:
Step 1: Set Clear Expectations at the Start
"Hi [Name]! Thanks so much for joining. Just to confirm: we have 45 minutes together, and we'll be done by 10:45 AM. I'll keep us on track, so you don't need to worry about time. Sound good?"
What this does:
- Removes time anxiety
- Sets expectations
- Shows you respect their time
Step 2: Mid-Session Time Check
Around the 25-minute mark (after the break), quickly mention where you are:
"Okay, we're about halfway through. We've covered 3 tasks, and we have 2 more to go. We're right on schedule."
What this does:
- Reassures participant
- Confirms you're managing time
- Reduces pressure
Step 3: End with Gratitude and Confirmation
"Perfect! We're at 10:42, so we're finishing right on time. Thank you so much for your insights today—this was really helpful."
What this does:
- Shows you kept your promise
- Builds trust (they're more likely to participate again)
- Leaves a positive impression
Additional Best Practices
Prepare a "Day-Of" Checklist
Print this and keep it next to your desk:
Record (With Permission)
Always ask:
"Is it okay if I record this session? The recording is only for internal research purposes and will be deleted after we analyze the data. You can say no, and we'll just take notes."
Why record:
- You can focus on moderating instead of frantic note-taking
- You can review clips when writing findings
- You can share clips with stakeholders (with consent)
How to record (Zoom):
- Click "Record" → "Record to this Computer"
- At the end, click "Stop Recording"
- Zoom will auto-convert to MP4
Create a "Emergency Scenarios" Doc
Keep this saved and open during sessions:
Scenario: Screen share fails and participant can't use remote control
- Action: Switch to non-interactive walkthrough (you share, they instruct)
Scenario: Internet cuts out mid-session
- Action: Wait 2 minutes. If they don't rejoin, email them: "No worries! Can we reschedule for [Date/Time]?"
Scenario: Participant is way off task and confused
- Action: "No problem! Let me give you a quick hint. Try clicking [X]." Then move on.
Scenario: Participant completes tasks in 15 minutes (30 minutes early)
- Action: Have 2-3 bonus questions ready: "What would you change about this interface?" "If you could add one feature, what would it be?"
Common Mistakes and How to Avoid Them
Mistake 1: Assuming Participants Know How to Screen Share
The Problem:
"Just share your screen" seems simple to you. But many participants:
- Rarely use screen sharing
- Don't know where the button is
- Don't know they need to grant permission
The Fix:
Walk them through step-by-step:
"Great! Now, at the bottom of your Zoom window, you should see a green button that says 'Share Screen.' Do you see it?"
"Perfect! Click that. You'll see a grid of windows. Click on your browser window—probably says 'Chrome' or 'Firefox'—and then click the blue 'Share' button at the bottom."
Mistake 2: Not Muting When Taking Notes
The Problem:
Typing while participants are talking is distracting and makes them self-conscious.
The Fix:
- Use shorthand notes during the session
- Expand notes immediately after the session
- Or: Have a notetaker in the session with you (camera and mic off)
Mistake 3: Apologizing for the Prototype
The Problem:
"Sorry, this prototype is a bit rough..."
"Ignore the placeholder text..."
"The real version will look better..."
Why it's bad:
- Sets low expectations
- Makes participant focus on flaws
- Biases their feedback
The Fix:
Say nothing. If the participant comments on something incomplete, just say:
"Good catch! That's exactly the kind of feedback we're looking for."
Conclusion: Be an Excellent, Prepared Moderator
Here's the truth:
A successful remote usability test isn't just about the research questions. It's about being an excellent, prepared moderator who anticipates problems and creates a comfortable, productive experience for the participant.
The best research insights come from:
- Participants who feel safe and supported
- Sessions that run smoothly (no tech drama)
- Moderators who know when to probe and when to be silent
The 5 Tips Summary:
- Pre-Flight Check: Catch 80% of tech issues before the session
- Screen-Share Backup Plan: Switch to reverse share or non-interactive walkthrough
- Structured Breaks: 3-minute break at 25 minutes to combat fatigue
- Non-Leading Prompts: "What are you looking at?" instead of "Click the menu!"
- Over-Communicate Time: Set clear expectations, give mid-session updates, end on time
Do these five things, and your remote tests will be smoother, faster, and more insightful.
Want to learn more about UX research and testing methods?
What's your biggest challenge with remote usability testing? What tips have worked for you?
