Recording a UX research or usability testing session
Recording is standard practice in UX research — you genuinely need the data. It also measurably changes participant behavior the moment they know a camera’s rolling, and good research practice accounts for that rather than ignoring it.
Consent needs to be genuine, not just a signed form
Beyond the legal requirement of informed consent (which any real UX research practice already has covered), participants who feel rushed through consent, or unclear on what’s actually being recorded and why, tend to behave more guardedly during the actual session. Taking a genuine minute to explain what’s recorded, how it’ll be used, and that it’s about evaluating the product rather than the participant measurably improves the naturalness of what follows.
Screen recording alone vs. screen plus face
Recording just the participant’s screen (their clicks, their navigation) is less invasive than adding a webcam feed of their face, and for many usability questions, the screen recording alone answers what you actually need — where do they get confused, what do they click, how long do specific steps take. Add facial recording specifically when you need to understand emotional reaction, not as a default for every session.
Explain that you’re testing the product, not them, repeatedly if needed
Participants who feel they’re being evaluated personally, rather than helping evaluate a product, tend to apologize excessively, second-guess their actions, or perform confidence rather than behaving naturally — genuinely undermining the research’s validity. Restating “there are no wrong answers here, we’re testing the design” at natural points, not just once at the start, helps counteract this as sessions go on.
Think-aloud narration needs modeling, not just instruction
Asking a participant to “think aloud” as they navigate rarely works well from instruction alone — most people go quiet the moment they’re concentrating, precisely when their narration would be most valuable. Briefly modeling what think-aloud sounds like yourself before the session starts (“I’m looking at this button, I’m not sure if it does what I need…”) gives participants an actual template to follow, not just an abstract instruction.
What to do with recordings afterward
Establish and communicate a clear retention and access policy for research recordings before the session, not as an afterthought — participants who know specifically who will see the recording and for how long it’s kept tend to trust the process more, which itself improves the quality of what you capture.
Frequently asked questions
Does recording change how UX research participants behave?
Yes, measurably — genuine, clear consent and repeatedly reassuring participants that the product (not them) is being evaluated meaningfully reduces this effect, though it doesn’t eliminate it entirely.
Should UX research sessions always include facial/webcam recording?
Not by default — screen recording alone answers most usability questions. Add facial recording specifically when emotional reaction is genuinely relevant to your research question.
How do I get participants to actually think aloud during a session?
Model it briefly yourself before the session starts, rather than just instructing them to do it — most people need an example of what think-aloud narration actually sounds like.
Related reading: A recorded product demo has one job · Recording a bug report your dev team will actually use · Recording a Zoom call — what’s legal and what’s built in