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 Intervention Mapping.
Systems Thinking
Intervention Mapping
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Purposedifferent
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.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.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
HighHighMedium
Timedifferent
1-5 TageHalber TagAs needed
Participantsdifferent
4-125-204-15
Formatdifferent
Workshop + asyncWorkshopWorkshop + async
Outputdifferent
Logic Model, Change Objectives, Intervention Components, Evaluation PlanSimulation Notes, Gaps List, Updated RunbooksIncident Log, Action Tracker, Stakeholder Updates
Tagsno overlap
ChangeSystems thinkingCapability
ResilienceOperationsIncident
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
Paper illustration of Leverage Points with its method-specific working model.
Systems Thinking
Leverage Points