Informed Consent in UX Research
Informed consent is the ethical line between a casual chat and research abuse. Once you record, transcribe, or share participant data, you need explicit permission. The footgun is treating a friendly call as private when your notes permanently expose it.
Why it exists
Research abuse has caused real harm. The Nuremberg doctors trial and the Tuskegee syphilis study are historic examples where participants were deceived or not fully informed, leading to lethal outcomes and the creation of ethical codes like the Nuremberg Code and the Belmont Report. Modern UX research may be nonclinical, but it still carries risk of distress, discomfort, or pain. Consent management exists to ensure that gathering insight never comes at the cost of a participant's wellbeing.
The mental model
Think of informed consent as an ethical contract, not a bureaucratic checkbox. It is the moment a casual conversation becomes legitimate research. Both sides must exchange information honestly: the researcher explains what will happen and what the risks are, and the participant understands those terms well enough to volunteer freely. Without this mutual agreement, you are simply using someone's goodwill for your own gain.
How it works
The process has two required parts. First, the researcher informs the participant about what the study involves and what the potential consequences of participating might be. Second, the participant must fully understand those terms and voluntarily agree to take part. A consent form serves as the written documentation of this exchange. You can adapt a template to your specific study, but the core requirement is that the participant knows what they are getting into before any data is collected.
When to use it
Use informed consent whenever your interaction crosses the line from casual help into documented research. The threshold is low: the moment you transcribe quotes from a phone call, store a recording, or share a participant's information with your team, you need consent. This is especially critical when studying sensitive topics or working with vulnerable populations who may already be experiencing trauma, injury, or disadvantage.
When not to use it
A quick, informal phone call about general experiences does not require a formal consent process if you are not recording, transcribing, or sharing identifiable information. However, this exception is narrow. If there is any chance the details could be reused later in a report, presentation, or team discussion, you should obtain consent upfront rather than retroactively.
One canonical example
A researcher schedules a friendly check-in with a customer to learn about their product experience. The conversation feels casual, so the researcher does not mention it is for research. Later, the researcher transcribes direct quotes and shares them with the design team. According to ethical standards, this is misuse of data because the participant was misled into believing the chat was private and never agreed to have their words documented or distributed. A proper consent form would have clarified the purpose, the use of transcripts, and who would see the data before the call began.
Interview question
Which action transforms a casual user conversation into research that requires informed consent?
- a.Asking probing questions about the participant's personal workflow
- b.Storing a transcript or sharing details with the design teamCorrect
- c.Speaking with a participant who belongs to a vulnerable population
- d.Discussing sensitive topics like health or financial struggles
Why? this is the answer
The card states that the threshold is crossed the moment a conversation is recorded, transcribed, or shared with others. While sensitive topics or vulnerable populations raise ethical stakes, the mandatory requirement is triggered by documenting or distributing participant data.
Just read this? Test yourself on what you have been reading.
Read the original → nngroup.com
- #ux research
- #ethics
- #informed consent
- #user research
- #research operations
You just looked this up. Could you explain it out loud?
That is the part interviews actually test. Tezvyn takes questions like this one and gives you what the interviewer is really checking, the answer that lands, and the mistake that ends the conversation, in the four minutes before your next meeting.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on ux research — each one lists the topics its interview covers.
See open roles