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 Feynman Technique | ![]() Architecture Architecture Decision Record | ![]() Knowledge Modeling Knowledge Mapping | ![]() Knowledge Modeling IBIS |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | IBIS structures thinking about complex questions as a sequence of issues, ideas, and arguments. The method keeps discussions open without forcing them into premature consensus. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 20-60 min | 15-45 min | 1-3 h | 1-3 h |
Participantsdifferent | 1 | 1-3 | 3-12 | 2-8 |
Formatdifferent | Async | Async | Workshop | Workshop + async |
Outputdifferent | Plain-language Explanation, Knowledge Gaps, Study Notes | ADR File, Decision Log, Rationale | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Issue Map, Positions, Argument Notes |
Tagsno overlap | LearningKnowledgeUnderstanding | ArchitectureRationaleDocumentationGovernance | KnowledgeMappingRisk | RationaleKnowledgeDecision |



