View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile NoEstimates |  Systems Thinking Iceberg Model |  Operations Bottleneck Analysis |
|---|---|---|---|
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. | The Iceberg Model separates visible events from patterns, structures, and mental models. This turns a single observation into a deeper understanding of why a problem keeps recurring. | 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. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | laufend | 30-60 min | 1-3 h |
Participantsdifferent | 2-12 | 2-10 | 3-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Throughput Data, Flow Forecast, Slicing Rules | Iceberg Worksheet, Pattern Notes, Intervention Ideas | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures |
Tagsno overlap | EstimationForecastingFlow | Systems thinkingRoot causePatterns | FlowMeasurementConstraints |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
