In a moderated remote usability test, you want to see how someone completes the task independently. If the prototype will not open on their phone or screen sharing does not show their interaction, the setup becomes the problem instead. A rehearsal from invitation link to first task helps you find this before the session, rather than rebuilding the planned flow with the participant.
Separate the test device from the call device
Agree which device will run the application. Do not move a mobile task onto a large screen for convenience when mobile interaction is the research question. Sometimes the call runs on a laptop while the test runs on a phone. You then need a way to observe interaction and give instructions without changing the task.
The GOV.UK remote research guide highlights technology checks, accessible communication tools and potential reluctance to share screens. Try the setup with someone outside your usual work account.
If customers need to reschedule an appointment on their own phones, you can prepare bookings without real customer data for the test. Access must allow the change without triggering actual bookings. Another team member can check beforehand whether the starting state can be restored for the next session.
Explain the setup in the invitation
To prepare for the session, the invited person needs to know the device and browser required, any installation needed and whether screen sharing is planned. They also need to know who will observe and whether recording is involved. This makes the setup understandable and provides the basis for the corresponding organisational and privacy arrangements.
Do not put credentials in a publicly shared document. Limited test access and a clear contact for technical problems make preparation easier. Personal screen content should not accidentally become research material. Participants need to know which window to share and that they can pause sharing.
Distinguish technical trouble from task performance
If sharing fails, the participant can no longer work under the planned conditions. Clearly identifying the technical interruption helps prevent them from treating the pause as their own mistake. Recording the interruption together with any help provided keeps the following time from being interpreted as uninterrupted task performance.
During the task itself, avoid filling every silence with an explanation. A pause may be search behaviour. A neutral follow-up such as “What do you expect here?” is more informative than an instruction. Record any hints you give, so an assisted completion does not later appear independent.
Observers should collect questions separately rather than interrupting without warning. Agree a signal or private channel for the facilitator. The participant should always know who is speaking to them.
Restore a valid starting state after each session
Stopping the recording and securing the agreed notes completes the session itself. The test data also needs preparing for the next person: saved filters, selected appointments or submitted forms could otherwise change their task. Resetting restores the planned starting conditions unless the study deliberately uses different conditions.
Create a short reset checklist for the usability test: test account, saved selections, completed actions and starting link. After each session, record whether the state has been restored or the next session needs adjusting.
