The difference between listening to users and understanding them

I've been in sessionsglossary×SessionA session is a single period of user interaction with a product, from entry to exit within a defined timeframe.Open glossary term→ where users confidently explain how they would behave, only to do something completely different a few minutes later. They say they'd read everything before making a decision, then skip half the content. They say they want more options, then hesitate when presented with them. They say something is clear, then struggle when they try to use it. None of that is intentional. It's just how people are.

Nobody is being unhelpful when this happens. People are describing an idealised versionglossary×VersionA version is a specific iteration of software or a product at a point in time.Open glossary term→ of themselves, because that is genuinely how they imagine they behave. The gap is not dishonesty, it is the difference between how someone thinks about a task in the abstract and what they do when they are actually in it.

If you take everything at face value, you end up designing for what users say they want, not what actually helps them. On one project, users repeatedly asked for more information earlier in the journey. The instinct was to surface more content upfront. On paper, that aligned perfectly with what had been said. In practice, it made the experience heavier and harder to move through. What users were really asking for wasn't more information. It was more confidenceglossary×ConfidenceConfidence is the level of certainty in a decision or outcome based on available evidence.Open glossary term→. That's a different problem.

The patternglossary×PatternA pattern is a reusable solution to a design problem that recurs across products and contexts. It captures an approach already shown to work, so a team solves the problem once rather than every time it appears.Open glossary term→ repeats across almost every project. Users ask for more options when they mean they do not trustglossary×TrustUser confidence that a product, service, or organisation will do what it promises.Open glossary term→ the default. They ask for a shorter form when they mean they do not understand why one of the questions is being asked. Taking the requestglossary×RequestA request is an action sent from a client to a server asking for data or a service.Open glossary term→ literally solves something, but rarely the thing that was actually wrong.

This is why the useful follow-up is almost never do you want more of this. It is what were you hoping to find out at that point, or what would have made you comfortable enough to carry on. Those questions get at the need underneath the requestglossary×RequestA request is an action sent from a client to a server asking for data or a service.Open glossary term→.

Understanding comes from looking beyond the words. It's about how people behave, where they hesitate, what they ignore, and what they expect to happen next. It's about spotting the gaps between what's said and what's done, and working out what's actually driving that behaviourglossary×BehaviourBehaviour refers to how users interact with a system, including actions, patterns, and responses.Open glossary term→.

Some of the most useful insightsglossary×InsightAn insight is a meaningful understanding that explains why something is happening and what it means.Open glossary term→ come from those gaps: a user saying something is fine but taking longer than expected to complete it; a moment where they pause not because something is unclear but because it doesn't feel right; a decision pointglossary×Decision PointA decision point is a moment in a user journey where a user must choose between actions that affect what happens next.Open glossary term→ where they second-guess themselves even though they've been given all the information they need. Those moments rarely show up in a summary, but they're often where the real issues sit.

Watching for it takes deliberate effort, because the interesting moments are quiet. A pause before a button. A scroll back up to re-read something. A cursor hovering while somebody decides. None of it registers as a problem in the moment, and all of it is evidence that the interfaceglossary×InterfaceAn interface is the point of interaction between a user and a system, where inputs are made and outputs are received. It can be visual, physical, or conversational.Open glossary term→ is asking for more than it should.

Strong researchservice×User ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service→ gets lost all the time because it gets reduced to a deck of quotes and observationsglossary×ObservationObservation is a research method where user behaviour is watched and analysed without interference.Open glossary term→. Everyone nods. Everyone agrees. It gets filed away as useful. And nothing changes.

Less polished researchservice×User ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service→ can leadglossary×LeadA lead is a potential customer who has shown interest in a product or service, typically by providing contact information or engaging with content.Open glossary term→ to real impact when someone takes the time to interpret it properly: to connect the dots, challenge what it means, push it into decisions instead of just documenting it. That's where the real difference sits. Not in how the research looks, but in what it changes. Good research is slightly uncomfortable. It challenges assumptions that felt safe, exposes gaps that weren't obvious, creates questions where there used to be certainty. That's when you know it's doing something.