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
Paper illustration for OODA Loop.
Decision Making
OODA Loop
Paper illustration for Incident Timeline Analysis.
DevOps
Incident Timeline Analysis
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.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.For an incident with an unclear sequence, the method makes the timeline precisely visible. It separates perception, reaction, and delay so cause and effect become more clearly readable.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 min15-60 min je Zyklus60-180 min1-4 Wochen
Participantsdifferent
3-121-83-106-30 Experten
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Force Field Map, Change Levers, Risk NotesSituation Assessment, Decision Loop, Action UpdatesIncident Timeline, Evidence Log, Delay Analysis, Improvement ActionsExpert Forecast, Consensus Range, Assumption Notes
Tagsno overlap
ChangeDecisionStrategy
DecisionChangeLearningStrategy
IncidentTimelineSite Reliability Engineering
ForecastingExpertsDecisionStrategy
Add more methods