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 DIBB with its method-specific working model.
Product Strategy
DIBB
Paper illustration of KPI Tree with its method-specific working model.
Product Strategy
KPI Tree
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Paper illustration for OODA Loop.
Decision Making
OODA Loop
Purposedifferent
DIBB helps clarify target groups, value, goals, and priorities by making the logic behind a decision explicit. It captures results as a DIBB document, belief list, bet list, and learning report.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 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
LowMediumLowMedium
Timedifferent
1-2 h90-180 min initial, dann laufend45-90 min15-60 min je Zyklus
Participantsdifferent
2-83-83-121-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
DIBB document, Belief list, Bet list, Learning reportKPI Tree, Owner ListForce Field Map, Change Levers, Risk NotesSituation Assessment, Decision Loop, Action Updates
Tags1 shared
StrategyDecisionAssumptionsHypothesis
MetricsStrategyAlignmentMeasurement
ChangeDecisionStrategy
DecisionChangeLearningStrategy
Add more methods