UX and research · Intermediate · 16 min
Moderate a remote usability test
By Padding · Updated 18 Nov 2026
Any video call tool with screen sharing and recording, a notes document and a team chat channel · November 2026
You will run a usability session over a video call, with the participant sharing their screen, observers in a separate chat channel and a consented recording, and finish with that recording and a page of time-stamped notes.
On this page
A remote usability session looks like an in-person one with a camera in between. It is not. You lose the participant's hands, their face when they lean towards the screen, and the shared silence that tells you they are thinking rather than stuck. You gain a recording that is easy to make, observers who can watch from anywhere, and participants who use their own device in their own setting, which is closer to how they will use your product.
Most of what goes wrong in a remote session is logistics: the participant cannot find the share button, an observer unmutes to suggest an answer, the recording was never started, or the call drops halfway through task three and nobody knows what to do. This tutorial covers those parts. It assumes you already know how to write tasks and how to stay quiet while someone struggles; if not, read the face-to-face guide first, linked at the end.
You will prepare one session, rehearse it, run it and file the results. The steps work with any mainstream video call tool. Where a tool differs, the tutorial says what to look for rather than naming a button that may have moved.
Step 1 · Decide who shares what, and write it on one page
Before inviting anyone, settle three choices. Write each answer at the top of a new document called something like Remote session setup.
- Whose screen is shared. The usual answer is the participant's: they open the prototype link on their own machine and share their screen with you. You see real browser chrome, their zoom level and their tabs, which is useful. The alternative, you sharing your screen and giving them control, adds lag and a permission prompt most people have never seen. Use it only when the prototype cannot leave your machine.
- Which device. If the product is mobile-first, decide now whether the participant will join from a laptop and use a desktop-sized prototype, or join from their phone and share the phone screen. Phone screen sharing works in most call apps but uses battery, hides the call controls and makes think-aloud harder to hear. A practical middle path: participant on a laptop for the call, prototype opened in a narrow browser window.
- What they must not share. Ask them to close email and messaging apps, or share a single window or browser tab rather than the whole screen, if your tool offers that choice.
Add the prototype link, a backup link (a second copy of the prototype or a plain screenshot sequence in a shared folder), and your own phone number for the participant to text if the call fails.
Check it worked
Your setup document has three answered choices, two working links you have opened in a private browser window while signed out, and a phone number. If the prototype asked you to sign in when you opened it signed out, fix the sharing settings before going further.
Step 2 · Send a pre-session message that removes the first ten minutes of fumbling
Send this the day before the session, in the channel the participant answered your recruitment in (email, text or chat). Keep it short enough to read on a phone.
Hi Amaka, thanks again for joining tomorrow at 14:00 (Lagos time).
The call link: <your call link>
It lasts 45 minutes.
Please join from a laptop or desktop with a working microphone.
A quiet room helps. Headphones help more.
During the call I'll ask you to share your screen and try out an early
design in your browser. There's nothing to install and nothing to prepare.
We're testing the design, not you.
With your permission I'll record the call, as described in the consent
form you agreed to. You can say no to recording on the day and still take part.
If the link doesn't work, text me on <your number> and I'll call you back.Replace the name, time, time zone, links and number. State the time zone every time; remote participants are often in a different one from you, and a missed session from a time-zone mistake is common.
If your call tool needs an app on some devices, say so here and ask the participant to join two minutes early. Do not ask them to install a separate screen recording tool. Every extra install loses participants.
Check it worked
You have a sent message with the time zone written out, the call link, your number and a sentence saying recording is optional. The participant has replied to confirm. If they have not replied by the morning of the session, send one short reminder.
Step 3 · Set up the observer channel and its rules
Observers are useful: a developer who watches someone fail at a task fixes it faster than one who reads about it. They are also the most common cause of a spoiled remote session. An unmuted observer sighing, or a camera tile of six people watching, changes how the participant behaves.
Set up a separate text channel for the session in your team chat (a channel or group chat named after the study and date). Do not use the call tool's own chat for observers; the participant may see it.
Then decide how observers watch:
- Joined to the call, cameras off and muted. Simplest. Before the session, ask each observer to rename themselves in the call to something neutral like
Observer 1, so the participant does not see job titles. Keep it to two or three. Introduce them to the participant as "a couple of colleagues taking notes". - Watching a stream or the recording later. Some tools can stream a meeting to a view-only audience. If yours does and your organisation allows it, this keeps the participant's call to just you and them.
Post these rules at the top of the observer channel and pin them:
Observer rules for today's sessions
1. Stay muted with your camera off for the whole call.
2. Do not use the call chat. Use this channel.
3. Note what people do and say, with the time. Leave out what you think it means for now.
4. Questions for the participant go here, prefixed with Q:. The moderator
will ask the useful ones at the end.
5. Please do not message the moderator directly during the session.Choose one note-taker who is not you. Moderating and writing detailed notes at the same time over a call does not work: you will miss either the participant's words or your next prompt.
Check it worked
The observer channel exists, the rules message is pinned, and each observer has reacted to it or replied. Your setup document names the note-taker.
Step 4 · Rehearse with a colleague, including a dropped call
Book 15 minutes with a colleague in the same call tool you will use, and play the full session at speed. Your colleague joins as the participant from a different machine and network if possible (their home connection or their phone hotspot).
Run through:
- Joining and checking audio.
- Asking them to share their screen, and talking them through it without looking at their screen. This is the hardest part to describe, because their buttons may be in different places from yours. Say what the control does ("the button to share your screen, often at the bottom of the call window") rather than where it is.
- Starting the recording and confirming the recording indicator is visible.
- Task one.
- A deliberate drop: ask your colleague to leave the call without warning. Time how long it takes you to notice, check the observer channel, and get them back.
- Stopping the recording and finding where the file was saved, or where the cloud recording will appear.
Note anything that took longer than expected in your setup document.
Check it worked
You have a rehearsal recording in the place you expect to find tomorrow's. Your setup document has a line saying how long the reconnect took and what you will say to the participant when it happens. If you could not find the rehearsal recording within two minutes, write down the exact place it ended up.
Step 5 · Open the session and record consent on the recording
Join ten minutes early. Open, in this order: the call, the observer channel, your task script, the setup document and a clock you can see. Check the observers are muted and renamed.
When the participant joins, do not start recording yet. Talk for a minute about something easy (where they are joining from, whether the audio is clear). Then explain the session and ask about recording, before you press anything:
Thanks for joining. For the next 40 minutes or so I'll ask you to try out
an early design and talk me through what you're thinking as you go.
There are no right answers. If something is confusing, that's what we
need to find out.
Two colleagues are on the call with cameras off, taking notes.
You agreed in the consent form to us recording the session. Are you still
happy for me to record? It's fine to say no.If they say yes, start the recording, wait for the tool's recording notice to appear, then ask the question again so the answer is on the recording: "The recording has started. Can you confirm you're happy to be recorded?" If they say no, do not record. Ask the note-taker in the observer channel to take fuller notes, and carry on.
Now ask them to share their screen. Talk them through it in terms of what the control does, as you rehearsed. When the share appears, confirm what you see out loud: "I can see your browser with the prototype open. Can you make the window a little wider?"
Check it worked
Your recording, when you play the first two minutes back later, has the participant saying yes to recording in their own voice. Your task script has the start time written next to the participant's code (not their name).
Step 6 · Run the tasks without the cues you would have in a room
Read each task aloud and also paste it into the call chat, so the participant can reread it without asking. Then stay quiet, as you would in person.
Three things change remotely:
- Silence is ambiguous. In a room you can see whether someone is reading or stuck. On a call, ten seconds of silence could be either, or a frozen connection. After about 15 seconds of silence and no cursor movement, use a neutral prompt that does not help: "What are you looking at right now?"
- You only see the cursor. You do not see where they are looking. Ask them, before the first task, to "say what you're looking for as you look for it". Repeat that once if they go quiet across a whole task.
- Lag looks like hesitation. If the cursor jumps or freezes, say "Your screen paused for me for a moment. What did you just do?" rather than assuming they hesitated. The note-taker should mark these moments so you do not count a lag as a usability problem.
Keep an eye on the observer channel between tasks, not during them. At the end of the last task, scan for questions prefixed with Q:, pick the two most useful, and ask them in your own words without saying who asked.
Check it worked
The note-taker's notes have a time stamp and a short observed fact for each task, for example 14:12 T2: scrolled past "Choose a time" twice, said "where do I pick the day?". Moments marked as lag are labelled separately from problems.
Step 7 · Recover when something breaks
Write this list into your setup document before the session. When something happens, you follow the list instead of improvising while the participant waits.
- Participant's audio cuts out, video still works. Type in the call chat: "Your audio has dropped. Can you try leaving and rejoining?" Wait a minute. Then offer to call their phone for audio while keeping the screen share on the call.
- Participant drops out of the call. Stay in the call. Post the time in the observer channel. If they have not rejoined in two minutes, text them: "No problem, the link is the same, rejoin when you can." After five minutes, call them.
- Screen share fails or shows a black screen. Ask them to stop sharing and share a single browser tab or window instead of the whole screen. If that fails, switch to your backup: you share the prototype and they tell you where to click. Note the switch.
- Prototype will not load. Send the backup link in the call chat. If that also fails, run the remaining tasks as a walkthrough of the screenshot sequence and say so in the notes.
- Recording stops or was never started. Restart it, ask the consent question again on the recording, and ask the note-taker to mark the gap.
- An observer unmutes or speaks. Make light of it to the participant ("Sorry, that was a colleague"). Remind observers in the channel.
When a participant rejoins after a drop, do not start again from the beginning. Say where you were ("You were on the second task, choosing a time") and let them carry on. A drop in the middle of a task changes their attempt, so mark that task as interrupted when you analyse it.
Check it worked
The list is in your setup document. After the session, every interruption in the notes has a time and a matching action from the list, and any interrupted task is labelled as such.
Step 8 · Close the call, file the recording and debrief
Stop the recording before small talk at the end, then thank the participant and tell them when and how any incentive will arrive. End the call for everyone.
Within the next 15 minutes, while memory is fresh:
- Find the recording. Local recordings often appear only after the call ends and the file finishes converting. Cloud recordings can take longer. Do not close the call app until you have seen the file or the message saying it is processing.
- Move it to the agreed place. Rename it with the study, the participant code and the date, for example
booking-test_P03_2026-11-20, and move it into the access-controlled research folder named in your consent form. Delete any copy left in a downloads folder or on the desktop. - Debrief for ten minutes. Get the note-taker and observers on a short call or in the observer channel. Each person writes the three things they saw that mattered most. Do not try to agree on causes or fixes yet; that comes after all sessions.
- Write down what to change for the next session. A task that was misread, a share step that took too long, an observer who needs reminding. Change one thing at most between sessions, so results stay comparable.
Check it worked
You have a recording file named by participant code and date in the research folder, and none left anywhere else. The observer channel has a debrief message listing each person's top three observations. Your setup document has a short "Change for next session" line, even if it says "none".
Next steps
Repeat the session with the rest of your participants, keeping the setup document and recovery list the same. Then turn the notes from all sessions into a list of problems and how many people hit each.
- For the moderator's job inside the session (think-aloud, not helping, taking structured notes), read /tutorials/run-a-five-person-usability-test.
- To test with more people at lower cost when you do not need to ask follow-up questions, read /tutorials/run-an-unmoderated-usability-test.
- To write the consent form your recording depends on and decide how long recordings are kept, read /tutorials/get-informed-consent-for-user-research.
- To fill your sessions and handle no-shows, read /tutorials/recruit-participants-for-user-research.
Part of these paths
Related tutorials
- Run a five-person usability testYou will run five in-person think-aloud sessions on a live product in one day, hold back from helping when people struggle, and finish with a list of observed problems showing how many of the five hit each one.
- Run an unmoderated usability testYou will have results from at least ten unmoderated sessions on one prototype, cleaned of low-quality sessions, with a short write-up that says what the data shows and what it cannot.
- Get informed consent and store research data safelyYou will have a plain-language consent form for one study and a data-handling checklist that says what you record, where it lives, who can see it and when it is deleted.
Need this done for you?
Padding does this work for growing companies, from the first diagnosis to a system that keeps working.
Get new tutorials