02.03Instrument DesignAvailable

Interview Question Development

Write interview questions and probes that return real accounts: episode questions, laddering, critical incidents, and how to ask why without asking why.

Free. Works on Claude, ChatGPT, Gemini or any assistant that accepts a skill file.

What this skill does

The method, encoded.

A guide can have the right sections, the right order and the right length and still produce nothing usable, because the failure happens at the sentence. Most weak interview questions ask people to do things people cannot do: predict their own behaviour, explain their own motivation, average their own conduct into a general tendency, rank options they have never compared. Participants answer anyway, fluently and confidently, and the damage is that the failure is invisible in the transcript. A rationalisation reads exactly like an account.

This skill works at the level of craft rather than structure. It covers open questions that do not lead, the difference between asking about behaviour and asking about reasons, why direct "why" questions return the most available explanation and what to ask instead, laddering and where to stop it, critical incident technique, grand tour questions, concrete episodes versus general tendencies, asking about socially undesirable behaviour, asking about the past without inviting reconstruction, and the questions that never work.

It sits inside a discussion guide rather than replacing one, and produces a question set with probe ladders, a rewrite log naming the defect in every question changed, and notes on the residual bias that could not be designed out.

Best used for

  • Turning a section purpose into the question that opens it
  • Replacing why questions with sequence, consequence and contrast routes
  • Designing critical incident and episode reconstruction sequences
  • Laddering from a stated attribute without inventing the value beneath it
  • Asking about sensitive or socially undesirable behaviour
  • Asking about the past without inviting reconstruction
  • Removing prediction, self-averaging and introspection questions from a draft

Typical inputs

What you give it.

Section purposes and exit conditions from the discussion guide, The unit of evidence each section must produce, Recruitment framing and what participants have already been told, Sequence position, including whether the question sits above the exposure boundary, Participant vocabulary from prior transcripts, verbatims or records (optional), Analysis approach and intended coded unit (optional), Mode, moderator experience level and language list (optional)

Typical outputs

What you get back.

Question set by section, with probe classes and worked examples, Question specification table naming evidence unit and mental act, Rewrite log for every supplied question changed, with the defect named, Removed-questions list with reinstate conditions, Sensitive-question notes with residual bias direction, Cognitive testing notes, Consolidated review points

Method coverage

What the skill works through.

  1. Why fluent answers are not good answers
  2. The mental act a question demands, and which acts people can perform
  3. Concrete episodes versus general tendencies
  4. Asking why without asking why: sequence, consequence and contrast
  5. Critical incident technique, step by step
  6. Laddering from attribute to consequence to value, and where to stop
  7. Grand tour and mini tour questions
  8. Writing the stem: one idea, participant vocabulary, no candidate answers
  9. Asking about sensitive and socially undesirable behaviour
  10. Asking about the past without inviting reconstruction
  11. The questions that never work
  12. Writing the probe ladder, including the evidential and negative-case probe
  13. Testing a question before fieldwork
  14. Where question craft ends and guide structure begins

Download

Free skill. One file.

Enter your email once. Every skill you download after that takes a single click.

How to install

Add the skill file and the five kernel protocols to a Claude Project, a ChatGPT Project, a Gemini Gem, or paste them at the top of any assistant conversation. Then give it your real research material, not a description of it.

Download skill

Questions

Common questions.

How do I ask "why" in an interview without getting a rationalised answer?

Route around it. Direct "why" questions return the most available, most socially acceptable explanation, produced on the spot by someone who has usually never been asked before, and it arrives in a form indistinguishable from insight. Use sequence instead ("what happened just before that?", "and then what?"), consequence ("what did that mean for you?"), and contrast anchored to a real event ("how was that different from the time before?", "what would have had to be different?"). If a direct why is used at all, use it last, on an episode already reconstructed, and treat the answer as a claim to weigh against the sequence rather than as the finding.

Why is "tell me about the last time" better than "what do you usually do"?

Three reasons. The participant is retrieving rather than composing, so the answer is a memory rather than an on-the-spot summary weighted to whatever is most recent and most vivid. The answer contains detail nobody thought to ask for, which is where unexpected findings come from. And an episode is an analysable unit, whereas a generalisation is the participant's own analysis, performed badly, with the working thrown away. The exception is when the participant's summary judgement is genuinely the object of study, such as their stated position on an issue or their sense of a relationship over time.

