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
Paper illustration for Learning Review.
Operations
Learning Review
Process Mapping method illustration showing its working structure
Operations
Process Mapping
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.After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights.With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots.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
LowMediumMediumLow
Timedifferent
30-60 min1-3 h1-3 h45-90 min
Participantsdifferent
3-123-103-104-12
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Start Stop Continue Board, Improvement ActionsLearning Review Notes, System Factors, Improvement ActionsProcess Map, Handoff List, Improvement BacklogSailboat Board, Risks, Improvement Actions
Tagsno overlap
RetrospectiveImprovementTeamReflection
LearningRetrospectiveIncidentOperations
ProcessOperationsImprovement
RetrospectiveTeamImprovement
Add more methods