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 Dual Track Agile with its method-specific working model.
Product Discovery
Dual-Track Agile
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 DIBB with its method-specific working model.
Product Strategy
DIBB
Purposedifferent
When uncertainty and delivery run in parallel, it separates learning work from implementation while keeping both connected. It prevents unvalidated ideas from falling directly into the delivery stream.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.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.
Complexitydifferent
MediumLowMediumLow
Timedifferent
Laufend, Wochen bis Monate45-90 min15-60 min je Zyklus1-2 h
Participantsdifferent
4-103-121-82-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Discovery Backlog, Delivery Backlog, Experiment-Ergebnisse, Validierte StoriesForce Field Map, Change Levers, Risk NotesSituation Assessment, Decision Loop, Action UpdatesDIBB document, Belief list, Bet list, Learning report
Tagsno overlap
AgileDiscoveryDelivery
ChangeDecisionStrategy
DecisionChangeLearningStrategy
StrategyDecisionAssumptionsHypothesis
Add more methods