methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration for Feynman Technique.
Knowledge Modeling
Feynman Technique
Paper illustration for Teach-back.
Knowledge Modeling
Teach-back
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.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.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.
Complexitysame
LowLowLowLow
Timedifferent
1-2 Tage15-45 min20-60 min5-20 min
Participantsdifferent
1-41-312-8
Formatdifferent
Workshop + asyncAsyncAsyncWorkshop + async
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewADR File, Decision Log, RationalePlain-language Explanation, Knowledge Gaps, Study NotesUnderstanding Check, Clarification Notes, Learning Gaps
Tagsno overlap
ArchitectureDocumentationCommunication
ArchitectureRationaleDocumentationGovernance
LearningKnowledgeUnderstanding
LearningUnderstandingCommunication
Add more methods