What is User Research?

Overview

Many organisations understand their services extremely well. Their teams know how different departments fit together, which processes sit behind each service and the terminology used every day.

A new visitor does not share that knowledge. They may arrive with a specific question, limited time and no understanding of how the organisation is structured. They may describe a service differently, start on an unexpected page, or look for information in a place the organisation would never think to check.

This difference matters because website projects involve hundreds of decisions about content, navigation, functionality and design. When those decisions rely mainly on internal experience, the finished website can make perfect sense to the people who commissioned it while remaining difficult for everyone else.

User research helps organisations understand that gap. It gives them evidence about the people they serve, the tasks those people need to complete and the barriers that can make those tasks harder. That evidence does not make every decision obvious, but it gives project teams a better basis for making them.

Good user research is not about collecting as much information as possible. It is about learning enough to make stronger decisions.

What user research helps organisations understand

User research is the process of learning about the people who use, or may need to use, a website and the tasks they are trying to complete.

The word ‘user’ can describe many different people. Depending on the organisation, users might be customers, students, residents, patients, applicants, parents, members, staff or professional partners. They may visit regularly or arrive once to complete a single important task.

That process helps organisations understand:

• who they are and what they need to achieve
• how they approach a task
• what information they expect to find
• where they become uncertain or frustrated
• what influences their decisions
• whether the website helps them complete their task

The purpose is not to hand design decisions to the people taking part. They can provide evidence about their goals, experiences and difficulties. The project team still needs to interpret that evidence and decide how the website should respond.

A project team can then combine that evidence with organisational objectives, technical knowledge, accessibility requirements and professional judgement.

Why assumptions are often wrong

Internal knowledge is valuable during a website project. Staff understand the organisation, its services and the practical constraints behind them. The difficulty arises when familiarity begins to influence decisions that should reflect the visitor’s point of view.

An organisation may group information by department because that structure is familiar internally. Visitors may think in tasks instead. Someone who needs to report a repair is unlikely to care which team handles the process. They want to know where to start, what information they need and what will happen next.

Language creates a similar problem. Terms that feel precise and ordinary inside an organisation can be unfamiliar outside it. A university may use a formal name for an admissions process while prospective students search using a much simpler phrase. Both descriptions may be accurate, but only one reflects the language people actually use.

This is often called ‘the curse of knowledge’. Once a process or service becomes familiar, it is easy to overlook what a first-time visitor may not know. Staff may skip over missing explanations, use internal terms without thinking or assume the organisation’s structure will make sense to everyone.

The people who know an organisation best may find it hardest to approach the website as a first-time visitor would. User research does not dismiss internal expertise. It helps teams recognise where that expertise needs to be balanced with evidence from the people using the service.

What user research tries to understand

The most useful starting point is a set of questions rather than a preferred solution.

Why has someone visited the website? What are they trying to complete? What do they already know? What information do they expect to find, and what language do they use to describe it? Where do they hesitate? What nearly stops them continuing?

Consider a parent who needs to report their child’s absence before leaving for work. The task may sound simple, but the surrounding circumstances affect the experience. They may be using a phone, working quickly and unsure whether they need to call, complete a form or contact a particular member of staff. A page that explains the school’s attendance policy in detail may still fail if the reporting instructions are difficult to find.

A page may contain all the necessary information and still be difficult to use if people cannot find it, understand it or know what to do next.

Where does user research come from?

User research rarely gets based on a single source of information. Different forms of evidence reveal different parts of the experience, and the clearest picture usually comes from comparing them.

Analytics

Analytics help show how people use a website. They can highlight popular pages, common routes, devices, website entry points and the places where people leave.

Those patterns help teams identify questions worth exploring. A page with a high exit rate may be causing difficulty or failing to answer the visitor’s question successfully. Analytics show that something happened, but they rarely explain why.

Website search

People often use different words from the organisation when they search a website. Those searches can expose missing information, labels that don’t make sense to visitors or content that sits somewhere they would not expect.

Search data can also show where people look for information that already exists. In that situation, the issue may not be the content itself. The page may be poorly named, placed in an unexpected section or difficult to reach through navigation.

User interviews

Interviews help organisations understand goals, expectations and previous experiences. A conversation can reveal why someone approached a task in a particular way, what they expected to happen and which parts of the process caused concern.

The value comes from listening for repeated needs and behaviours rather than treating every individual preference as a requirement.

Usability testing

Usability testing involves observing people as they attempt realistic tasks using a website, design or prototype. It shows where instructions are misunderstood, interactions are missed and apparently simple routes become harder than expected.

