methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration of two people facing each other, speech bubbles and an open interview notebook.
UX Research
User Interviews
Paper illustration of two user profile cards with a goal, behavior evidence, and an open research question.
UX Research
Personas
A paper-based illustration representing Kano Model with its core stages and visible working result.
Product Discovery
Kano Model
Affinity Diagramming
UX Research
Affinity Diagramming
Purposedifferent
When teams derive needs only from assumptions and real motives are missing, user interviews give direct access to behavior and meaning. Conversations from the target group's everyday life make patterns, tensions, and open questions solidly visible.When target groups stay too vague and teams talk about the same people differently, personas create a shared, solid picture of usage. Condensed profiles make needs, contexts, and differences tangible enough for decisions.When features need to be distinguished by their effect on satisfaction, it makes expectations and surprises comparable. It separates basic needs, performance contribution, and delight.When research notes, feedback, or observations sit unconnected side by side, affinity diagramming sorts the raw material into solid themes. Many individual points turn into patterns that make decisions and opportunities clearer.
Complexitydifferent
LowMediumMediumLow
Timedifferent
30–60 min per interview1-3 Tage1-2 Tage45–90 min
Participantsdifferent
1 participant per interviewInternes Team10-503-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Interview Notes, Themes, Insight SummaryPersona Profiles, Needs Summary, Scenario NotesKano Matrix, Feature Classes, Priority ThemesTheme clusters, Insight statements, Opportunity areas
Tagsno overlap
QualitativeResearchCustomerDiscovery
ResearchCustomerSynthesis
SatisfactionPrioritizationCustomer
SynthesisQualitativeRoot cause
Add more methods