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 Systems Mapping | ![]() Decision Making Assumption Surfacing | ![]() Knowledge Modeling Knowledge Mapping | ![]() Systems Thinking Evaporating Cloud |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 1-3 h | 45-90 min | 1-3 h | 60-120 min |
Participantsdifferent | 3-12 | 2-8 | 3-12 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | System Map, Dependencies, Leverage Points | Assumption List, Critical Assumptions, Learning Plan | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments |
Tagsno overlap | Systems thinkingMappingBoundariesChange | AssumptionsRiskDecisionDiscovery | KnowledgeMappingRisk | Theory of ConstraintsAssumptionsSystems thinking |



