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 arc42 |  Architecture ARID (Active Reviews for Intermediate Designs) |  Knowledge Modeling Teach-back |  Knowledge Modeling Feynman Technique |
|---|---|---|---|---|
Purposedifferent | 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. | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. | Teach-back checks whether an explanation actually got through to the other person. The method makes misunderstandings visible early and strengthens shared understanding in advisory and learning situations. | 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 1-2 Tage | 2–4 h review as a planning range; preparation and evaluation additional | 5-20 min | 20-60 min |
Participantsdifferent | 1-4 | Designers, developers as users, and facilitation | 2-8 | 1 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Understanding Check, Clarification Notes, Learning Gaps | Plain-language Explanation, Knowledge Gaps, Study Notes |
Tagsno overlap | ArchitectureDocumentationCommunication | ArchitectureEngineeringFeedbackValidationTasks | LearningUnderstandingCommunication | LearningKnowledgeUnderstanding |