Reference families used in this guide
User Interviews
Use when you need to understand user goals, motivations, pain points, expectations, workarounds, and decision making.
Focus Group Discussions
Use selectively when you need to explore perception, language, reactions, or shared expectations across a relevant user group.
Field Observation and Contextual Inquiry
Use when you need to see what users actually do in their real context.
Stakeholder and Expert Interviews
Use when you need business rules, constraints, policy context, risks, or domain knowledge.
Surveys
Use when you need broad input from many users and already know what questions to ask.
Usability Testing
Use when you need to know whether users can complete key tasks using a design, prototype, or product.
Prototype and Concept Testing
Use when you need to test an idea, flow, dashboard, admin journey, or risky assumption before full development.
Design Sprint
Use when a cross-functional team needs to quickly align, prototype, and validate a risky product idea.
Journey Mapping
Use when you need to understand an end-to-end experience across stages, channels, touchpoints, pain points, and emotions.
Card Sorting
Use when you need to understand how users group information, features, labels, or categories.
Tree Testing
Use when you need to test whether users can find items in a proposed navigation structure.
Heuristic Evaluation
Use when experts need to quickly review an interface against usability principles.
Analytics and Funnel Analysis
Use when you need to understand behavior at scale, drop-offs, retention, feature usage, or conversion.
Support Ticket, Complaint, and App Review Analysis
Use when a live product already has complaints, tickets, app reviews, or call center feedback.
A/B Testing and Controlled Experiments
Use when a live product has enough traffic and the team needs to compare two alternatives using measurable outcomes.
Planning, question, and output helpers
Open these when the team needs planning support, not before.
Source families used in the guide
Method-specific chips point back here so the page stays readable instead of turning into a long bibliography.