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
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration for OODA Loop.
Decision Making
OODA Loop
Paper illustration of Leverage Points with its method-specific working model.
Systems Thinking
Leverage Points
Paper illustration for Learning Review.
Operations
Learning Review
Purposedifferent
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.In dynamic situations, decisions become outdated faster than they can be prepared. The OODA Loop holds observing, orienting, deciding, and acting together as a recurring rhythm so reaction does not slide into inertia.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.After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights.
Complexitydifferent
MediumMediumHighMedium
Timedifferent
As needed15-60 min je ZyklusHalf day1-3 h
Participantsdifferent
4-151-83-123-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Incident Log, Action Tracker, Stakeholder UpdatesSituation Assessment, Decision Loop, Action UpdatesLeverage Map, Action StrategyLearning Review Notes, System Factors, Improvement Actions
Tagsno overlap
IncidentOperationsReliability
DecisionChangeLearningStrategy
Systems thinkingChangeStrategy
LearningRetrospectiveIncidentOperations
Add more methods