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
Affinity Diagramming
UX Research
Affinity Diagramming
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
Paper illustration of two user profile cards with a goal, behavior evidence, and an open research question.
UX Research
Personas
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 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.LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail.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.
Complexitydifferent
LowLowMediumMedium
Timedifferent
30–60 min per interview45–90 min3–4 h for initial assessment; preparation and deeper analysis additional1-3 Tage
Participantsdifferent
1 participant per interview3-101 or a small team; particularly suitable for 3–4 peopleInternes Team
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Interview Notes, Themes, Insight SummaryTheme clusters, Insight statements, Opportunity areasLean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checksPersona Profiles, Needs Summary, Scenario Notes
Tagsno overlap
QualitativeResearchCustomerDiscovery
SynthesisQualitativeRoot cause
ArchitectureQualityRiskAssessmentLean
ResearchCustomerSynthesis
Add more methods