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 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
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 for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
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.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.For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.
Complexitydifferent
MediumLowMediumHigh
Timedifferent
1-3 Tage30-60 min3–4 h for initial assessment; preparation and deeper analysis additional2-6 h
Participantsdifferent
Internes Team3-101 or a small team; particularly suitable for 3–4 people3-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Persona Profiles, Needs Summary, Scenario NotesRisk Matrix, Top Risk ListLean 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 checksFMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap
ResearchCustomerSynthesis
RiskDecisionPrioritizationAssessment
ArchitectureQualityRiskAssessmentLean
RiskQualityOperationsRoot cause
Add more methods