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 CATWOE Analysis.
Systems Thinking
CATWOE Analysis
The Scrum Team inspects people, interactions, processes, tools, and the Definition of Done, then agrees on a few testable improvements.
Agile
Sprint Retrospective
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Purposedifferent
CATWOE structures a problem from six viewpoints and prevents too narrow a view of the situation. Different experiences of the system become comparably discussable this way.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.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.
Complexitydifferent
MediumLowLowMedium
Timedifferent
45-90 minUp to 3 hours for a one-month Sprint; shorter Sprints are usually shorter30-120 min1-3 h
Participantsdifferent
3-8Scrum Team2-63-10
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
CATWOE Canvas, Root Definition, Stakeholder Perspectives, ConstraintsImprovement actions, Team agreementsObservation Notes, Improvement IdeasProcess Map, Handoff List, Improvement Backlog
Tagsno overlap
Systems thinkingFramingStakeholders
RetrospectiveImprovementLearning
LeanObservationProcessOperations
ProcessOperationsImprovement
Add more methods