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 of Family Tree Analysis with its method-specific working model.
Operations
Family Tree Analysis
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 a series of incidents with a similar pattern, the method arranges individual events as branches of a common origin. It makes visible which conditions keep recurring.
Complexitydifferent
LowMediumMedium
Timedifferent
45-90 min15-60 min je Zyklus2-4 h
Participantsdifferent
3-121-82-6
Formatdifferent
WorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Force Field Map, Change Levers, Risk NotesSituation Assessment, Decision Loop, Action UpdatesFamily Tree Diagram, Pattern Notes, Systemic Measures
Tagsno overlap
ChangeDecisionStrategy
DecisionChangeLearningStrategy
Root causePatternsIncidentSystemic
Add more methods

Often compared together

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

Paper illustration of MORT Analysis with its method-specific working model.
Operations
MORT Analysis
Paper illustration of Barrier Analysis with its method-specific working model.
Operations
Barrier Analysis
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem