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 Concept Mapping |  Knowledge Modeling Teach-back |  Architecture arc42 |  Knowledge Modeling Feynman Technique |
|---|---|---|---|---|
Purposedifferent | 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. | Teach-back checks whether an explanation actually got through to the other person. The method makes misunderstandings visible early and strengthens shared understanding in advisory and learning situations. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-2 h | 5-20 min | 1-2 Tage | 20-60 min |
Participantsdifferent | 1-8 | 2-8 | 1-4 | 1 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Understanding Check, Clarification Notes, Learning Gaps | Architecture Document, Context View, Runtime View, Deployment View | Plain-language Explanation, Knowledge Gaps, Study Notes |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | LearningUnderstandingCommunication | ArchitectureDocumentationCommunication | LearningKnowledgeUnderstanding |