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
Paper illustration for Incident Timeline Analysis.
DevOps
Incident Timeline Analysis
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Paper illustration for Causal Factor Analysis.
Operations
Causal Factor 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.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.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.For an event with a complicated course, the method breaks down the contributing factors along the timeline. It shows how conditions, decisions, and reactions together produce a course of events.
Complexitydifferent
MediumMediumLowHigh
Timedifferent
15-60 min je Zyklus60-180 min45-90 min2-6 h
Participantsdifferent
1-83-103-123-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Situation Assessment, Decision Loop, Action UpdatesIncident Timeline, Evidence Log, Delay Analysis, Improvement ActionsForce Field Map, Change Levers, Risk NotesEvent Timeline, Causal Factor Chart, Cause List, Corrective Actions
Tagsno overlap
DecisionChangeLearningStrategy
IncidentTimelineSite Reliability Engineering
ChangeDecisionStrategy
CausalityIncidentRoot causeTimeline
Add more methods