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
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
Paper illustration for OODA Loop.
Decision Making
OODA Loop
Paper illustration for Trade-off Analysis.
Decision Making
Trade-off Analysis
Purposedifferent
For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access.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.With limited resources, quality, speed, cost, and risk almost always compete with each other. Trade-off Analysis makes these tensions explicit and prevents decisions from producing hidden side effects.
Complexitydifferent
LowMediumMedium
Timedifferent
20-60 min15-60 min je Zyklus45-120 min
Participantsdifferent
1-41-82-8
Formatdifferent
AsyncWorkshop + asyncWorkshop + async
Outputdifferent
Runbook, Checklist, Escalation PathSituation Assessment, Decision Loop, Action UpdatesTrade-off Matrix, Criteria List, Decision Rationale, Accepted Downsides
Tagsno overlap
OperationsReliabilityDocumentation
DecisionChangeLearningStrategy
TradeoffsDecisionCriteriaOptions
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration of a decision table with criteria rows, weighted ratings, and a narrowly leading alternative.
Decision Making
Decision Matrix
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem