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 RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
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.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.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 min Setup, dann laufend1-4 h2-6 h
Participantsdifferent
Internes Team1-3 maintaining, briefing for everyone3-83-10
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop
Outputdifferent
Persona Profiles, Needs Summary, Scenario NotesRAID Log, Status Report SourceProblem Statement, Cause Hypotheses, Confirmed Causes, Action PlanFMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap
ResearchCustomerSynthesis
RiskTrackingStakeholdersGovernance
Root causeProblem solvingQualityIncident
RiskQualityOperationsRoot cause
Add more methods