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 Intervention Mapping.
Systems Thinking
Intervention Mapping
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
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.Intervention Mapping translates a need for change into a planned, evaluable program. The method connects target group, determinants, actions, and measurement into a traceable chain.During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once.
Complexitydifferent
LowHighMedium
Timedifferent
20-60 min1-5 TageAs needed
Participantsdifferent
1-44-124-15
Formatdifferent
AsyncWorkshop + asyncWorkshop + async
Outputdifferent
Runbook, Checklist, Escalation PathLogic Model, Change Objectives, Intervention Components, Evaluation PlanIncident Log, Action Tracker, Stakeholder Updates
Tagsno overlap
OperationsReliabilityDocumentation
ChangeSystems thinkingCapability
IncidentOperationsReliability
Add more methods

Often compared together

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

Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Paper illustration for Future Reality Tree.
Systems Thinking
Future Reality Tree
Paper illustration for Learning Review.
Operations
Learning Review