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
A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving
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.For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together.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
HighHighMediumMedium
Timedifferent
1-5 TageHalber Tag45-90 minAs needed
Participantsdifferent
4-125-202-54-15
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Logic Model, Change Objectives, Intervention Components, Evaluation PlanSimulation Notes, Gaps List, Updated RunbooksA3 Report, Action Plan, Root Cause AnalysisIncident Log, Action Tracker, Stakeholder Updates
Tagsno overlap
ChangeSystems thinkingCapability
ResilienceOperationsIncident
LeanProblem solvingCoachingOperations
IncidentOperationsReliability
Add more methods