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 of Leverage Points with its method-specific working model.
Systems Thinking
Leverage Points
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Paper illustration for OODA Loop.
Decision Making
OODA Loop
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.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.Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.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.
Complexitydifferent
MediumHighLowMedium
Timedifferent
As neededHalf day45-90 min15-60 min je Zyklus
Participantsdifferent
4-153-122-81-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Incident Log, Action Tracker, Stakeholder UpdatesLeverage Map, Action StrategyAssumption List, Critical Assumptions, Learning PlanSituation Assessment, Decision Loop, Action Updates
Tagsno overlap
IncidentOperationsReliability
Systems thinkingChangeStrategy
AssumptionsRiskDecisionDiscovery
DecisionChangeLearningStrategy
Add more methods