People can give thoughtful opinions about a product idea without knowing how they would behave when using it. The GOV.UK user-research guidance provides a starting point for planning research around user needs. A practical interviewing technique is to ask about a recent, concrete experience and follow the sequence of events closely.
Reconstruct an actual task
A hypothetical team designing expense software can ask a participant about the last claim they submitted. What triggered the task? Which documents did they need? Where did they wait? What happened when information was missing? The resulting account can reveal dependencies that a question such as would you use an easier app leaves unexplored.
Researchers should distinguish observed behavior, the participant’s explanation and the team’s interpretation. Keeping those layers separate makes the evidence easier to discuss. It also reduces the chance that an attractive design idea is mistaken for a need expressed by participants.
Watch for the workaround
A handwritten note, a spreadsheet or a message to a colleague can show how someone bridges a gap in the current service. The workaround may be inconvenient, but it can also provide useful flexibility that a new product accidentally removes. Understanding its purpose is more valuable than assuming every manual step should disappear.
Recruitment matters too. A study drawn only from confident existing users may miss people who abandoned the service or could not begin. The research plan should explain whose experience is represented and where more evidence is needed.
Turn findings into decisions
A useful research summary connects evidence to a question the team needs to resolve. It can identify what to change, what to test next and what remains uncertain. The goal is an improved understanding of the task, with enough traceability that another person can examine how the conclusion was reached.
