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
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Anonymous individual judgments pass through feedback loops to form a distribution.
Decision Making
Delphi Method
Purposedifferent
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 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.When knowledge is distributed and direct dominance should be avoided, groups quickly fall under the sway of their opinion leaders. The Delphi Method gathers assessments iteratively and gradually brings expert judgments closer together.
Complexitydifferent
MediumLowHigh
Timedifferent
As needed45-90 min1-4 Wochen
Participantsdifferent
4-153-126-30 Experten
Formatdifferent
Workshop + asyncWorkshopAsync
Outputdifferent
Incident Log, Action Tracker, Stakeholder UpdatesForce Field Map, Change Levers, Risk NotesExpert Forecast, Consensus Range, Assumption Notes
Tagsno overlap
IncidentOperationsReliability
ChangeDecisionStrategy
ForecastingExpertsDecisionStrategy
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
Paper illustration of DIBB with its method-specific working model.
Product Strategy
DIBB