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
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 the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Paper illustration of DIBB with its method-specific working model.
Product Strategy
DIBB
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Purposedifferent
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.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.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.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
LowLowLowLow
Timedifferent
45–75 min45-90 min1-2 h30-60 min
Participantsdifferent
Team members involved3-122-83-12
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
4Ls Board, Learning Themes, Improvement ActionsForce Field Map, Change Levers, Risk NotesDIBB document, Belief list, Bet list, Learning reportStart Stop Continue Board, Improvement Actions
Tagsno overlap
RetrospectiveLearningReflectionTeam
ChangeDecisionStrategy
StrategyDecisionAssumptionsHypothesis
RetrospectiveImprovementTeamReflection
Add more methods