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
Paper illustration for OODA Loop.
Decision Making
OODA Loop
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Anonymous individual judgments pass through feedback loops to form a distribution.
Decision Making
Delphi Method
Paper illustration for Incident Timeline Analysis.
DevOps
Incident Timeline Analysis
Purposedifferent
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.After an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures.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.For an incident with an unclear sequence, the method makes the timeline precisely visible. It separates perception, reaction, and delay so cause and effect become more clearly readable.
Complexitydifferent
MediumMediumHighMedium
Timedifferent
15-60 min je Zyklus30-90 min1-4 Wochen60-180 min
Participantsdifferent
1-83-126-30 Experten3-10
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Situation Assessment, Decision Loop, Action UpdatesPostmortem Doc, Action Items, TimelineExpert Forecast, Consensus Range, Assumption NotesIncident Timeline, Evidence Log, Delay Analysis, Improvement Actions
Tagsno overlap
DecisionChangeLearningStrategy
Site Reliability EngineeringIncidentLearningReliability
ForecastingExpertsDecisionStrategy
IncidentTimelineSite Reliability Engineering
Add more methods