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 | ![]() Decision Making Assumption Surfacing | ![]() Knowledge Modeling Concept 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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | 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. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | laufend | 45-90 min | 1-2 h |
Participantsdifferent | 2-12 | 2-8 | 1-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Throughput Data, Flow Forecast, Slicing Rules | Assumption List, Critical Assumptions, Learning Plan | Concept Map, Relationship Labels, Knowledge Gaps |
Tagsno overlap | EstimationForecastingFlow | AssumptionsRiskDecisionDiscovery | KnowledgeConceptsMappingSensemaking |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






