Start with a clear invitation
Consent begins before the interview. An invitation should say who is conducting the research, what the conversation is about, how long it is expected to take, and whether it will be remote or in person. If the interview involves a product demonstration, screen sharing, or a follow-up conversation, mention that too. People can make a more informed choice when the invitation describes what participation actually involves.
Avoid promising that an interview is anonymous if you will know the participant’s name or contact details. Instead, explain which details you need and why. For example, you may need an email address to arrange the call but not to analyze the responses. If an incentive is offered, describe it plainly and avoid making participants feel that they must answer every question to receive it. Make it easy to decline without having to give a reason.
Explain consent as a conversation
At the start of the interview, briefly restate its purpose and how the information will be used. Explain who may see the notes or recordings, whether comments might appear in a report, and whether identifying details will be removed. Use everyday language rather than asking someone to agree to a vague statement about “research purposes.” Allow time for questions before beginning.
Make clear that participation is voluntary: the person can skip a question, pause, or end the conversation. If you want to record, ask for permission separately rather than treating agreement to the interview as agreement to recording. Have a workable alternative, such as taking notes, for someone who wants to talk but does not want to be recorded. If the scope changes during the call—for instance, you decide to ask the participant to show an account screen—explain the change and ask again before proceeding.
Collect less and ask carefully
Good interview questions focus on experiences and decisions, not on collecting every available detail about a person. Before the session, review the guide and ask whether each question helps answer the research question. A broad prompt such as “Walk me through how you chose a service” may reveal more useful context than a request for an exact income, account balance, or medical history. If sensitive information is not needed, do not request it.
Interviews can still surface private details unexpectedly. A participant might name a coworker, describe a family situation, or show a notification while sharing a screen. The interviewer can steer back to the relevant experience without probing further. When taking notes, capture the insight rather than unnecessary identifying detail. For example, “needed approval from a colleague” may be sufficient without recording that colleague’s name.
Set boundaries for notes, recordings, and sharing
Before collecting anything, decide where interview materials will be stored, who needs access, and when the materials will be reviewed for deletion. Keep contact information separate from analysis notes when practical. Use clear file names or participant codes so the team can work without repeatedly exposing names. Limit access to people working on the research rather than sharing raw recordings widely for convenience.
Reports usually need patterns and illustrative examples, not a complete transcript of someone’s private life. Review quotations and screenshots for details that could identify a participant, including combinations of seemingly ordinary facts such as a job role, location, and unusual experience. Removing a name alone may not be enough. If you plan to share a recognizable quote, voice clip, or image beyond the interview team, explain that intended use and seek specific permission. Do not assume permission to record also covers publication.
Close the loop with participants and the team
At the end of the conversation, thank the participant and remind them how to contact the team with a question about their contribution. If you have told participants they can request a correction or withdrawal, make sure the team has a realistic process for handling those requests and has explained any limits. Do not offer control over material that has already been irreversibly combined into a report if you cannot provide it.
Privacy practices should also be part of the research debrief. Check that notes reflect what participants meant, remove incidental personal details, and confirm that recordings are kept only as long as they serve a defined purpose. Requirements can vary by location, organization, and type of information, so a team may need to check its applicable policies or seek qualified guidance. The everyday principle is simpler: tell people what will happen, ask before changing course, and handle what they share with care.
