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 |  Delivery RAID Log |  Architecture arc42 |  Architecture Architecture Decision Record |
|---|---|---|---|---|
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. | 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. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 20-60 min | 30 min Setup, dann laufend | 1-2 Tage | 15-45 min |
Participantsdifferent | 1 | 1-3 maintaining, briefing for everyone | 1-4 | 1-3 |
Formatdifferent | Async | Async | Workshop + async | Async |
Outputdifferent | Plain-language Explanation, Knowledge Gaps, Study Notes | RAID Log, Status Report Source | Architecture Document, Context View, Runtime View, Deployment View | ADR File, Decision Log, Rationale |
Tagsno overlap | LearningKnowledgeUnderstanding | RiskTrackingStakeholdersGovernance | ArchitectureDocumentationCommunication | ArchitectureRationaleDocumentationGovernance |