View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Strategy Counter Metrics |  Architecture Architecture Decision Record |  UX Research HEART Framework |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 30-60 min | 15-45 min | 120 min initial, dann laufend | 1-2 Tage |
Participantsdifferent | 2-6 | 1-3 | 3-6 | 1-4 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Counter Metric List, Guardrail Definitions | ADR File, Decision Log, Rationale | HEART-GSM Table, Dashboard | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | MetricsMeasurementStrategyExperiments | ArchitectureRationaleDocumentationGovernance | MetricsUX researchMeasurementSatisfaction | ArchitectureDocumentationCommunication |