View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Knowledge Mapping |  Systems Thinking Evaporating Cloud |  Architecture Architecture Decision Record |  Product Discovery Assumption Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-3 h | 60-120 min | 15-45 min | 45-60 min |
Participantsdifferent | 3-12 | 2-8 | 1-3 | 2-8 |
Formatdifferent | Workshop | Workshop | Async | Workshop + async |
Outputdifferent | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | ADR File, Decision Log, Rationale | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | KnowledgeMappingRisk | Theory of ConstraintsAssumptionsSystems thinking | ArchitectureRationaleDocumentationGovernance | AssumptionsRiskExperimentsValidation |