User Research
Structured method to gather user insights through interviews, testing and observation to inform product decisions and design.
Classification
- ComplexityMedium
- Impact areaOrganizational
- Decision typeOrganizational
- Organizational maturityIntermediate
Technical context
Principles & goals
Use cases & scenarios
Compromises
- Incorrect sampling biases findings
- Stakeholder interpretations without methodological context
- Ethics and privacy breaches from improper conduct
- Small, fast iterations instead of rare large studies
- Combine qualitative and quantitative methods
- Prepare findings clearly for decision processes
I/O & resources
- Research questions and hypotheses
- Recruited participants and screening criteria
- Prototypes or artefacts to test
- Evidence-based recommendations
- Personas and usage scenarios
- Prioritised actions for roadmap/backlog
Description
User research collects qualitative and quantitative insights about users’ needs, behaviours, and contexts to inform product decisions. It combines interviews, surveys, observation and testing to validate assumptions and prioritise features. Results guide design, strategy and measurement across discovery and delivery phases.
✔Benefits
- Reduces uncertainty in product decisions
- Improves user-centred prioritisation
- Early identification of risks and side effects
✖Limitations
- Findings are often context-dependent and not always generalisable
- Requires time and resources for recruitment and analysis
- Qualitative insights must be translated into priorities
Trade-offs
Metrics
- Actionable insight rate
Share of research findings that lead to concrete product decisions.
- Time to insight
Time from research start to derivation of actionable recommendations.
- Participant diversity
Degree of representation of different user segments in studies.
Examples & implementations
E-commerce checkout optimisation
Moderated usability tests identified confusion points, led to simplified flows and reduced drop-off rates.
B2B portal user interviews
In-depth interviews revealed unnoticed work processes; the product team adapted features to real workflows.
Mobile app field observation
Contextual observations showed discrepancies between stated behaviour and actual usage, leading to design changes.
Implementation steps
Define goals and research questions.
Design study, recruit participants and review ethics.
Conduct, analyse and derive actions.
⚠️ Technical debt & bottlenecks
Technical debt
- Lack of central documentation of research findings
- No standardised templates for studies
- Outdated participant pools and lack of maintenance
Known bottlenecks
Misuse examples
- Using only friends and family as participants
- Treating findings as definitive truths instead of indications
- No follow-up after deriving insights
Typical traps
- Confirmation bias in question formulation
- Overinterpreting small samples
- Unclear success criteria before starting studies
Required skills
Architectural drivers
Constraints
- • Privacy and ethics regulations
- • Limited time and budget
- • Accessibility of realistic participants