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 for OODA Loop.
Decision Making
OODA Loop
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
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
Purposedifferent
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 a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.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.
Complexitydifferent
MediumLowLowLow
Timedifferent
15-60 min je Zyklus30-60 min45-90 minUp to 3 hours for a one-month Sprint; shorter Sprints are usually shorter
Participantsdifferent
1-83-123-12Scrum Team
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Situation Assessment, Decision Loop, Action UpdatesStart Stop Continue Board, Improvement ActionsForce Field Map, Change Levers, Risk NotesImprovement actions, Team agreements
Tagsno overlap
DecisionChangeLearningStrategy
RetrospectiveImprovementTeamReflection
ChangeDecisionStrategy
RetrospectiveImprovementLearning
Add more methods