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
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
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.After an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures.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 min30-90 min15-60 min je Zyklus1-4 Wochen
Participantsdifferent
3-123-121-86-30 Experten
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Force Field Map, Change Levers, Risk NotesPostmortem Doc, Action Items, TimelineSituation Assessment, Decision Loop, Action UpdatesExpert Forecast, Consensus Range, Assumption Notes
Tagsno overlap
ChangeDecisionStrategy
Site Reliability EngineeringIncidentLearningReliability
DecisionChangeLearningStrategy
ForecastingExpertsDecisionStrategy
Add more methods