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 of an IBIS map with issues, positions and arguments
Knowledge Modeling
IBIS
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.IBIS structures thinking about complex questions as a sequence of issues, ideas, and arguments. The method keeps discussions open without forcing them into premature consensus.
Complexitydifferent
LowLowLowMedium
Timedifferent
1-2 Tage15-45 min20-60 min1-3 h
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 NotesIssue Map, Positions, Argument Notes
Tagsno overlap
ArchitectureDocumentationCommunication
ArchitectureRationaleDocumentationGovernance
LearningKnowledgeUnderstanding
RationaleKnowledgeDecision
Add more methods