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 C4 Model |  Knowledge Modeling IBIS |
|---|---|---|---|---|
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. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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 | Low | Medium | Low | Medium |
Timedifferent | 15-45 min | 1-3 h | 1-4 h | 1-3 h |
Participantsdifferent | 1-3 | 3-12 | 1-5 | 2-8 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Context Diagram, Container Diagram, Component Diagram | Issue Map, Positions, Argument Notes |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | KnowledgeMappingRisk | ArchitectureCommunicationVisualization | RationaleKnowledgeDecision |