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 Three-Point Estimation |  Architecture C4 Model |  Decision Making PERT Estimation |
|---|---|---|---|---|
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. | A single estimate for effort, time, or risk often looks too smooth for the real uncertainty behind it. It separates options, evaluation criteria, and open risks. The result is captured as a Three-Point Estimate, Risk Range, and Assumption Notes. | 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. | On complex initiatives, a plain average tends to understate just how uncertain the outcome really is. It separates options, evaluation criteria, and open risks. The result is captured as a PERT Estimate, Expected Value, and Risk Notes. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 15-45 min | 10-30 min je Item | 1-4 h | 15-45 min |
Participantsdifferent | 1-3 | 1-8 | 1-5 | 1-8 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Three-Point Estimate, Risk Range, Assumption Notes | Context Diagram, Container Diagram, Component Diagram | PERT Estimate, Expected Value, Risk Notes |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | EstimationUncertaintyForecasting | ArchitectureCommunicationVisualization | EstimationUncertaintyRisk |