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
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
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 preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic.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
LowHighLow
Timedifferent
20-60 minHalber Tag45-90 min
Participantsdifferent
1-45-203-12
Formatdifferent
AsyncWorkshopWorkshop
Outputdifferent
Runbook, Checklist, Escalation PathSimulation Notes, Gaps List, Updated RunbooksForce Field Map, Change Levers, Risk Notes
Tagsno overlap
OperationsReliabilityDocumentation
ResilienceOperationsIncident
ChangeDecisionStrategy
Add more methods

Often compared together

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

Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration for OODA Loop.
Decision Making
OODA Loop
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Anonymous individual judgments pass through feedback loops to form a distribution.
Decision Making
Delphi Method