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 for OODA Loop.
Decision Making
OODA Loop
Paper illustration of KPI Tree with its method-specific working model.
Product Strategy
KPI Tree
Paper illustration of a branching impact map with a Why goal at the root, actor circles, How behavior changes and What options.
Product Strategy
Impact Mapping
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Purposedifferent
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 metrics across the organization drift apart, it arranges drivers and effects under one shared logic. It connects customer value, product logic, and decision priorities. The result is captured as a KPI tree and owner list.When a goal needs to be connected to several possible paths, it shows chains of impact instead of feature lists. It connects business goal, behavior change, and measures.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.
Complexitydifferent
MediumMediumMediumLow
Timedifferent
15-60 min je Zyklus90-180 min initial, dann laufend45-90 min45-90 min
Participantsdifferent
1-83-83-83-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Situation Assessment, Decision Loop, Action UpdatesKPI Tree, Owner ListImpact Map, Outcome Hypotheses, Delivery OptionsForce Field Map, Change Levers, Risk Notes
Tags1 shared
DecisionChangeLearningStrategy
MetricsStrategyAlignmentMeasurement
OutcomesStrategyBehaviorPlanning
ChangeDecisionStrategy
Add more methods