Turn a broad research question into neutral questions people can answer, with examples and useful follow-up probes.
Qualitative questions explore how people experience, understand or explain something. A research question defines what the study seeks to understand; a question asked of a participant invites an account that can help answer it. These are related but not interchangeable.
“How do new employees experience onboarding?” is a research question. “Tell me about your first week” is a participant question. Asking the research question word for word may produce an abstract answer instead of a useful account.
| Research question | Participant question | Possible probe |
|---|---|---|
| How do people navigate access? | What happened when you first tried to use the service? | What did you do next? |
| What supports learning transfer? | Tell me about a time you used the skill. | What made that possible? |
| How do partners experience reporting? | Walk me through your last reporting cycle. | Where did you need clarification? |
The guide does not need to anticipate every answer. It needs enough structure to address the purpose while leaving room for experiences that challenge your expectations.
| Purpose | Example questions |
|---|---|
| Experience | What was that experience like? Which part stands out, and why? |
| Process | How did you decide what to do? What happened after that? |
| Meaning | What does a good result mean to you? How would you recognize it? |
| Barriers | What made the next step difficult? What support was missing? |
| Change | What, if anything, changed? What else was happening then? |
| Variation | When was the experience different? Who might see it another way? |
These are examples, not a validated instrument. For a larger bank organized by application, see 100 open-ended questions.
A question such as “Why was our training helpful?” assumes it was helpful. Ask “What was useful, if anything?” and allow criticism. “How was communication and scheduling?” combines two subjects; separate them when each matters.
Avoid jargon, unnecessary abstraction and questions that ask people to diagnose an entire organization. Ask about something they experienced. A neutral request for an example often produces better evidence than a request for a general judgment.
A probe should help the person explain their meaning. Do not offer an answer and ask them to confirm it. Give people permission to skip a question or say they do not remember. Silence does not need to be filled immediately.
Try the guide with a small number of suitable people before full collection. Check which questions are misunderstood, repetitive or too difficult to answer. Revise wording and sequence while preserving the study purpose.
Begin with accessible experience questions before moving to sensitive or reflective topics. Explain recording, use and confidentiality clearly. The guide should fit the time available and the person’s circumstances.
Before collection, write what each question is intended to illuminate. During analysis, keep unexpected themes and evidence that does not fit the initial categories. A study designed only to confirm a product benefit will miss other explanations.
Keep the guide version, interview context and source excerpts with the analysis. AI-assisted coding can help organize material, but a reviewer should check that themes reflect what people actually said. Continue to interview data collection methods.
No, but those openings often invite explanation. The wording and purpose matter more than a fixed formula.
Yes. Consider whether it sounds accusatory; “What led to that?” can be easier to answer in some contexts.
Not necessarily. Keep the core topics consistent while using probes to clarify each person’s account.
It can examine an explanation, but the design should allow evidence to challenge it rather than force answers into a predetermined conclusion.
