Technology
Shows teams how people really use their products
Organisations make assumptions about people using their products and services. A user researcher tests them. They study what people are trying to achieve, how they behave and where a product gets in their way. They then help a team decide what to improve. User researchers work in technology, government, finance, healthcare and other services designed around human behaviour.
Getting people to talk is only the beginning. A researcher must notice when a question suggests its own answer. They separate one memorable participant from a wider pattern and state what a small study cannot prove. Curiosity needs restraint. The pleasure comes when a confident assumption fails, without claiming more certainty than the evidence supports.
Psychology, anthropology, sociology and human-computer interaction are common backgrounds, but no single degree is required. People also move from design, market research, customer insight, academia and service delivery. Employers seek ethical research, careful analysis and clear implications. A portfolio is useful when it shows how research changed a decision, not only the methods used.
| When | Lowest 10% earn under | A typical earner | Top 10% earn over |
|---|---|---|---|
| On graduating | £23,000 | £29,000 | £40,000 |
| 1 year in | £25,000 | £33,000 | £46,000 |
| 2 years in | £28,000 | £38,000 | £52,000 |
| 3 years in | £31,000 | £43,000 | £60,000 |
| 4 years in | £34,000 | £48,000 | £68,000 |
| 5 years in | £36,000 | £52,000 | £76,000 |
| 6 years in | £38,000 | £56,000 | £83,000 |
| 7 years in | £40,000 | £60,000 | £89,000 |
| 8 years in | £42,000 | £64,000 | £95,000 |
| 9 years in | £44,000 | £67,000 | £100,000 |
| 10 years in | £46,000 | £70,000 | £105,000 |
A product team can spend weeks debating what users probably want. Speaking to the people themselves often changes the conversation in an hour. Your work can reveal that a simple-looking form is excluding somebody. Customers may have invented their own workaround, or the team may be solving the wrong problem. There is real satisfaction in making a decision more humane because the people affected were understood rather than imagined.
People rarely behave as neatly as a customer journey suggests. Somebody will understand an ordinary word differently or use a feature for an unexpected purpose. They may avoid a useful service because of a concern the team never considered. If you enjoy having your assumptions challenged, research offers a steady supply of small discoveries. Curiosity is part of the job.
Research is especially valuable when it happens early. A few well-chosen conversations can show that a proposed feature has little value before months are spent building it. Later, a usability study can identify the exact moment people become confused. You do not make the final decision alone, but strong evidence can change what a whole team builds and why.
Evidence competes with deadlines, budgets, technical limits and senior opinions. A team may ask for research after it has committed to a solution. It may then resist a finding that would force a change. You need good working relationships and must present the result at the right moment. Being correct is not enough if the organisation cannot act on what you learnt.
The memorable part is the conversation with a participant. Before it happens, you may spend days deciding who to speak to and writing questions that find suitable people. You arrange consent, check accessibility needs and find a time that works. Participants cancel, technology fails and a well-designed study can stall because the right people are hard to reach. Good research depends on careful organisation as much as insightful questions.
Research sometimes means hearing about debt, illness, discrimination, bereavement or repeated failure by a service. You must stay present without turning the session into counselling and protect participants without becoming detached. Even ordinary interviews require sustained attention. After five conversations, the sixth person still deserves to be heard as if they were the first.
Usually 3–4 years
Psychology, anthropology, sociology and human-computer interaction offer different ways to observe people and interpret what they do. A master’s may deepen those methods but is not always necessary. During the degree, volunteer to run a study rather than only writing about research: recruit participants, handle consent and discover how quickly a neat question becomes messy. For a portfolio, trace the finding into a decision that changed, while being honest about what your small sample could not establish.
Usually 0–2 years’ experience
Early studies are closely supervised. You recruit participants, take notes, watch people use a product and organise findings. The essential habits are neutral questions and responsible treatment of participants. You also learn why an interesting comment is not automatically a dependable pattern.
Usually 2–5 years’ experience
A loose request such as “find out which design users prefer” becomes your responsibility to reframe. You choose the method and participants, run the study, analyse the evidence and connect it to the team’s decision. Owning the question matters more than simply delivering competent sessions.
Usually 5–7 years’ experience
You’re trusted with broader, more sensitive and less clearly defined questions. You may combine several methods, plan research across a product area and challenge the team when it is asking the wrong question. You’ll also coach colleagues and make sure research influences strategy rather than arriving as feedback on an almost finished design.
Usually 7–10 years’ experience
Research now crosses several products or services. You decide where separate studies should become one programme and where local differences matter. A lead may coordinate a group of researchers. A principal usually stays an individual researcher with influence across the organisation. The work is to improve how many teams learn, not maximise the number of sessions you run.
Usually 10+ years’ experience
You’re responsible for the research function as well as individual projects. You hire and develop researchers and set ethical and quality standards. You decide where limited research time should go and bring user evidence into senior decisions. The work moves towards leadership and organisational change, though credibility still depends on understanding the craft.
Gives you a foundation in human behaviour, experiments and the dangers of drawing conclusions too quickly. The methods transfer directly. Product research is usually faster and messier than a university study, and it requires recommendations rather than only an academic conclusion.
Sociology, anthropology and related subjects teach you to notice context and power. They also reveal the gap between what people say and what they do. Interview and observation methods are especially useful. Some graduates need more confidence with product data and business decisions.
Provide direct experience of watching people use digital products and designing studies around them. Graduates often understand how research fits into a product team. They must ensure their design instincts do not lead participants towards a preferred solution.
History, English, languages and similar subjects develop careful interpretation and close listening. They also teach you to build a clear argument from incomplete evidence. The gap is research design: graduates must distinguish a striking account from a dependable pattern and make their method transparent enough to challenge.
Builds an understanding of customers, organisations and how evidence supports a commercial decision. The main adjustment is moving from broad questions about markets and preferences towards observing how particular people experience a product or service.
Science, education, health and computing can provide valuable knowledge of a specialist service and the people using it. That familiarity reveals vocabulary, constraints and risks an outsider may miss. Sound methods and a willingness to question the field’s familiar assumptions are what turn subject knowledge into reliable research.
Hover a subject to see why it helpsTap a subject to see why it helps
08:45 – 10:00Choose the real question
You check consent and accessibility for a study about booking a medical appointment online. The test design does not work with a screen reader, so one participant will use the real service. A product manager asks which reminder design people prefer. You ask what decision sits underneath the question and uncover an assumption about why people miss appointments. The study widens to the whole journey instead of becoming a beauty contest between two screens.
10:00 – 11:30Run and interpret the first session
A participant overlooks the rearrangement link and phones the clinic instead. You resist pointing it out and learn that they fear losing the original appointment before securing another; colour is not the problem. Afterwards, you and the designer separate observation from interpretation and add the path to a journey map. One session is not a verdict, but it has produced a useful question to test in the next four.
11:30 – 12:30Speak to the clinic manager
The clinic manager explains that patients often ring because the service cannot handle some complicated appointments. What looked like avoidable behaviour is partly a sensible response to a hidden rule. You update the questions so later sessions explore how people decide when the website can be trusted.
12:30 – 13:15Lunch
Café toastie.
13:15 – 14:45More sessions
Two participants rearrange easily; another struggles because English is not their first language. You keep the core questions consistent while following unexpected details. A transcription tool saves time, but it mistakes medical terms and cannot tell you which pauses mattered, so your notes remain important.
14:45 – 15:45Make sense of the evidence
You group observations across the sessions. The participants did not simply need a louder reminder: they needed confidence that changing an appointment would not leave them without one. You mark which findings appeared repeatedly, which affected only a particular circumstance and what the small sample cannot answer.
15:45 – 16:30Share early
The product manager, designer and engineer join a short playback. You show brief clips, explain the pattern and connect it to the decision in front of them. The engineer suggests a way to display available alternatives before releasing the original appointment. The research has moved the conversation from wording to the structure of the service.
16:30 – 17:15Plan what comes next
The finding raises a new risk: some patients may see no suitable alternatives. You agree to test that case and to examine support-call data before recommending a change. Good research often replaces one vague assumption with a smaller set of answerable questions.
17:15 – 17:45Respect a change of mind
A participant emails to withdraw permission for their recording to be used in presentations. You remove their clip from the team playback and confirm that the broader finding is still supported by other sessions. The quotation was vivid, but consent continues after the interview; no insight is valuable enough to make a participant’s choice inconvenient.
+3 hours compared with the average UK job