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
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
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 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 team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.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.
Complexitysame
LowLowLow
Timedifferent
45-90 min30-60 minUp to 3 hours for a one-month Sprint; shorter Sprints are usually shorter
Participantsdifferent
3-123-12Scrum Team
Formatsame
WorkshopWorkshopWorkshop
Outputdifferent
Force Field Map, Change Levers, Risk NotesStart Stop Continue Board, Improvement ActionsImprovement actions, Team agreements
Tagsno overlap
ChangeDecisionStrategy
RetrospectiveImprovementTeamReflection
RetrospectiveImprovementLearning
Add more methods

Often compared together

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

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 for OODA Loop.
Decision Making
OODA Loop
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective