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
A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls Retrospective
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
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 should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time.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.
Complexitysame
LowLowLow
Timedifferent
45-90 min45–75 min30-60 min
Participantsdifferent
3-12Team members involved3-12
Formatsame
WorkshopWorkshopWorkshop
Outputdifferent
Force Field Map, Change Levers, Risk Notes4Ls Board, Learning Themes, Improvement ActionsStart Stop Continue Board, Improvement Actions
Tagsno overlap
ChangeDecisionStrategy
RetrospectiveLearningReflectionTeam
RetrospectiveImprovementTeamReflection
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration for OODA Loop.
Decision Making
OODA Loop
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective
The Scrum Team inspects people, interactions, processes, tools, and the Definition of Done, then agrees on a few testable improvements.
Agile
Sprint Retrospective