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
ChatOps workspace showing the question, observations, and next decision.
DevOps
ChatOps
Paper illustration of Leverage Points with its method-specific working model.
Systems Thinking
Leverage Points
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
Paper illustration for Intervention Mapping.
Systems Thinking
Intervention Mapping
Purposedifferent
For operational work in a distributed team, the method links communication with direct system control. It records decisions right where the signal, the context, and the execution come together.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.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.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.
Complexitydifferent
MediumHighHighHigh
Timedifferent
OngoingHalf dayHalber Tag1-5 Tage
Participantsdifferent
2-203-125-204-12
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
Chat Transcript, Action Log, AutomationsLeverage Map, Action StrategySimulation Notes, Gaps List, Updated RunbooksLogic Model, Change Objectives, Intervention Components, Evaluation Plan
Tagsno overlap
CollaborationEngineeringIncident
Systems thinkingChangeStrategy
ResilienceOperationsIncident
ChangeSystems thinkingCapability
Add more methods