View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Decision Making Three-Point Estimation |  Knowledge Modeling Concept Mapping |  Systems Thinking Evaporating Cloud |  Agile NoEstimates |
|---|---|---|---|---|
Purposedifferent | A single estimate for effort, time, or risk often looks too smooth for the real uncertainty behind it. It separates options, evaluation criteria, and open risks. The result is captured as a Three-Point Estimate, Risk Range, and Assumption Notes. | Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 10-30 min je Item | 1-2 h | 60-120 min | laufend |
Participantsdifferent | 1-8 | 1-8 | 2-8 | 2-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Three-Point Estimate, Risk Range, Assumption Notes | Concept Map, Relationship Labels, Knowledge Gaps | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Throughput Data, Flow Forecast, Slicing Rules |
Tagsno overlap | EstimationUncertaintyForecasting | KnowledgeConceptsMappingSensemaking | Theory of ConstraintsAssumptionsSystems thinking | EstimationForecastingFlow |