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
Causal Loop Diagram workspace showing the question, observations, and next decision.
Systems Thinking
Causal Loop Diagram
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.A Causal Loop Diagram makes feedback, reinforcement, and balance in a system legible. It uncovers side effects and self-reinforcement that stay hidden in linear explanations.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
MediumMediumMediumLow
Timedifferent
15-60 min je Zyklus30-90 min1-3 h45-90 min
Participantsdifferent
1-83-122-83-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Situation Assessment, Decision Loop, Action UpdatesPostmortem Doc, Action Items, TimelineCausal Loop Diagram, Feedback Notes, Leverage PointsForce Field Map, Change Levers, Risk Notes
Tagsno overlap
DecisionChangeLearningStrategy
Site Reliability EngineeringIncidentLearningReliability
FeedbackSystems thinkingCausalityDynamics
ChangeDecisionStrategy
Add more methods