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 KPI Tree with its method-specific working model.
Product Strategy
KPI Tree
Paper illustration of Goal Question Metric with its method-specific working model.
Engineering
Goal Question Metric
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.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.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.
Complexitydifferent
LowMediumMediumMedium
Timedifferent
45-90 min15-60 min je Zyklus90-180 min initial, dann laufend90-180 min
Participantsdifferent
3-121-83-83-6
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Force Field Map, Change Levers, Risk NotesSituation Assessment, Decision Loop, Action UpdatesKPI Tree, Owner ListGQM Table, Metric Profiles
Tagsno overlap
ChangeDecisionStrategy
DecisionChangeLearningStrategy
MetricsStrategyAlignmentMeasurement
MetricsMeasurementEngineeringAlignment
Add more methods