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.

Selected:PersonasRisk MatrixKano ModelLASR (Lightweight Approach for Software Reviews)
Criterion
Paper illustration of two user profile cards with a goal, behavior evidence, and an open research question.
UX Research
Personas
Paper illustration of a calibrated five-by-five risk matrix with response cards.
Decision Making
Risk Matrix
A paper-based illustration representing Kano Model with its core stages and visible working result.
Product Discovery
Kano Model
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)
Purposedifferent
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 a project faces many possible disruptions, it quickly becomes unclear which risks deserve attention first. It separates options, evaluation criteria, and open risks. The result is captured as a Risk Matrix and a Top Risk List.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.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.
Complexitydifferent
MediumLowMediumMedium
Timedifferent
1-3 Tage30-60 min1-2 Tage3–4 h for initial assessment; preparation and deeper analysis additional
Participantsdifferent
Internes Team3-1010-501 or a small team; particularly suitable for 3–4 people
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Persona Profiles, Needs Summary, Scenario NotesRisk Matrix, Top Risk ListKano Matrix, Feature Classes, Priority ThemesLean 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 checks
Tagsno overlap
ResearchCustomerSynthesis
RiskDecisionPrioritizationAssessment
SatisfactionPrioritizationCustomer
ArchitectureQualityRiskAssessmentLean
Add more methods