How to Write an Interview Protocol That Gets Rich Data

The quality of your qualitative findings depends heavily on the quality of your data, and the quality of your data depends on the questions you ask. A well-designed interview protocol does not just list questions. It creates a conversation structure that invites participants to share detailed, reflective, and honest accounts of their experiences. Here is how to build one.

What Is an Interview Protocol?

An interview protocol is more than a list of questions. It is a complete guide for conducting a semi-structured interview, typically including:

• An opening script (introduction, consent reminder, rapport building)
• The main interview questions, organized by topic
• Probes and follow-up prompts for each question
• Transition language between topics
• A closing script (final thoughts, next steps, gratitude)

The protocol serves as your roadmap during the interview. It keeps you on track without making the conversation feel rigid or scripted.

Principles of Good Interview Questions

Ask Open-Ended Questions

This seems obvious, but many graduate students still write questions that can be answered with yes or no. Compare these two questions:

• "Did you feel supported by your advisor?" (closed)
• "Tell me about your relationship with your advisor." (open)

The open version invites a story. The closed version invites a single word.

Start Broad, Then Narrow

Begin each topic area with a grand-tour question that lets the participant define the territory. Then use follow-up questions to explore specific aspects.

• Grand tour: "Walk me through a typical day in your program."
• Follow-up: "You mentioned feeling rushed between classes and work. Can you tell me more about that?"

Use Descriptive and Experience-Based Language

Questions that ask participants to describe specific experiences produce richer data than questions that ask them to generalize. Compare:

• "What challenges do you face?" (general)
• "Think of a time when you felt really challenged in your program. What happened?" (specific)

The specific version anchors the participant in a concrete memory, which leads to detailed, vivid data.

Avoid Leading Questions

A leading question contains an assumption that pushes the participant toward a particular answer:

• "How frustrating is it to deal with bureaucracy?" (assumes it is frustrating)
• "What has your experience been with administrative processes?" (neutral)

Leading questions compromise your data because you cannot be sure whether the participant genuinely holds that view or is simply agreeing with your framing.

Structuring Your Protocol

Opening (5 minutes)

Start with easy, non-threatening questions that build rapport. These might ask about the participant's background, how long they have been in their program, or what drew them to their field. The goal is to help the participant feel comfortable talking.

Main Questions (40-50 minutes)

Organize your main questions into three to five topic areas that align with your research questions. Within each area, begin with the broadest question and follow with more specific ones. Here is an example structure for a study on doctoral student experiences:

Topic 1: Program entry

• "Tell me about how you decided to pursue a doctoral degree."
• Probe: "Who or what influenced that decision?"
• Probe: "What were your expectations going in?"

Topic 2: Academic relationships

• "Describe your relationships with faculty in your program."
• Probe: "Can you give me an example of a particularly positive interaction?"
• Probe: "What about a time when a relationship felt difficult?"

Topic 3: Challenges and coping

• "What has been the hardest part of your doctoral experience so far?"
• Probe: "How did you handle that?"
• Probe: "Who did you turn to for support?"

Closing (5-10 minutes)

End with a question that gives the participant the final word:

"Is there anything else about your experience that we haven't covered that you think is important for me to understand?"

This question often produces some of the richest data in the entire interview, because participants share what matters most to them rather than responding to your agenda.

Writing Effective Probes

Probes are the secret weapon of skilled qualitative interviewers. They are short follow-up prompts that encourage the participant to go deeper. Good probes include:

• "Tell me more about that."
• "What was that like for you?"
• "Can you give me an example?"
• "What happened next?"
• "How did that make you feel?"
• "Why do you think that is?"

Write two or three probes under each main question in your protocol. You will not use all of them in every interview, but having them ready prevents you from going blank when a participant gives a short answer.

Piloting Your Protocol

Never use your protocol for the first time in an actual data collection interview. Conduct at least one pilot interview with someone similar to your target participants. Pay attention to:

• Question clarity: Did the participant understand what you were asking?
• Question order: Did the flow feel natural, or were there awkward transitions?
• Timing: Did you have enough time for all your questions?
• Richness: Did the questions elicit detailed, relevant responses?

Revise your protocol based on the pilot, then pilot again if you made significant changes.

Common Protocol Mistakes

• Too many questions. A sixty-minute interview can usually accommodate eight to twelve main questions with probes. More than that, and you will rush through without getting depth.
• Jargon. Write questions in language your participants actually use, not academic terminology.
• Double-barreled questions. "How do you balance work and family while in school?" asks about two things at once. Split it.
• Assuming shared understanding. If your study is about "mentorship," do not assume participants define that word the same way you do. Ask them what mentorship means to them.

A strong interview protocol is not about asking clever questions. It is about creating space for participants to tell their stories in their own words. The more carefully you design that space, the richer your data will be.