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 KPI Tree with its method-specific working model.
Product Strategy
KPI Tree
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Paper illustration for OODA Loop.
Decision Making
OODA Loop
Purposedifferent
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 statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on.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.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
90-180 min initial, dann laufend1-3 h45-90 min15-60 min je Zyklus
Participantsdifferent
3-81-83-121-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
KPI Tree, Owner ListArgument Map, Evidence Gaps, Decision RationaleForce Field Map, Change Levers, Risk NotesSituation Assessment, Decision Loop, Action Updates
Tagsno overlap
MetricsStrategyAlignmentMeasurement
SensemakingDecisionRationale
ChangeDecisionStrategy
DecisionChangeLearningStrategy
Add more methods