View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Delivery Cost of Delay | ![]() Architecture arc42 | ![]() Architecture Architecture Decision Record | ![]() Decision Making Argument Mapping |
|---|---|---|---|---|
Purposedifferent | Helps clarify scope, order, and delivery flow in concrete terms. It makes work, constraints, and sequence manageable. The result is captured as a Cost of Delay table and prioritization sequence. | 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. | 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 | High | Low | Low | Medium |
Timedifferent | 90-180 min | 1-2 Tage | 15-45 min | 1-3 h |
Participantsdifferent | 3-8 | 1-4 | 1-3 | 1-8 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | CoD Table, Prioritization Sequence | Architecture Document, Context View, Runtime View, Deployment View | ADR File, Decision Log, Rationale | Argument Map, Evidence Gaps, Decision Rationale |
Tagsno overlap | PrioritizationDeliveryEconomicsDecision | ArchitectureDocumentationCommunication | ArchitectureRationaleDocumentationGovernance | SensemakingDecisionRationale |



