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
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
Systems Mapping method illustration showing its working structure
Systems Thinking
Systems Mapping
Paper illustration of Leverage Points with its method-specific working model.
Systems Thinking
Leverage Points
Purposedifferent
For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access.Systems Mapping arranges elements, relationships, and boundaries so a complex field becomes legible at a glance. The overview stabilizes the overall picture before detail work or steering begins.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
LowMediumHigh
Timedifferent
20-60 min1-3 hHalf day
Participantsdifferent
1-43-123-12
Formatdifferent
AsyncWorkshop + asyncWorkshop
Outputdifferent
Runbook, Checklist, Escalation PathSystem Map, Dependencies, Leverage PointsLeverage Map, Action Strategy
Tagsno overlap
OperationsReliabilityDocumentation
Systems thinkingMappingBoundariesChange
Systems thinkingChangeStrategy
Add more methods

Often compared together

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

Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Paper illustration for Future Reality Tree.
Systems Thinking
Future Reality Tree
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command