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 |  Product Strategy Counter Metrics |  Architecture C4 Model |  Product Strategy KPI Tree |
|---|---|---|---|---|
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. | When a headline metric could mask side effects, it adds guardrail signals against unwanted outcomes. It connects customer value, product logic, and decision priorities. The result is captured as a counter-metric list and guardrail definitions. | 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 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 | Low | Medium |
Timedifferent | 15-45 min | 30-60 min | 1-4 h | 90-180 min initial, dann laufend |
Participantsdifferent | 1-3 | 2-6 | 1-5 | 3-8 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Counter Metric List, Guardrail Definitions | Context Diagram, Container Diagram, Component Diagram | KPI Tree, Owner List |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | MetricsMeasurementStrategyExperiments | ArchitectureCommunicationVisualization | MetricsStrategyAlignmentMeasurement |