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 of Goal Question Metric with its method-specific working model.
Engineering
Goal Question Metric
Paper illustration of KPI Tree with its method-specific working model.
Product Strategy
KPI Tree
Paper illustration for OODA Loop.
Decision Making
OODA Loop
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.Helps clarify technical problems, hypotheses, and next steps in concrete terms. It breaks a technical problem into testable parts. The result is captured as a GQM table and metric briefs.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.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
LowMediumMediumMedium
Timedifferent
45-90 min90-180 min90-180 min initial, dann laufend15-60 min je Zyklus
Participantsdifferent
3-123-63-81-8
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Force Field Map, Change Levers, Risk NotesGQM Table, Metric ProfilesKPI Tree, Owner ListSituation Assessment, Decision Loop, Action Updates
Tagsno overlap
ChangeDecisionStrategy
MetricsMeasurementEngineeringAlignment
MetricsStrategyAlignmentMeasurement
DecisionChangeLearningStrategy
Add more methods