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
The Scrum Team inspects people, interactions, processes, tools, and the Definition of Done, then agrees on a few testable improvements.
Agile
Sprint Retrospective
Paper illustration for OODA Loop.
Decision Making
OODA Loop
Paper illustration of DIBB with its method-specific working model.
Product Strategy
DIBB
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.When a sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together.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
LowLowMediumLow
Timedifferent
45-90 minUp to 3 hours for a one-month Sprint; shorter Sprints are usually shorter15-60 min je Zyklus1-2 h
Participantsdifferent
3-12Scrum Team1-82-8
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Force Field Map, Change Levers, Risk NotesImprovement actions, Team agreementsSituation Assessment, Decision Loop, Action UpdatesDIBB document, Belief list, Bet list, Learning report
Tagsno overlap
ChangeDecisionStrategy
RetrospectiveImprovementLearning
DecisionChangeLearningStrategy
StrategyDecisionAssumptionsHypothesis
Add more methods