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
Anonymous individual judgments pass through feedback loops to form a distribution.
Decision Making
Delphi Method
Paper illustration for Learning Review.
Operations
Learning Review
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.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.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
HighHighMedium
Timedifferent
Halber Tag1-4 Wochen1-3 h
Participantsdifferent
5-206-30 Experten3-10
Formatdifferent
WorkshopAsyncWorkshop
Outputdifferent
Simulation Notes, Gaps List, Updated RunbooksExpert Forecast, Consensus Range, Assumption NotesLearning Review Notes, System Factors, Improvement Actions
Tagsno overlap
ResilienceOperationsIncident
ForecastingExpertsDecisionStrategy
LearningRetrospectiveIncidentOperations
Add more methods

Often compared together

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

Paper illustration for OODA Loop.
Decision Making
OODA Loop
A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls Retrospective
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