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 Knowledge Mapping |  Architecture arc42 |  Knowledge Modeling Concept Mapping |
|---|---|---|---|---|
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. | Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable. | 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. | Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 15-45 min | 1-3 h | 1-2 Tage | 1-2 h |
Participantsdifferent | 1-3 | 3-12 | 1-4 | 1-8 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Architecture Document, Context View, Runtime View, Deployment View | Concept Map, Relationship Labels, Knowledge Gaps |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | KnowledgeMappingRisk | ArchitectureDocumentationCommunication | KnowledgeConceptsMappingSensemaking |