When this helps
The team has a product idea or service problem but is uncertain about people’s needs, context or priorities. Research turns those uncertainties into questions that can be investigated.
What you receive
A question-led plan, recruitment criteria, interview or observation guide, synthesis and decision-focused findings.
Start with a decision you could change
“Understand our users” is too broad to guide a study by itself. A more useful question is whether a proposed application asks for information people can obtain, or how a worker completes a task when they are away from a desk. We identify the decision that the evidence should inform and the assumptions most likely to change it.
Discovery interviews can examine needs and past experiences. Contextual observation can reveal workarounds and environmental constraints that are difficult to recall. Reviewing existing support evidence can expose recurring questions, provided the sample and collection process are understood. The plan explains why each method is appropriate.
Make synthesis traceable
The analysis connects a finding back to source observations or interview material. It records whose perspective is represented, where people differed and what we still do not know. A memorable quotation should not outweigh a wider pattern, and a theme should not imply a frequency the study cannot support.
Deliverables focus on choices: what to investigate next, what a prototype needs to demonstrate and which assumptions are too uncertain to treat as requirements. Personas or journey maps are useful only where they help the team act on the evidence. They are not mandatory decorative outputs.
Protect the people taking part
The study plan sets out recruitment, participant information, consent, access to material and retention arrangements. Recording is a separate, explicit decision. Access needs and the sensitivity of the topic affect how the session is run; research should not ask a person to disclose private information simply to make a scenario feel realistic.
How the engagement runs
- Discuss what you need to learn, who uses the service and what you already know.
- Agree the research activities, access requirements, deliverables and what is included in the proposal.
- Carry out the research and explain both what we observed and what we think it means.
- Walk your team through the findings, prioritise improvements and agree what needs a follow-up check.
Cost and timing
Access to appropriate people, context of use, session format, sensitive topics and the depth of synthesis. The proposal states the scope, fee basis and dependencies. Recruitment, stakeholder availability or access to a test environment can affect the calendar; no fixed turnaround is assumed before these are understood.
What to bear in mind
What somebody says they would do is different from observing what they do. Choose methods that fit the question and label the distinction.
Your team receives recommendations it can discuss and implement with its chosen supplier. Where another method would answer the question better, we explain why before proposing additional work.