Why Users Say One Thing and Do Another
What people intend to do is not always what they actually do
User Research, Behaviour, Decision-Making
The most dangerous thing in research is believing the answer too quickly.
Ask someone, “Would you use this feature?”
They might say yes.
Ask, “Would you pay for it?”
They might say yes again.
But put the feature in front of them in a real situation — and their behaviour can look completely different.
This is known as the intention–behaviour gap: the difference between what people say they intend to do and what they actually do. Research has repeatedly found that intentions are useful, but they don't fully predict subsequent behaviour.
So what should researchers do?
Stop asking only about the future. Start studying the present.
Instead of:
“Would you use this?”
Try:
“Show me how you solve this today.”
Instead of:
“Which option would you choose?”
Try:
“Which one did you choose the last time this happened?”
Instead of:
“Would you pay ₹500 for this?”
Look at what people currently spend, avoid, substitute, or compromise on.
The difference seems small. The quality of the insight isn't.
A simple example
Imagine you're designing a learning app.
In an interview, a student says:
“I would definitely study for 30 minutes every day.”
So the product team builds:
Daily 30-minute learning streak → reminders → progress tracking.
But diary research shows something else.
The student intends to study every evening.
When evening arrives, they're commuting, tired, or have only 8 minutes available.
The problem wasn't motivation.
The product was designed around the intention instead of the behaviour.
Research on the intention–behaviour gap suggests that time, effort, resources, context, habits and situational cues can all affect whether intentions actually become actions.
What this changes in UX research
Good research isn't just about getting better answers.
It's about getting closer to reality.
Use interviews to understand why.
Use observation to understand what.
Use usability testing to understand how the product performs.
Use behavioural or longitudinal research to understand what happens over time.
And when the answers conflict?
Don't automatically choose the answer people said. Investigate the gap.
Because sometimes the most valuable research finding isn't:
“Users want this.”
It's:
“Users say they want this — but their behaviour tells us something else.”
That gap is where the real insight begins.
Why I think this fits your app
Your existing blogs cover visual design, asking better questions, AI, portfolios, confidence, and learning. This adds a more explicitly research/behavioural angle without repeating those topics.
It also gives you a nice progression:
Ask → Observe → Compare → Find the gap → Design
And it's genuinely research-backed rather than being another opinion piece.
Comments