People do not always recognise or describe these difficulties afterwards. Watching the task unfold can reveal hesitation, misunderstanding and recovery that a survey or analytics report may miss.

Surveys

Surveys provide a structured way to collect feedback from a larger group. They can help organisations understand satisfaction, confidence, recurring concerns and differences between audiences.

Survey results are most useful when the questions are focused and the findings are considered alongside other evidence. A rating can show that people found something difficult, but further research may still be needed to understand the cause.

Customer-facing teams

Support staff, reception teams, advisers, sales teams and others who speak with people every day often hold some of the richest knowledge in an organisation. They know which questions recur, which instructions cause confusion and where people regularly need extra help.

That information is invaluable, but it only tells part of the story. People will rarely get in touch to say a website worked well for them. Even so, repeated questions can expose problems that are easy to miss elsewhere.

Research becomes most valuable when different sources point towards the same conclusion. Analytics could identify a pattern, while interviews or usability testing help to explain it. Together, they give organisations more confidence that the issues they’re addressing genuinely matter.

How research is used in practice

Findings need to remain useful after the interviews, testing sessions or data reviews have finished. Project teams often turn what they have learned into a small set of shared outputs that can guide decisions throughout the project.

These outputs do not replace the research. They make the findings easier for the wider team to understand and use.

User research is not only for large organisations

Useful evidence does not always require a large study, a large budget or months of work. The scale should reflect the decision being made, the importance of the service and the resources available.

A smaller organisation might begin by reviewing enquiries, speaking with customer-facing staff, looking at website searches and observing a few people attempting key tasks. An organisation improving an existing website may already have years of analytics, support questions and feedback available.

None of these sources is perfect on its own. It’s never the best approach to let a few conversations speak for every visitor. Similarly, analytics rarely explain exactly why someone behaved in a particular way. Together, though, they give the organisation more to work with than assumptions alone.

The principle matters more than the budget. Even modest research can change the direction of a project when it happens early enough to influence decisions.

How user research influences a website project

User research should not sit in a discovery report that the project team reads once and then sets aside. Its value comes from remaining connected to the decisions that follow.

A simplified process can show the main stages of a website project, but research does not belong to only one of them. Early findings help teams test their objectives and develop personas, scenarios and user journeys. Later research informs information architecture, content, navigation, functionality and design. Testing and real-world use may then lead the team back to earlier decisions.

Research may confirm the organisation’s initial objectives or show that its priorities need to change. If people struggle to understand whether they are eligible for a service, for example, the project can make clearer eligibility information a priority.

Those findings influence the journeys the website needs to support, how information is organised and the language used across content and navigation. Because the process is not perfectly linear, testing or live use may lead the team back to an earlier decision. What matters is that understanding users remains connected to the project rather than being collected once at the beginning and gradually forgotten.

Common misconceptions about user research

User research is not simply asking people what they want

People can often explain their goals, concerns and experiences, but they may describe solutions based on what they already know.

Someone might ask for a chatbot because they struggled to find an answer. The underlying need may be clearer navigation, better search or more direct content. Building the requested feature without understanding the problem could add cost without making the task easier.

The aim is to understand what people are trying to achieve and why the current experience falls short. Designers, content specialists and developers then use their expertise to decide how the website should respond.

Analytics are only part of the picture

Analytics can reveal where people go, what they do and where patterns emerge. They rarely explain the complete reason behind that behaviour.

A heavily visited page may be valuable, or people may be returning because the information is unclear. Combining analytics with interviews, usability testing, feedback and organisational knowledge gives teams a stronger basis for deciding what to change.

Research is not a one-off exercise

The most intensive research may happen before and during a website project, but learning should continue after launch.

Analytics, website searches, enquiries and occasional testing can show whether earlier decisions still work as content, services and user expectations change. This does not mean keeping the website in constant redevelopment. It means revisiting it when the evidence identifies a worthwhile improvement.

Better decisions, not perfect certainty

User research cannot represent every person or predict every situation. It does not remove disagreement, settle every priority or decide how much an organisation should invest.

Its value lies in reducing avoidable uncertainty. Research helps teams distinguish evidence from opinion, identify which problems matter most and make decisions with a clearer understanding of the people the website needs to support.

Some of those decisions concern prominent parts of the website, such as navigation, content and functionality. Others involve details visitors may never consciously notice, including labels, instructions, page order, form questions and what happens when something goes wrong.

User research does not automatically make those decisions. Professional judgement still matters, but it is better informed when teams understand how people actually use the website.

Better information leads to more informed decisions. User research provides the evidence that helps organisations make them with greater confidence.

How we can help