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
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 Learning Review.
Operations
Learning Review
The Scrum Team inspects people, interactions, processes, tools, and the Definition of Done, then agrees on a few testable improvements.
Agile
Sprint Retrospective
Purposedifferent
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.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.When a sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together.
Complexitydifferent
LowMediumMediumLow
Timedifferent
30-120 min1-3 h1-3 hUp to 3 hours for a one-month Sprint; shorter Sprints are usually shorter
Participantsdifferent
2-63-103-10Scrum Team
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Observation Notes, Improvement IdeasProcess Map, Handoff List, Improvement BacklogLearning Review Notes, System Factors, Improvement ActionsImprovement actions, Team agreements
Tagsno overlap
LeanObservationProcessOperations
ProcessOperationsImprovement
LearningRetrospectiveIncidentOperations
RetrospectiveImprovementLearning
Add more methods