View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Architecture Decision Record |  Knowledge Modeling Feynman Technique |  Business Strategy Strategy Execution Loop |  Architecture Request for Comments |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | The Strategy Execution Loop helps avoid treating strategy as a one-off document. It makes visible how strategic decisions are turned into objectives, initiatives, operational work, measurement, and learning. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. |
Complexitydifferent | Low | Low | High | Medium |
Timedifferent | 15-45 min | 20-60 min | Initial 3-6 h, then monthly or quarterly reviews | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 1-3 | 1 | 5-12 | 3-20 Reviewer |
Formatdifferent | Async | Async | Workshop + async | Async |
Outputdifferent | ADR File, Decision Log, Rationale | Plain-language Explanation, Knowledge Gaps, Study Notes | Execution Loop, Review Cadence, Strategic Learning Log | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | LearningKnowledgeUnderstanding | ExecutionCadenceLearningGovernance | ArchitectureDecisionAsyncGovernance |