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 arc42 | ![]() Architecture Architecture Decision Record | ![]() Decision Making Assumption Surfacing | ![]() Decision Making Argument Mapping |
|---|---|---|---|---|
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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 1-2 Tage | 15-45 min | 45-90 min | 1-3 h |
Participantsdifferent | 1-4 | 1-3 | 2-8 | 1-8 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | ADR File, Decision Log, Rationale | Assumption List, Critical Assumptions, Learning Plan | Argument Map, Evidence Gaps, Decision Rationale |
Tagsno overlap | ArchitectureDocumentationCommunication | ArchitectureRationaleDocumentationGovernance | AssumptionsRiskDecisionDiscovery | SensemakingDecisionRationale |



