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
Paper illustration for DACI
Decision Making
DACI
Paper illustration for OODA Loop.
Decision Making
OODA Loop
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
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 cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated.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.In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving.
Complexitydifferent
MediumLowMediumLow
Timedifferent
30-90 min30-60 min15-60 min je Zyklus45-90 min
Participantsdifferent
3-122-101-83-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Postmortem Doc, Action Items, TimelineDACI Matrix, Decision Owner, Decision LogSituation Assessment, Decision Loop, Action UpdatesForce Field Map, Change Levers, Risk Notes
Tagsno overlap
Site Reliability EngineeringIncidentLearningReliability
DecisionRolesGovernanceAlignment
DecisionChangeLearningStrategy
ChangeDecisionStrategy
Add more methods