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 of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
Purposedifferent
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.During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once.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.
Complexitydifferent
LowMediumHigh
Timedifferent
45-90 minAs neededHalber Tag
Participantsdifferent
3-124-155-20
Formatdifferent
WorkshopWorkshop + asyncWorkshop
Outputdifferent
Force Field Map, Change Levers, Risk NotesIncident Log, Action Tracker, Stakeholder UpdatesSimulation Notes, Gaps List, Updated Runbooks
Tagsno overlap
ChangeDecisionStrategy
IncidentOperationsReliability
ResilienceOperationsIncident
Add more methods

Often compared together

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

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
Paper illustration of DIBB with its method-specific working model.
Product Strategy
DIBB