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 Starfish Retrospective
Agile
Starfish Retrospective
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
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
Purposedifferent
When improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued.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.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.
Complexitydifferent
LowLowLowMedium
Timedifferent
45-90 min30-120 min30-60 min1-3 h
Participantsdifferent
4-122-63-123-10
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Starfish Board, Practice Changes, ExperimentsObservation Notes, Improvement IdeasStart Stop Continue Board, Improvement ActionsProcess Map, Handoff List, Improvement Backlog
Tagsno overlap
RetrospectiveImprovementExperimentsTeam
LeanObservationProcessOperations
RetrospectiveImprovementTeamReflection
ProcessOperationsImprovement
Add more methods