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
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Gap Analysis method illustration showing its working structure
Business Strategy
GAP Analysis
Paper illustration for OODA Loop.
Decision Making
OODA Loop
Purposedifferent
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.In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures.GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing.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
MediumLowMediumMedium
Timedifferent
30-90 min20–45 min1-3 h15-60 min je Zyklus
Participantsdifferent
3-12Small cross-functional group2-81-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Postmortem Doc, Action Items, TimelineRisk list, Mitigation plan, Assumption logGap Matrix, Action Plan, Risk NotesSituation Assessment, Decision Loop, Action Updates
Tagsno overlap
Site Reliability EngineeringIncidentLearningReliability
RiskDecisionFailurePlanning
StrategyAnalysisPlanning
DecisionChangeLearningStrategy
Add more methods