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
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
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.When there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions.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
LowLowMediumLow
Timedifferent
30-60 min30-120 min1-3 h45-90 min
Participantsdifferent
3-122-63-104-12
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Start Stop Continue Board, Improvement ActionsObservation Notes, Improvement IdeasProcess Map, Handoff List, Improvement BacklogSailboat Board, Risks, Improvement Actions
Tagsno overlap
RetrospectiveImprovementTeamReflection
LeanObservationProcessOperations
ProcessOperationsImprovement
RetrospectiveTeamImprovement
Add more methods