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 |  Knowledge Modeling Feynman Technique |  Systems Thinking Systems Mapping |  Knowledge Modeling Concept Mapping |
|---|---|---|---|---|
Purposedifferent | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | The Feynman Technique checks understanding by explaining a topic so that it stays easy for others to understand. It makes knowledge gaps visible before they become costly in everyday work. | 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. | 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 | Medium |
Timedifferent | 60-120 min | 20-60 min | 1-3 h | 1-2 h |
Participantsdifferent | 2-8 | 1 | 3-12 | 1-8 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop + async |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Plain-language Explanation, Knowledge Gaps, Study Notes | System Map, Dependencies, Leverage Points | Concept Map, Relationship Labels, Knowledge Gaps |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | LearningKnowledgeUnderstanding | Systems thinkingMappingBoundariesChange | KnowledgeConceptsMappingSensemaking |