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 for Current Reality Tree
Systems Thinking
Current Reality Tree
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
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.A Current Reality Tree condenses many symptoms into a few causal chains. The method makes visible which core problems drive several negative effects at once.When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects.When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.
Complexitydifferent
HighHighHighMedium
Timedifferent
2-6 h2-6 h1-4 Wochen45-60 min
Participantsdifferent
3-83-81-62-8
Formatdifferent
Workshop + asyncWorkshopAsyncWorkshop + async
Outputdifferent
Fault Tree, Critical Paths, Cause Hypotheses, Control ActionsCurrent Reality Tree, Core Problems, Intervention IdeasExperiment results, Decision log, Learning summaryAssumption map, Test backlog, Risk ranking
Tagsno overlap
RiskRoot causeSafety
Systems thinkingRoot causeConstraintsCausality
ExperimentsGrowthAnalyticsValidation
AssumptionsRiskExperimentsValidation
Add more methods