Users rarely tell you the truth in UX interviews. Not because they are lying — because they do not know the truth yet. A user who says “the checkout was a bit confusing” has handed you a surface symptom. The real issue might be three, four, or seven levels deeper: an unresolved trust concern, a fear of making an irreversible mistake, a mental model built from a different product entirely.
Most UX interview questions stop at the first answer. They get polite, socially acceptable responses — “it was fine,” “a little confusing,” “I’d probably use it” — and mistake them for insight. They are not.
This guide gives you 50 battle-tested UX research interview questions organized by research category, with laddering probes for each and a clear explanation of what each question is designed to surface. Before the questions, two sections explain why most interview questions fail and how to use laddering to extract the real signal. Use this as a working toolkit — not a checklist to race through.
Why Most UX Interview Questions Fail
The failure mode is almost always the same: researchers ask questions that produce the answer they want rather than the truth participants hold.
Leading questions bias answers before participants speak. “Was the navigation confusing?” tells the participant that you think navigation might be confusing. Many will confirm it — not because it was confusing, but because you signaled that confirmation is the expected response. The better question: “Walk me through how you tried to find what you were looking for.” That puts no frame on the response.
Hypothetical questions get hypothetical answers. “Would you use a dark mode feature?” produces a yes or no that means almost nothing. People are genuinely bad at predicting their own behavior. “Tell me about the last time you were using this in a low-light situation — where were you, and what did you wish worked differently?” gives you actual behavior and actual context.
Opinion questions get opinions, not behavior. “What do you think of the dashboard?” invites evaluation. Evaluation is not evidence. “Tell me about the last time you came back to the dashboard after being away for a few days — what were you trying to figure out?” pulls behavior. Behavior reveals motivation.
Stopping at the first answer is the most common and most costly mistake. A participant says “I didn’t know where to click.” Most interviewers note it and move on. The first answer is almost always a description of surface behavior. The real finding — the one that drives product decisions — is four or five follow-up probes deeper. The first answer tells you what happened. Laddering tells you why it matters and what to do about it.
The fix is three things combined: open-ended framing, behavior-anchored questions, and deliberate laddering until you hit bedrock motivation. The question list below applies all three.
How to Use Laddering to Go 5-7 Levels Deep
Laddering is borrowed from motivational psychology and refined through decades of qualitative research practice. The premise is simple: when a participant gives you an answer, that answer almost always contains an implicit assumption or an unexplained mechanism. Asking about it — gently, non-leading — takes you one level deeper. Repeat five to seven times and you arrive at something genuinely useful.
Here is a concrete example from a checkout flow study:
Level 1 — What the participant said: “The checkout took too long.”
Follow-up: “Tell me more about that — what part specifically felt slow?”
Level 2: “I had to re-enter my card details even though I thought I’d used the site before.”
Follow-up: “What were you expecting to happen at that point?”
Level 3: “I wasn’t sure my card was saved from last time. I couldn’t remember if I’d created an account.”
Follow-up: “What was going through your mind when you realized you weren’t sure?”
Level 4: “I didn’t trust that the site had kept my information. I wasn’t sure it knew who I was.”
Follow-up: “Why was that important to you at that moment?”
Level 5: “I’ve had card details stolen before from sites I didn’t recognize. I get nervous if I can’t tell whether a site is legitimate.”
Follow-up: “What would have helped you feel more confident at that point?”
Level 6: “Some kind of signal that you were a real company — a logo I recognized, or something about security. I couldn’t find anything.”
Level 7 — The real finding: The dropout had nothing to do with form length or checkout friction. The user could not find trust signals at the moment of payment hesitation. The fix is not a shorter checkout form. It is trust credentialing — a security badge, recognized payment icons, or a brief reassurance near the payment field.
If the researcher had stopped at Level 1 and logged “checkout is too slow,” they would have optimized the wrong thing.
The probes that move you between levels:
- “Tell me more about that.”
- “Why was that important to you?”
- “What did that feel like?”
- “What were you expecting instead?”
- “Walk me through that moment again.”
- “What would have needed to be true for that to feel different?”
- “What does that mean to you?”
The goal is not to interrogate — it is to follow the participant’s own thread. Stay in their language. Use their words back to them. The moment you introduce your own framing, you are leading.
One operational advantage of AI-moderated interviews is that laddering gets applied consistently across every participant, at every level. There is no moderator fatigue, no unconscious decision to move on because the thread seems to lead somewhere inconvenient, and no variation between different moderators running the same guide. The system follows the thread every time. If you are running these questions at scale, that consistency compounds. See how User Intuition applies this in UX research at scale.
Category 1: First Use and Onboarding Questions
These questions target the critical window when users form their mental model of your product. First impressions set expectations that shape every subsequent interaction. The goal is to surface the gap between what users expected and what they encountered — including the moments they nearly gave up.
Question 1: “Walk me through the first time you used [product]. What were you trying to accomplish?”
Laddering probe: “What made you decide to try it at that particular moment?”
What it uncovers: The triggering event and the job the user hired the product to do. This establishes the context for every other question. You learn what the user was actually trying to accomplish — which is often different from what the product was designed for.
Question 2: “What did you expect to happen when you first opened it?”
Laddering probe: “Where did that expectation come from?”
What it uncovers: The mental model the user brought in from prior experience — usually a competitor, a category convention, or a referral description. Mismatches between this expectation and product reality are the source of most first-session abandonment.
Question 3: “Tell me about the moment when you first felt like you understood what the product was for.”
Laddering probe: “What changed between before that moment and after it?”
What it uncovers: The aha moment — and more importantly, what caused it. Sometimes it is a feature. Sometimes it is a piece of copy. Sometimes it is a demo video the user found accidentally. Knowing what triggers comprehension lets you move it earlier.
Question 4: “Was there a point in those first few sessions where you weren’t sure whether to keep going?”
Laddering probe: “What made you stay rather than stop?”
What it uncovers: The friction points strong enough to generate quit intent, and the countervailing forces that overcame them. Users who stayed despite early frustration often name something specific that redeemed the experience. Users who quit rarely come back to tell you why.
Question 5: “What did you wish someone had told you before you started?”
Laddering probe: “If you had known that upfront, what would you have done differently?”
What it uncovers: Documentation and onboarding gaps. Users who have been with a product for weeks or months have a clear retrospective view of what would have compressed their learning curve. These answers map directly to tooltip copy, welcome emails, and onboarding flows.
Question 6: “Describe the first time you successfully did the thing you came to do.”
Laddering probe: “What did that feel like?”
What it uncovers: The emotional reward of first success — and whether it arrived at the right moment with the right weight. If users describe first success as neutral or anticlimactic, the product is leaving activation value on the table.
Question 7: “Was there anything during setup or getting started that you almost skipped or ignored?”
Laddering probe: “What made you decide to engage with it anyway — or not?”
What it uncovers: Which onboarding elements users perceive as friction versus value. An onboarding step users universally skip is either unnecessary or positioned wrong. One they almost skipped but are glad they didn’t signals a framing problem.
Question 8: “Tell me about anything you tried during your first session that didn’t work the way you expected.”
Laddering probe: “What did you do next when that happened?”
What it uncovers: Error recovery behavior and the downstream effects of first-use friction. A feature that fails confusingly on first use often gets permanently categorized as broken — even after the user learns to use it correctly.
Question 9: “How long did it take before the product felt familiar?”
Laddering probe: “What made it start feeling familiar — was there a specific moment or did it happen gradually?”
What it uncovers: Time-to-competency and the events that drive it. Short familiarity timelines correlate with clear progressive disclosure. Long ones usually reflect poor information architecture or missing feedback signals.
Question 10: “If you were recommending this to someone else, what would you tell them to do first?”
Laddering probe: “Why that — what makes that the right starting point?”
What it uncovers: The user’s mental model of the optimal path through the product. Often significantly different from the path the product was designed to lead them through. Gaps between designed path and perceived optimal path are prioritized redesign candidates.
Category 2: Core Task and Navigation Questions
These questions explore how users accomplish the main things they come to do. They surface mental model mismatches, navigation confusion, and the workarounds users have developed — often without realizing they are workarounds at all.
Question 11: “Tell me about the last time you used [product] to do [core task]. Walk me through what you did, step by step.”
Laddering probe: “What were you looking for at each step — what were you expecting to see?”
What it uncovers: The user’s actual navigation path compared to the designed one. Step-by-step recollection surfaces the moments of hesitation users do not volunteer when asked a summary question.
Question 12: “Is there anything you do regularly in [product] that you have figured out a shortcut for?”
Laddering probe: “How did you discover that shortcut?”
What it uncovers: Workarounds and user-invented paths that reveal either missing features or navigation inefficiencies. A workaround that five users independently invented is a feature request expressed through behavior.
Question 13: “Is there anything you regularly do in [product] that still feels slower or more annoying than it should?”
Laddering probe: “What would make it feel right?”
What it uncovers: Chronic low-level friction users have adapted to but not accepted. These tasks rarely show up in support tickets because they do not break — they just grind. Naming them creates direct input for roadmap prioritization.
Question 14: “When you land on [key screen], what do you look at first?”
Laddering probe: “What are you trying to figure out when you arrive there?”
What it uncovers: Actual visual scanning behavior and the information hierarchy users care about versus the one the design imposes. When users consistently ignore the hero element in favor of something secondary, the design is misaligned with the user’s job.
Question 15: “Tell me about the last time you couldn’t find something you were looking for.”
Laddering probe: “What did you do when you couldn’t find it? What did that process feel like?”
What it uncovers: Navigation failure behavior — whether users search, browse, give up, or ask someone. The emotional response to not finding something tells you how serious the navigation problem is perceived to be.
Question 16: “Is there anything in [product] you have stopped trying to use because you could not figure it out?”
Laddering probe: “When did you make the decision to stop trying?”
What it uncovers: Features with high abandonment rates and the threshold of frustration tolerance. Users rarely report giving up on a feature in aggregate data. They just stop. Asking directly surfaces a category of loss that analytics alone cannot see.
Question 17: “How do you typically navigate to [feature] — do you have a route you always take?”
Laddering probe: “Have you ever tried a different route? What happened?”
What it uncovers: Habituated navigation paths that may bypass entire sections of the product. Users who have found a reliable path rarely explore alternatives, meaning large parts of the product can be invisible to active users.
Question 18: “Tell me about the last time you needed to find information in [product] to make a decision or answer a question.”
Laddering probe: “How confident were you in the answer you found?”
What it uncovers: Data trustworthiness and information architecture for decision support. Users who are not confident in the data they find often make the same decision they would have made anyway — the product added no value.
Question 19: “Is there anything about how [product] is organized that does not match how you think about your work?”
Laddering probe: “How would you organize it if you were designing it?”
What it uncovers: Category and taxonomy mismatches between the product’s information architecture and the user’s mental model. These mismatches are often invisible to the product team because the team built the taxonomy and then adapted to it.
Question 20: “Have you ever used [product] alongside another tool at the same time to accomplish the same task?”
Laddering probe: “What was the other tool filling in that [product] wasn’t?”
What it uncovers: Functional gaps, workflow integration points, and the specific jobs users are offloading to adjacent tools. The answer almost always names a missing feature or integration opportunity directly.
Category 3: Emotional Response and Trust Questions
These questions surface the emotional texture of the product experience — moments of delight, anxiety, confusion, and trust or its absence. Emotional response drives retention and recommendation behavior at least as much as functional performance.
Question 21: “Tell me about a moment when using [product] felt genuinely good — where you thought, this is exactly right.”
Laddering probe: “What specifically made it feel right? What was happening at that moment?”
What it uncovers: Delight moments and the conditions that produce them. Delight is almost never the product of a single feature in isolation — it is usually the result of a feature behaving consistently with what the user needed in a specific context.
Question 22: “Tell me about a moment when using [product] felt frustrating or wrong — where your experience didn’t match your expectation.”
Laddering probe: “What were you expecting instead?”
What it uncovers: Expectation failures and the emotional weight they carry. The gap between expected and actual experience is the most reliable predictor of churn intent. Participants almost always remember these moments in vivid detail.
Question 23: “Was there ever a moment when you weren’t sure whether to trust [product] with your data or your work?”
Laddering probe: “What would have made you feel more confident at that point?”
What it uncovers: Trust thresholds and the specific signals users look for. Trust concerns in B2B products almost always cluster around data security, accuracy of output, and reliability of the platform. In consumer products, they cluster around privacy and financial safety.
Question 24: “Tell me about a time when [product] surprised you — either positively or negatively.”
Laddering probe: “What made it surprising? Were you expecting something different?”
What it uncovers: Moments where the product exceeded or violated user expectations in memorable ways. Positive surprises signal delight features worth amplifying. Negative surprises signal violations of the implicit contract users formed during onboarding.
Question 25: “Have you ever felt like [product] understood what you were trying to do?”
Laddering probe: “What gave you that sense? What was the product doing at that moment?”
What it uncovers: The features and behaviors users experience as intelligent responsiveness. These are high-value retention signals — when users feel understood by a product, they develop an emotional attachment that survives functional friction.
Question 26: “Have you ever felt like [product] got in your way or didn’t understand what you needed?”
Laddering probe: “What do you think the product assumed you wanted instead?”
What it uncovers: Misalignment between the product’s model of user intent and the user’s actual intent. These moments often produce visible rage behavior — rapid clicking, form abandonment, tab closing — that analytics see but cannot explain.
Question 27: “When you make a significant action in [product] — like deleting something or submitting something important — how does that feel?”
Laddering probe: “What are you worried might go wrong?”
What it uncovers: Anxiety around irreversible actions and the adequacy of safeguards. Fear of irreversibility is one of the most common hidden drivers of user hesitation. It rarely shows up in usability tests because participants do not want to appear nervous about simple tasks.
Question 28: “Tell me about a time when [product] felt slow — not just the technical speed, but the feeling of the experience.”
Laddering probe: “What were you trying to accomplish when that feeling hit?”
What it uncovers: Perceived performance versus technical performance. Users experience slowness not just as latency but as a breakdown in their sense of control. Understanding the task context of perceived slowness reveals which flows need performance investment most urgently.
Question 29: “Is there anything about [product] that makes you feel like it was built for someone else?”
Laddering probe: “Who do you imagine it was built for?”
What it uncovers: Fit perception and identity alignment. Users who feel a product was built for someone else disengage gradually — not because specific features are broken but because the overall product signals that their needs were not the primary consideration.
Question 30: “What would have to happen for you to genuinely recommend [product] to a colleague without any hesitation?”
Laddering probe: “What is the thing currently giving you some hesitation?”
What it uncovers: The gap between current experience and recommendation-threshold experience. The hesitation is almost always specific and actionable. Users who are net promoters have already cleared this threshold; users who are neutral or detractors are stuck below it for a named reason.
Category 4: Decision and Comparison Questions
These questions probe the purchase and adoption decision — what triggered evaluation, what alternatives were considered, what tipped the outcome, and what almost prevented it. This is the research category most directly connected to win-loss analysis and positioning.
Question 31: “Tell me about what was happening when you first decided to look for a solution like [product].”
Laddering probe: “What made that the moment — had something changed?”
What it uncovers: The triggering event for the evaluation. Most B2B and many B2C purchasing decisions are triggered by a specific pain event, not a general dissatisfaction. Knowing the trigger helps you reach buyers at the right moment with the right message.
Question 32: “What else did you look at when you were evaluating your options?”
Laddering probe: “What specifically were you comparing when you put them side by side?”
What it uncovers: The competitive consideration set and the evaluation criteria users actually applied. The criteria users volunteer are almost always more specific than product-category features — they reflect the particular pain the trigger event created.
Question 33: “Was there a moment when you decided [product] was the right choice? What happened at that point?”
Laddering probe: “What would have happened if that moment hadn’t gone well?”
What it uncovers: The decisive factor — the specific thing that tipped the decision. Often this is not the primary differentiator the product markets. It may be a piece of social proof, a specific feature in a demo, or the behavior of a salesperson.
Question 34: “Was there anything that almost made you not choose [product]?”
Laddering probe: “What made you proceed anyway despite that concern?”
What it uncovers: Objections that were overcome and the arguments or signals that overcame them. This is extremely high-value positioning input — it tells you which objections buyers bring into the decision and which counter-signals are sufficient to resolve them.
Question 35: “Tell me about your experience with the product you used before [product].”
Laddering probe: “What was the thing you most wanted to leave behind?”
What it uncovers: The specific pain from the prior solution that created the switching motivation. The “leave behind” answer is almost always the primary driver of switching — and the thing your product needs to solve credibly to win the comparison.
Question 36: “If [product] ceased to exist tomorrow, what would you do?”
Laddering probe: “How would that affect the work you currently do with it?”
What it uncovers: Switching costs, dependency depth, and the real job the product is doing in the user’s workflow. Users who have no good alternative are deeply embedded; users who immediately name a replacement are functionally replaceable.
Question 37: “When you were making the decision, who else was involved?”
Laddering probe: “What were their concerns, and how did you address them?”
What it uncovers: The buying committee and the objections each member raised. In B2B especially, the economic buyer, the user, and the security/legal reviewer often have very different objections. Knowing all three helps you build the right multi-threaded deal strategy.
Question 38: “How did you justify the purchase to yourself — or to others — when you made the decision?”
Laddering probe: “What was the hardest part of that justification?”
What it uncovers: The ROI narrative users constructed and the specific value proposition they found most convincing. The hardest part of the justification almost always reveals the point of lingering uncertainty that a better proof point, case study, or guarantee could resolve.
Question 39: “Tell me about a point during your evaluation when you almost stopped the process entirely.”
Laddering probe: “What brought you back to it?”
What it uncovers: Deal-threatening friction points in the evaluation journey — often in trial onboarding, pricing discovery, or security review. Each of these is a place where the product or sales process is losing evaluators who would otherwise convert.
Question 40: “Looking back, is there anything you wish you had asked or tested during your evaluation that you didn’t?”
Laddering probe: “Why do you wish you had checked that?”
What it uncovers: Post-purchase regret signals and evaluation blind spots. Users who wish they had tested something specific during evaluation have almost always encountered a problem since purchasing that would have been revealed by that test. This is direct input for trial design and sales demo structure.
Category 5: Unmet Needs and Feature Gap Questions
These questions surface the work users cannot do, have given up trying to do, or have assembled awkward workarounds to accomplish. They are the most direct input for roadmap prioritization and product strategy.
Question 41: “Is there something you regularly wish [product] could do that it currently can’t?”
Laddering probe: “How often does that gap come up, and what do you do instead?”
What it uncovers: Feature requests grounded in real recurring need. The frequency of the gap and the workaround behavior together signal prioritization weight — a gap that comes up daily with an expensive workaround outweighs a gap that comes up monthly with a simple one.
Question 42: “Tell me about the last time you had to leave [product] and use a different tool to finish something.”
Laddering probe: “What made that frustrating — or was it fine?”
What it uncovers: Workflow breakage points and integration gaps. Users who leave for a different tool and return have accepted a productivity cost; users who leave and do not return have solved the problem elsewhere. Both patterns are worth understanding.
Question 43: “Is there a task you have given up trying to do in [product] and now handle outside it entirely?”
Laddering probe: “When did you make that decision? What made you stop trying?”**
What it uncovers: Silent churn on specific features — abandonment that never produces a support ticket or explicit feedback. These tasks are invisible in usage data because they stopped generating events. Direct questioning is the only way to surface them.
Question 44: “If you could add one thing to [product] that would make it essential to your work, what would it be?”
Laddering probe: “Tell me about a specific situation where that would have helped.”**
What it uncovers: The feature most connected to lock-in and daily essential use. The follow-up probe converts the answer from a wish into a use case — which is the information needed to evaluate whether and how to build it.
Question 45: “Tell me about the most complicated or multi-step process you regularly do that touches [product].”
Laddering probe: “Which part of that process feels the most unnecessary or the most breakable?”
What it uncovers: End-to-end workflow inefficiencies that cross multiple tools and steps. The most breakable part is almost always the integration point or manual handoff. These are the highest-value automation targets.
Question 46: “Is there information you wish [product] gave you that it currently doesn’t?”
Laddering probe: “What decision would you make differently if you had that information?”
What it uncovers: Data and reporting gaps that impair decision-making. Grounding the answer in a specific decision converts a vague “more data” request into a concrete prioritization input.
Question 47: “Have you ever had to go around [product] — doing something manually or in a spreadsheet — because the product didn’t support it?”
Laddering probe: “How long have you been doing it that way?”
What it uncovers: Long-standing workarounds that have calcified into workflow. The duration of the workaround signals both the severity of the gap and the switching friction a new feature would have to overcome to replace the established habit.
Question 48: “Tell me about a time when you needed help or support from your team to accomplish something in [product] that you felt you should be able to do yourself.”
Laddering probe: “What would have to be different for you to not need that help?”
What it uncovers: Capability gaps that create team dependencies and hidden support costs. When individual users need help with routine tasks, the product has a self-service design failure — which compounds as the user base scales.
Question 49: “Is there a category of work in your job that [product] doesn’t touch at all, that you think it could?”
Laddering probe: “What would need to change for you to consider using it there?”
What it uncovers: Adjacency opportunities — jobs the product is not positioned for but users can imagine it doing. These are expansion surface candidates, though the follow-up probe often surfaces significant requirements the current product does not meet.
Question 50: “If you were building a version of [product] from scratch for your exact situation, what would be different about it?”
Laddering probe: “What would you keep exactly the same?”
What it uncovers: Both the gap and the anchor. Knowing what users would change narrows the roadmap. Knowing what they would preserve tells you which elements have earned genuine attachment — the core to protect when making significant changes.
Common Mistakes When Running UX Interviews
Asking good questions is necessary but not sufficient. How you behave during the interview shapes the quality of answers as much as the questions themselves.
Asking “why” directly feels interrogatory. “Why did you do that?” puts participants on the defensive. It implies they made a wrong choice and need to justify it. Replace “why” with “tell me more about” or “what was happening for you at that point.” The information you get is the same; the emotional register is entirely different.
Filling silence is the most common moderator error. When a participant pauses, the instinct is to jump in with clarification or a follow-up. Do not. Silence is thinking time. The two or three seconds after an answer often produces the real answer — the thing the participant was working up to saying. Jump in and you kill it.
Nodding and affirming leads answers. Enthusiastic nodding during a participant’s response signals that you like what they are saying and want more of it. They will give you more of it. The problem is that your nods are selecting for a particular type of answer, systematically biasing your data. Practice neutral acknowledgment: “Mm-hm,” a slight nod, “I see” — enough to signal that you heard them, not enough to reward specific content.
Moving on too fast from surprising answers. When a participant says something unexpected — something that doesn’t fit your hypothesis — the instinct is to note it and continue with the guide. Unexpected answers are almost always the most valuable data in the session. Slow down. Ask the follow-up. Let the thread run. The guide is a safety net, not a script.
Confirmation bias in probing. Researchers unconsciously probe harder on answers that support their existing hypothesis and move past answers that challenge it. A discipline of probing every surprising or unexpected answer equally, regardless of direction, is the only defense against this. The best UX research finds what is true, not what you hoped was true.
How to Use These Questions with AI-Moderated Interviews
Running these questions with five to ten human-moderated participants is valuable. Running them with fifty to two hundred participants, consistently, at the same depth — that is where the signal becomes structural and reliable.
AI-moderated interviews apply these questions the same way every time, to every participant. When a participant mentions a trust concern in response to Question 23, the system pursues that thread with appropriate laddering probes before continuing. It does not get tired at participant forty. It does not decide that the thread is probably not important. Every thread gets followed.
Which questions work best at scale: All of them. The questions designed for emotional response (Category 3) benefit most from AI-moderated delivery — participants often share more candidly with an AI moderator because there is no perceived judgment. Questions in Category 4 (decision and comparison) produce particularly reliable competitive intelligence when run across 50+ participants, because individual variation averages out and genuine patterns become visible.
The output: AI-moderated interviews at scale produce auto-coded themes, pattern clusters ranked by frequency, and verbatim quotes attached to each theme. When a finding says “23 of 50 participants mentioned trust uncertainty at checkout,” you can click through to the exact quote from each of those 23 participants. The evidence is traceable.
Running studies: A study with 20 participants using a focused 8-question guide from this list, with probing, takes 48-72 hours from setup to results. From $200. That is the cost of two traditional recruiter calls, which tells you almost nothing about behavior.
For UX teams that run research to inform sprint decisions, that economics changes what is possible. You can run a study before every significant design decision instead of once a quarter. See how the methodology works at User Intuition’s UX research solution.
For planning your overall research program, see how to build a UX research plan and the complete guide to UX research.
Conclusion
The 50 questions in this guide share three properties: they are open-ended, behavior-anchored, and designed to be probed. None of them will produce useful findings if you stop at the first answer.
The pattern that runs through every category is the same: users describe what happened on the surface. Laddering reveals why it happened, what it meant to them, and what would have made it different. Surface answers produce interface tweaks. Laddering produces product strategy.
A few principles to take into each session: Silence is your friend. Follow surprising answers instead of moving past them. Ask about specific past events rather than hypothetical future ones. When a participant gives you a one-sentence answer, there are usually two or three more sentences waiting behind it — your job is to make it safe for them to say them.
If you are running these questions at scale and want consistent depth across every participant, User Intuition’s AI-moderated interview platform applies laddering systematically — 5-7 levels deep, 200+ participants, results in 48-72 hours. The platform surfaces pattern clusters, auto-coded themes, and verbatim evidence so findings are traceable to real people, not just summaries.