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
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Paper illustration of Barrier Analysis with its method-specific working model.
Operations
Barrier Analysis
Paper illustration of Lean Startup with its method-specific working model.
Innovation
Lean Startup
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Purposedifferent
For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions.For uncertain business assumptions, the method forces the idea into contact with real market reactions early. It separates wishful picture, assumption, and observable behavior, so that learning becomes faster than planning. This translates uncertainty into measurable insight.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.
Complexitydifferent
LowMediumMediumMedium
Timedifferent
15-30 min2-4 hWochen bis Monate je Lernzyklus1-4 h
Participantsdifferent
2-62-62-83-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Root cause notes, CountermeasuresBarrier Inventory, Failure Analysis per Barrier, Action BacklogHypothesis list, MVPs, Learning reports, Pivot or persevere decisionProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
Root causeIncidentLeanProblem solving
Root causeSafetyIncident
LeanStartupValidationMVP
Root causeProblem solvingQualityIncident
Add more methods