What questions should never be asked in a qualitative interview?

Four families. Anything asking a participant to predict their own future behaviour, because stated intention is systematically generous. Anything asking them to explain their own unconscious motivation, because that is an analyst's inference from evidence, not something a person has access to. Anything asking them to rank or rate things they have never compared, because it manufactures a preference at the moment of asking. And anything asking them to count a routine, low-salience behaviour over a long window, because the answer is rounded to salient numbers and anchored to whatever the question suggests.

What is laddering and when does it stop being evidence?

Laddering climbs from a stated attribute to the consequence it delivers and the value beneath it, one rung at a time, using the participant's own words at each step. It stops being evidence at the rung where the answers become abstract virtues that could apply to anyone: "I want value", "I want the best for my family". Everything above that point is the participant supplying the culturally expected top of the ladder. Two or three rungs is usually the honest limit, and the output is one person's articulated account of a preference, not proof of a hidden hierarchy.

What is critical incident technique?

A protocol for reaching what actually happens at a moment that matters. Define the incident class precisely, have the participant select a specific instance and anchor it in time and place, elicit the sequence in the order it happened without interrupting, walk it again for detail, elicit the outcome and its consequence, and only then ask what made the difference. Two or three incidents per interview is realistic; budget 8 to 12 minutes each. It produces behaviour-level detail no attitude question reaches, and its cost is time.

How do you ask about embarrassing or socially undesirable behaviour?

Design the permission into the question rather than retrofitting an assurance. Normalise first ("some people manage to keep on top of this and plenty of people do not"). Load the question toward the undesirable side, so the presupposition is easier to correct than to confess. Ask about the behaviour, not the identity, because people will describe missing three payments and will not accept being someone who misses payments. Where the direct route is closed, ask in the third person about what people they know say, and label the answer at analysis as evidence about the norm rather than about the individual. Never pair a confidentiality assurance with a question that makes the honest answer sound bad; the assurance signals that the topic is shameful.

How do you ask about something that happened months ago?

Anchor to an event rather than a period: "the last time" beats "in the past six months", and a landmark ("since you moved", "since the baby") beats a calendar date. Ask what happened before you ask what they thought, because an opinion given first gets retrofitted into the account. And never ask someone to explain their past self's reasoning as though they had access to it. Ask what they knew at the time, what options were in front of them and what they did, and let the analyst reconstruct the decision.

What is a grand tour question?

A question that asks the participant to walk you through a domain they know and you do not: "talk me through what happens on a normal Tuesday from when you get in". It works because it hands the expertise to the participant, sets the expected answer length at several minutes rather than a sentence, and surfaces vocabulary, sequence and actors no direct question would have thought to ask about. Anchor it in a time and a place, or the participant will not know where to start, and follow it with mini tours into the parts that matter.

How can I tell whether an interview question is any good before I use it?

Three tests. Write down the three answers you expect: if you can predict them, the question is closed, leading, or collecting culture rather than this person's life. Ask whether someone with nothing to say could still answer it fluently: if yes, it will not discriminate. Then cognitively test it on two or three people from the target population, asking them afterwards what they thought the question meant and how they arrived at their answer. That last test takes under an hour and catches ambiguous terms, unanswerable recall windows and imported vocabulary that no amount of desk redrafting will find.

Can AI write interview questions?

It can draft them quickly, and its characteristic failures are specific. Generated question sets are symmetric, with the same shapes in every section and nothing removed. They are frequently full of well-worded "why do you feel that way" questions, which read as good practice and are the core defect, because the problem is the mental act being demanded rather than the phrasing. They invent category vocabulary that was never supplied. And the most dangerous habit is generating example answers or "what participants are likely to say" alongside the questions, which travel into analysis documents and become indistinguishable from real evidence. Require a rewrite log naming the defect in every question changed, and never accept anticipated answers in a design document.

Research where people already are.
Analyse it where you already work.

Yazi helps researchers conduct surveys, AI interviews and longitudinal research directly through WhatsApp.

New Report on SA Gambling Impact
Check It Out