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 review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
Paper illustration for Bottleneck Analysis.
Operations
Bottleneck Analysis
Paper illustration for NoEstimates.
Agile
NoEstimates
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Purposedifferent
After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement.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.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
LowMediumMediumMedium
Timedifferent
20-45 min1-3 hlaufend1-3 h
Participantsdifferent
3-123-82-123-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Lessons learned, Action items, Event summaryBottleneck Map, Flow Metrics, Improvement Options, Follow-up MeasuresThroughput Data, Flow Forecast, Slicing RulesProcess Map, Handoff List, Improvement Backlog
Tagsno overlap
LearningOperationsImprovement
FlowMeasurementConstraints
EstimationForecastingFlow
ProcessOperationsImprovement
Add more methods