User-centred design has become a familiar phrase across almost every industry. Most organisations now understand that speaking to customers is important, so research sessions, surveys and usability tests have become a regular part of product development. Yet despite all this activity, many digital products still leave people frustrated. They still ask questions that should not need asking, struggle to complete simple tasks and abandon journeys that looked perfectly reasonable in the design studio.
The problem is rarely that organisations are ignoring users altogether. More often, they are listening without really understanding what they are hearing.
There is an important difference between collecting opinions and uncovering meaning. Good design depends on recognising that difference.
What users say is only the starting point
When someone participates in a research session, they bring much more than the words they say. They arrive with habits, expectations, past experiences and assumptions built over years of using other products. They may describe one problem while struggling with something completely different. They may confidently explain how they would behave in the future, only to act differently when faced with the product in front of them.
People are good at explaining how they feel – they are much less reliable at explaining why they feel that way.
This is where understanding begins. A participant might say that they dislike a homepage because it feels “busy”. If that feedback is taken at face value, the instinct may be to remove content or create more white space. Yet the real issue may have nothing to do with visual design. Perhaps the page contains too many competing calls to action. Perhaps the navigation gives them no clear starting point. Perhaps they simply cannot recognise the information that matters to them.
Behaviour often reveals more than feedback
This is why experienced researchers spend as much time observing behaviour as they do asking questions. Watching someone hesitate before clicking a button can reveal more than several minutes of conversation. A long pause before selecting a menu option often tells you that the labels are unclear. Repeatedly scrolling up and down a page may suggest uncertainty rather than curiosity.
Context shapes the experience
Understanding also requires context. Users do not interact with products in controlled environments. They are distracted, tired, in a hurry, or trying to complete a task between meetings. They may be using a phone with one hand while walking to a train, or they may have poor internet access slowing everything down.
Design decisions that seem obvious in a quiet meeting room can feel completely different in everyday life. This is why successful research asks broader questions than simply whether someone liked a design. It explores where they are, what they are trying to achieve and what pressures they are working under.
A banking journey, for example, may be used by someone who is already anxious about money. A healthcare form may be completed by someone who is worried about their symptoms. In these situations, unclear wording or an unexpected error message can have a much greater impact than the design team anticipated.
Look beyond the solution users suggest
Another common mistake is treating every piece of feedback as a design request – users often suggest solutions because they want to be helpful. They might ask for another button, a larger menu or a new feature. Their suggestion deserves attention because it points towards a genuine frustration, but it should not automatically become the solution.
Imagine someone says they want a search bar on every page – they may believe that search is the answer because they cannot find information quickly enough. The real issue may be that the navigation structure makes no sense. Improving the information architecture could solve the problem more effectively than adding another search function.
The goal is to understand the need behind the suggestion. Asking follow-up questions can help uncover that need. What were they trying to find? Where did they expect it to be? What made them feel that search would help? These questions move the conversation away from a specific feature and towards the underlying problem.
Patterns matter more than isolated opinions
Every research project produces individual opinions. One participant prefers one layout, another likes something completely different – if decisions are based on whichever opinion is expressed most strongly, products become inconsistent and directionless.
Meaningful insights appear when similar behaviours emerge across different people. If several participants hesitate in the same place, misunderstand the same label or fail the same task, there is a strong signal that something in the experience deserves attention.
An isolated comment may still be important, particularly when it relates to accessibility, safety or a serious barrier. However, most design decisions need to be informed by the wider body of evidence rather than a memorable quote from one participant.
Data shows what happened, research helps explain why
The same principle applies when interpreting quantitative data. Analytics can reveal where users leave a journey, how long they spend on a page or which features receive the most attention. These numbers are incredibly useful, but they cannot explain motivation on their own. A sudden drop in conversions might indicate confusion. It might also reflect seasonal demand, technical issues or changing customer expectations. Without speaking to people, the numbers remain incomplete.
Equally, research conversations without supporting data can become misleading if a small number of participants dominate the narrative. The strongest decisions usually come from combining both perspectives. Data highlights where problems exist. Research helps explain why they happen. For example, analytics may show that many users abandon a form at the same step. Usability testing may then reveal that the question is unclear or that users do not have the information required to answer it. Together, these findings provide a much stronger basis for change.
Book a call
At Make it Clear, we treat listening as an important first step, but it is only the beginning. Our user-centred design asks deeper questions. It looks beyond opinions, feature requests and first impressions. It pays attention to behaviour, context, and recurring patterns. It connects individual observations into a clearer picture of what people genuinely need.
Our research strives to influence products in a way that feels natural to use because they reflect how people actually think, behave, and move through the world.
If you’d like to start the conversation, book a call with our team here.
