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
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Purposedifferent
For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access.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 a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.
Complexitysame
LowLowLow
Timedifferent
20-60 min45-90 min15-30 min
Participantsdifferent
1-43-122-6
Formatdifferent
AsyncWorkshopWorkshop
Outputdifferent
Runbook, Checklist, Escalation PathForce Field Map, Change Levers, Risk NotesRoot cause notes, Countermeasures
Tagsno overlap
OperationsReliabilityDocumentation
ChangeDecisionStrategy
Root causeIncidentLeanProblem solving
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration for Kepner-Tregoe
Operations
Kepner-Tregoe
A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration for OODA Loop.
Decision Making
OODA Loop