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 a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
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 Barrier Analysis with its method-specific working model.
Operations
Barrier Analysis
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective
Purposedifferent
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 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.For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions.When a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture.
Complexitydifferent
LowLowMediumLow
Timedifferent
30-60 min45–75 min2-4 h45-90 min
Participantsdifferent
3-12Team members involved2-64-12
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Start Stop Continue Board, Improvement Actions4Ls Board, Learning Themes, Improvement ActionsBarrier Inventory, Failure Analysis per Barrier, Action BacklogSailboat Board, Risks, Improvement Actions
Tagsno overlap
RetrospectiveImprovementTeamReflection
RetrospectiveLearningReflectionTeam
Root causeSafetyIncident
RetrospectiveTeamImprovement
Add more methods