View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Systems Thinking Evaporating Cloud | ![]() Systems Thinking Systems Mapping | ![]() Knowledge Modeling Knowledge Mapping | ![]() Decision Making Assumption Surfacing |
|---|---|---|---|---|
Purposedifferent | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | Systems Mapping arranges elements, relationships, and boundaries so a complex field becomes legible at a glance. The overview stabilizes the overall picture before detail work or steering begins. | 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. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 60-120 min | 1-3 h | 1-3 h | 45-90 min |
Participantsdifferent | 2-8 | 3-12 | 3-12 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | System Map, Dependencies, Leverage Points | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | Systems thinkingMappingBoundariesChange | KnowledgeMappingRisk | AssumptionsRiskDecisionDiscovery |



