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 Bottleneck Analysis.
Operations
Bottleneck Analysis
Paper illustration for Theory of Constraints.
Operations
Theory of Constraints
Paper illustration for NoEstimates.
Agile
NoEstimates
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Purposedifferent
For a flow that backs up at one point, the method looks for the capacity limit with the greatest leverage. It explains why extra effort elsewhere barely improves throughput.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 estimating slows a team down more than it helps, it shifts the focus to flow, small slices, and real lead time. It sorts work by value, risk, and delivery ability. The result is captured as Throughput Data, Flow Forecast, and Slicing Rules.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
MediumHighMediumMedium
Timedifferent
1-3 h2-4 h Analyse, laufendlaufend1-3 h
Participantsdifferent
3-83-122-123-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Bottleneck Map, Flow Metrics, Improvement Options, Follow-up MeasuresConstraint Map, Improvement Plan, Flow MetricsThroughput Data, Flow Forecast, Slicing RulesProcess Map, Handoff List, Improvement Backlog
Tagsno overlap
FlowMeasurementConstraints
OperationsConstraintsFlowImprovement
EstimationForecastingFlow
ProcessOperationsImprovement
Add more methods