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 of Leverage Points with its method-specific working model.
Systems Thinking
Leverage Points
Paper illustration for Intervention Mapping.
Systems Thinking
Intervention Mapping
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Purposedifferent
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.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
HighHighMedium
Timedifferent
Half day1-5 TageAs needed
Participantsdifferent
3-124-124-15
Formatdifferent
WorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Leverage Map, Action StrategyLogic Model, Change Objectives, Intervention Components, Evaluation PlanIncident Log, Action Tracker, Stakeholder Updates
Tagsno overlap
Systems thinkingChangeStrategy
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 of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Paper illustration for Future Reality Tree.
Systems Thinking
Future Reality Tree