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 | ![]() Architecture Architecture Decision Record | ![]() Engineering Goal Question Metric | ![]() Product Strategy KPI Tree |
|---|---|---|---|---|
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. | 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. | Helps clarify technical problems, hypotheses, and next steps in concrete terms. It breaks a technical problem into testable parts. The result is captured as a GQM table and metric briefs. | When metrics across the organization drift apart, it arranges drivers and effects under one shared logic. It connects customer value, product logic, and decision priorities. The result is captured as a KPI tree and owner list. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 1-4 h | 15-45 min | 90-180 min | 90-180 min initial, dann laufend |
Participantsdifferent | 1-5 | 1-3 | 3-6 | 3-8 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | ADR File, Decision Log, Rationale | GQM Table, Metric Profiles | KPI Tree, Owner List |
Tagsno overlap | ArchitectureCommunicationVisualization | ArchitectureRationaleDocumentationGovernance | MetricsMeasurementEngineeringAlignment | MetricsStrategyAlignmentMeasurement |



