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 |  UX Research HEART Framework |  Architecture C4 Model |  Product Strategy Counter Metrics |
|---|---|---|---|---|
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. | Helps clarify observations, needs, and patterns in concrete terms. It groups observations into patterns, questions, and decisions. The result is captured as a HEART-GSM table and dashboard. | 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 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 15-45 min | 120 min initial, dann laufend | 1-4 h | 30-60 min |
Participantsdifferent | 1-3 | 3-6 | 1-5 | 2-6 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | HEART-GSM Table, Dashboard | Context Diagram, Container Diagram, Component Diagram | Counter Metric List, Guardrail Definitions |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | MetricsUX researchMeasurementSatisfaction | ArchitectureCommunicationVisualization | MetricsMeasurementStrategyExperiments |