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 |  Delivery RAID Log |
|---|---|---|---|---|
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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 20-60 min | 15-45 min | 1-3 h | 30 min Setup, dann laufend |
Participantsdifferent | 1 | 1-3 | 3-12 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Async | Async | Workshop | Async |
Outputdifferent | Plain-language Explanation, Knowledge Gaps, Study Notes | ADR File, Decision Log, Rationale | Knowledge Map, Critical Knowledge Areas, Transfer Plan | RAID Log, Status Report Source |
Tagsno overlap | LearningKnowledgeUnderstanding | ArchitectureRationaleDocumentationGovernance | KnowledgeMappingRisk | RiskTrackingStakeholdersGovernance |