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 Views and Beyond |  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. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | 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 | Medium | Medium |
Timedifferent | 15-45 min | 1-3 h | 1-3 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 Views, Cross-view Notes, Rationale | Concept Map, Relationship Labels, Knowledge Gaps |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | KnowledgeMappingRisk | DocumentationStakeholdersArchitecture | KnowledgeConceptsMappingSensemaking |