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
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
Paper illustration for OODA Loop.
Decision Making
OODA Loop
Anonymous individual judgments pass through feedback loops to form a distribution.
Decision Making
Delphi Method
Purposedifferent
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.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.When knowledge is distributed and direct dominance should be avoided, groups quickly fall under the sway of their opinion leaders. The Delphi Method gathers assessments iteratively and gradually brings expert judgments closer together.
Complexitydifferent
HighMediumHigh
Timedifferent
Halber Tag15-60 min je Zyklus1-4 Wochen
Participantsdifferent
5-201-86-30 Experten
Formatdifferent
WorkshopWorkshop + asyncAsync
Outputdifferent
Simulation Notes, Gaps List, Updated RunbooksSituation Assessment, Decision Loop, Action UpdatesExpert Forecast, Consensus Range, Assumption Notes
Tagsno overlap
ResilienceOperationsIncident
DecisionChangeLearningStrategy
ForecastingExpertsDecisionStrategy
Add more methods

Often compared together

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

Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Paper illustration for Learning Review.
Operations
Learning Review
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