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 Theory of Constraints.
Operations
Theory of Constraints
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
Value Stream Mapping workspace showing the question, observations, and next decision.
Delivery
Value Stream Mapping
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Purposedifferent
For a system that does not get faster despite effort, the method directs attention to the bottleneck. It concentrates improvement on the point that actually limits throughput.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 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 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
HighLowMediumMedium
Timedifferent
2-4 h Analyse, laufend30-120 min1-3 h1-3 h
Participantsdifferent
3-122-64-103-10
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Constraint Map, Improvement Plan, Flow MetricsObservation Notes, Improvement IdeasCurrent-state map, Future-state map, Bottleneck listProcess Map, Handoff List, Improvement Backlog
Tagsno overlap
OperationsConstraintsFlowImprovement
LeanObservationProcessOperations
LeanFlowWasteDelivery
ProcessOperationsImprovement
Add more methods