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
Paper illustration for 8D Problem Solving.
Operations
8D Problem Solving
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field 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.For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly.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
MediumMediumHighLow
Timedifferent
15-60 min je Zyklus30-90 min1-6 Wochen45-90 min
Participantsdifferent
1-83-124-103-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Situation Assessment, Decision Loop, Action UpdatesPostmortem Doc, Action Items, Timeline8D Report, Containment Plan, Root Cause Evidence, Corrective Action PlanForce Field Map, Change Levers, Risk Notes
Tagsno overlap
DecisionChangeLearningStrategy
Site Reliability EngineeringIncidentLearningReliability
QualityProblem solvingRoot cause
ChangeDecisionStrategy
Add more methods