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 C4 Model | ![]() Facilitation Decision Jam | ![]() Architecture Architecture Decision Record | ![]() Decision Making Argument Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | When a decision is stuck, Decision Jam loosens the knot through structured separation of problem, idea, and selection. The format creates movement without jumping prematurely at the first seemingly elegant answer. | 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 | Low | Low | Low | Medium |
Timedifferent | 1-4 h | 60-90 min | 15-45 min | 1-3 h |
Participantsdifferent | 1-5 | 4-10 | 1-3 | 1-8 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop + async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Problem Cluster, Prioritized Challenge, Experiment | ADR File, Decision Log, Rationale | Argument Map, Evidence Gaps, Decision Rationale |
Tagsno overlap | ArchitectureCommunicationVisualization | FacilitationDecisionProblem solvingWorkshop | ArchitectureRationaleDocumentationGovernance | SensemakingDecisionRationale |



