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 MoSCoW board with four columns and a visible release boundary.
Delivery
MoSCoW
Value Stream Mapping workspace showing the question, observations, and next decision.
Delivery
Value Stream Mapping
Paper illustration for ABC Analysis
Operations
ABC Analysis
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
Purposedifferent
When a release carries too many demands and priorities are only ever negotiated, MoSCoW creates clear boundaries for the next cut. Must, Should, Could, and Won't make commitment, room for maneuver, and trade-off logic visible to everyone involved.When delivery work dissolves into wait times, handoffs, and hidden effort, Value Stream Mapping makes the actual flow visible. The method exposes bottlenecks, idle time, and feedback loops so lead time and improvement levers become tangible.With many similar objects of differing economic significance, the method prioritizes effort by effect. It separates what needs regular steering from what rarely needs attention.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
LowMediumLowLow
Timedifferent
30-90 min1-3 h30-60 min30-120 min
Participantsdifferent
3-124-101-52-6
Formatdifferent
Workshop + asyncWorkshopAsyncWorkshop
Outputdifferent
Prioritized Backlog, Release Scope, Tradeoff NotesCurrent-state map, Future-state map, Bottleneck listABC Classification, Focus Rules, Control ListObservation Notes, Improvement Ideas
Tagsno overlap
PrioritizationScopeDecision
LeanFlowWasteDelivery
PrioritizationOperationsPortfolio
LeanObservationProcessOperations
Add more methods