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
Paper illustration for Future Reality Tree.
Systems Thinking
Future Reality Tree
Systems Mapping method illustration showing its working structure
Systems Thinking
Systems Mapping
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.A Future Reality Tree shows how desired actions are meant to lead to a better system state. The method checks whether a path of change holds together logically before time flows into implementation.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.
Complexitydifferent
LowHighMedium
Timedifferent
20-60 min2-4 h1-3 h
Participantsdifferent
1-43-83-12
Formatdifferent
AsyncWorkshopWorkshop + async
Outputdifferent
Runbook, Checklist, Escalation PathFuture Reality Tree, Negative Branches, Assumption List, Improved InjectionsSystem Map, Dependencies, Leverage Points
Tagsno overlap
OperationsReliabilityDocumentation
Theory of ConstraintsSystems thinkingChange
Systems thinkingMappingBoundariesChange
Add more methods

Often compared together

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

Paper illustration for Evaporating Cloud.
Systems Thinking
Evaporating Cloud
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration for Intervention Mapping.
Systems Thinking
Intervention Mapping
Paper illustration of Leverage Points with its method-specific working model.
Systems Thinking
Leverage Points