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
A paper-based illustration representing WSJF with its core stages and visible working result.
Agile
WSJF
Process Mapping method illustration showing its working structure
Operations
Process Mapping
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
Purposedifferent
When many tasks compete for the same capacity, it orders work by economic impact. It makes time lost, benefit, and effort comparable together.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.For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.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.
Complexitydifferent
HighMediumLowLow
Timedifferent
45-90 min1-3 h15-30 min30-120 min
Participantsdifferent
3-103-102-62-6
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Ranked Backlog, Cost-of-Delay AssumptionsProcess Map, Handoff List, Improvement BacklogRoot cause notes, CountermeasuresObservation Notes, Improvement Ideas
Tagsno overlap
LeanEconomicsSequencePrioritization
ProcessOperationsImprovement
Root causeIncidentLeanProblem solving
LeanObservationProcessOperations
Add more methods