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
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
Paper illustration for Evaporating Cloud.
Systems Thinking
Evaporating Cloud
Paper illustration of Leverage Points with its method-specific working model.
Systems Thinking
Leverage Points
Purposedifferent
In preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic.The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict.Leverage Points show exactly where interventions in a system produce a disproportionate effect. It draws relationships, patterns, and feedback loops. The result is captured as a leverage map and action strategy.
Complexitydifferent
HighMediumHigh
Timedifferent
Halber Tag60-120 minHalf day
Participantsdifferent
5-202-83-12
Formatsame
WorkshopWorkshopWorkshop
Outputdifferent
Simulation Notes, Gaps List, Updated RunbooksConflict Cloud, Assumption List, Breakthrough Ideas, Next ExperimentsLeverage Map, Action Strategy
Tagsno overlap
ResilienceOperationsIncident
Theory of ConstraintsAssumptionsSystems thinking
Systems thinkingChangeStrategy
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration for Future Reality Tree.
Systems Thinking
Future Reality Tree
Paper illustration of DIBB with its method-specific working model.
Product Strategy
DIBB
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command