Table of Contents
“Why?” sounds like the deepest question in research.
Why did you choose this product?
Why did you stop using it?
Why did you abandon the checkout?
Why did you prefer that competitor?
It feels direct. It sounds thoughtful. It seems like the shortest path to motivation.
But in many interviews, “why?” is the wrong first question.
Not because it is a bad question. Because it is often asked too early.
When you ask someone “why?” before you understand what actually happened, you invite them to explain, justify, summarize, or rationalize. You get the story they have constructed after the fact, not the moment as they experienced it.
Good research usually needs to slow down before it asks people to explain themselves.
It needs the moment first.
Most of us are not perfectly aware of our own motivations.
We can describe what we saw, what we clicked, what confused us, what we expected, who else was involved, and what happened next.
But when asked why we did something, we often reach for the cleanest explanation available.
“I guess it was too expensive.”
“I just didn’t trust it.”
“It felt complicated.”
“I didn’t really need it.”
“The timing wasn’t right.”
These answers may be true. But they are often incomplete.
“Too expensive” could mean:
If you ask “why?” too early, you may accept the first explanation as the reason.
But if you first reconstruct the moment, you can see what the explanation is attached to.
Imagine a user abandoned a signup flow.
You ask:
Why did you stop signing up?
They answer:
I think it just felt like too much work.
That sounds useful. But it is still vague.
What felt like work?
Was it the number of steps?
The information requested?
The uncertainty about what would happen next?
The fear of being charged?
The lack of confidence that the product was worth it?
Now compare that to asking:
Walk me through what happened when you started signing up.
Then:
What were you expecting to happen next?
Then:
Where did you pause?
Then:
What were you thinking at that point?
Only after that does “why?” become useful.
Because now you are not asking for a generic explanation. You are asking about a specific moment, with context.
The answer becomes grounded.
A good interview often moves in this order:
The “why” comes later.
This order matters because it protects you from shallow certainty.
When a participant says, “I didn’t trust it,” the tempting follow-up is:
Why didn’t you trust it?
That can work. But often a stronger path is:
What did you see that made you feel unsure?
or:
Was there a specific moment where trust became a concern?
or:
What would you normally expect to see in that situation?
These questions do not ask the participant to generate a theory. They ask them to return to the experience.
That is where the useful detail usually lives.
Weak first question:
Why did you abandon checkout?
Better first questions:
What were you trying to buy?
What did you expect the checkout step to show?
What made you pause?
What did you do after leaving?
Then:
Looking back, why do you think that stopped you from continuing?
Weak first question:
Why did you switch to another tool?
Better first questions:
What was happening in your work around the time you started looking?
What was the first thing that made you consider switching?
What alternatives did you compare?
What did the other tool seem to solve better?
Then:
Why did that difference matter enough to switch?
Weak first question:
Why don’t you use this feature?
Better first questions:
When was the last time this feature might have been relevant?
What did you do instead?
Did you notice the feature at the time?
What did you assume it was for?
Then:
Why do you think it did not become part of your workflow?
Weak first question:
Why does the price feel too high?
Better first questions:
What were you comparing the price to?
What did you think was included?
Was there anything unclear about the plan?
At what point did the price start to feel like a concern?
Then:
Why did that concern matter in your decision?
The goal is not to remove “why” from research.
The goal is to earn it.
“Why?” becomes powerful when it is attached to a concrete behavior, moment, tradeoff, or emotional reaction.
It is weak when it floats above the experience.
A vague “why” gives you a vague answer.
A grounded “why” can reveal motivation.
The difference is not the word itself. It is the setup.
Human researchers often sense when an answer is too abstract. They can pause, redirect, or ask the participant to go back to the moment.
AI interviewers need to learn the same discipline.
The challenge is not simply asking more follow-up questions. It is knowing what kind of follow-up is needed.
Sometimes the right follow-up is not:
Why?
It is:
Can you walk me through what happened?
or:
What did you notice first?
or:
What were you expecting instead?
or:
What did you do next?
At Usercall, this is one of the things we think a lot about when building AI-moderated interviews. The goal is not to make AI ask endless questions. It is to make it better at helping people reconstruct real experiences, so the insights are grounded in what actually happened.
Before asking “why,” ask yourself:
Do I understand the moment well enough for the answer to mean something?
If not, start with the experience.
Ask what happened.
Ask what they saw.
Ask what they expected.
Ask what changed.
Ask what they did next.
Then ask why.
Because the best research does not start by asking people to explain themselves.
It starts by helping them remember the moment clearly enough that their explanation becomes useful.
