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 of Counter Metrics with its method-specific working model.
Product Strategy
Counter Metrics
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 a headline metric could mask side effects, it adds guardrail signals against unwanted outcomes. It connects customer value, product logic, and decision priorities. The result is captured as a counter-metric list and guardrail definitions.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
MediumLowLowMedium
Timedifferent
90-180 min initial, dann laufend30-60 min45-90 min15-60 min je Zyklus
Participantsdifferent
3-82-63-121-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
KPI Tree, Owner ListCounter Metric List, Guardrail DefinitionsForce Field Map, Change Levers, Risk NotesSituation Assessment, Decision Loop, Action Updates
Tags1 shared
MetricsStrategyAlignmentMeasurement
MetricsMeasurementStrategyExperiments
ChangeDecisionStrategy
DecisionChangeLearningStrategy
Add more methods