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 for Sailboat Retrospective
Agile
Sailboat Retrospective
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
Purposedifferent
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.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.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.After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement.
Complexitydifferent
LowLowMediumLow
Timedifferent
45-90 min30-60 min1-3 h20-45 min
Participantsdifferent
4-123-123-103-12
Formatdifferent
WorkshopWorkshopWorkshopWorkshop + async
Outputdifferent
Sailboat Board, Risks, Improvement ActionsStart Stop Continue Board, Improvement ActionsProcess Map, Handoff List, Improvement BacklogLessons learned, Action items, Event summary
Tags1 shared
RetrospectiveTeamImprovement
RetrospectiveImprovementTeamReflection
ProcessOperationsImprovement
LearningOperationsImprovement
Add more methods