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 NoEstimates.
Agile
NoEstimates
Paper illustration for Theory of Constraints.
Operations
Theory of Constraints
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
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.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.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
MediumHighLowMedium
Timedifferent
laufend2-4 h Analyse, laufend30-120 min1-3 h
Participantsdifferent
2-123-122-63-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Throughput Data, Flow Forecast, Slicing RulesConstraint Map, Improvement Plan, Flow MetricsObservation Notes, Improvement IdeasProcess Map, Handoff List, Improvement Backlog
Tagsno overlap
EstimationForecastingFlow
OperationsConstraintsFlowImprovement
LeanObservationProcessOperations
ProcessOperationsImprovement
Add more methods