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 |  Decision Making Pareto Analysis |  Operations Scatter Diagram |  Architecture C4 Model |
|---|---|---|---|---|
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. | In many problem situations, effect is distributed unequally across many causes. A Pareto Analysis separates the few drivers with high leverage from the long remainder and focuses attention on what measurably moves the needle. | When the question is whether two measures are related, the method makes patterns in the data picture visible. It separates felt correlations from relationships that actually show up in the data. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 15-45 min | 30-60 min | 30-90 min | 1-4 h |
Participantsdifferent | 1-3 | 1-6 | 1-4 | 1-5 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Pareto Chart, Top Causes, Focus List | Scatter Plot, Korrelationsnotiz, Hypothesenliste | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | PrioritizationQualityFocusRoot cause | Root causeQualityVisualization | ArchitectureCommunicationVisualization |