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
Paper illustration for OODA Loop.
Decision Making
OODA Loop
Anonymous individual judgments pass through feedback loops to form a distribution.
Decision Making
Delphi Method
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 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.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
LowMediumMediumHigh
Timedifferent
45-90 minAs needed15-60 min je Zyklus1-4 Wochen
Participantsdifferent
3-124-151-86-30 Experten
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Force Field Map, Change Levers, Risk NotesIncident Log, Action Tracker, Stakeholder UpdatesSituation Assessment, Decision Loop, Action UpdatesExpert Forecast, Consensus Range, Assumption Notes
Tagsno overlap
ChangeDecisionStrategy
IncidentOperationsReliability
DecisionChangeLearningStrategy
ForecastingExpertsDecisionStrategy
Add more methods