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 arc42 | ![]() Architecture Architecture Decision Record | ![]() 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. | 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. | 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. | 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 | Low | Medium |
Timedifferent | 20-60 min | 1-2 Tage | 15-45 min | 1-3 h |
Participantsdifferent | 1 | 1-4 | 1-3 | 2-8 |
Formatdifferent | Async | Workshop + async | Async | Workshop + async |
Outputdifferent | Plain-language Explanation, Knowledge Gaps, Study Notes | Architecture Document, Context View, Runtime View, Deployment View | ADR File, Decision Log, Rationale | Issue Map, Positions, Argument Notes |
Tagsno overlap | LearningKnowledgeUnderstanding | ArchitectureDocumentationCommunication | ArchitectureRationaleDocumentationGovernance | RationaleKnowledgeDecision |



