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 for Fault Tree Analysis.
Operations
Fault Tree Analysis
Paper illustration of Lean Startup with its method-specific working model.
Innovation
Lean Startup
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Purposedifferent
For a critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage.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.Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.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.
Complexitydifferent
HighMediumLowLow
Timedifferent
2-6 hWochen bis Monate je Lernzyklus45-90 min15-30 min
Participantsdifferent
3-82-82-82-6
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Fault Tree, Critical Paths, Cause Hypotheses, Control ActionsHypothesis list, MVPs, Learning reports, Pivot or persevere decisionAssumption List, Critical Assumptions, Learning PlanRoot cause notes, Countermeasures
Tagsno overlap
RiskRoot causeSafety
LeanStartupValidationMVP
AssumptionsRiskDecisionDiscovery
Root causeIncidentLeanProblem solving
Add more methods