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 Ideal Days |  Knowledge Modeling Knowledge Mapping |  Systems Thinking Evaporating Cloud |  Knowledge Modeling Concept Mapping |
|---|---|---|---|---|
Purposedifferent | When effort needs to be thought of as real working time, it offers a simple common denominator for comparison. It sorts work by value, risk, and delivery ability. The result is captured as Ideal Day Estimates, Assumption Notes, and Capacity Caveats. | Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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 | Low | Medium | Medium | Medium |
Timedifferent | 15-60 min | 1-3 h | 60-120 min | 1-2 h |
Participantsdifferent | 2-9 | 3-12 | 2-8 | 1-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Ideal Day Estimates, Assumption Notes, Capacity Caveats | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Concept Map, Relationship Labels, Knowledge Gaps |
Tagsno overlap | EstimationEffortAgile | KnowledgeMappingRisk | Theory of ConstraintsAssumptionsSystems thinking | KnowledgeConceptsMappingSensemaking |