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 Views and Beyond |  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. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | 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 | Medium | Low |
Timedifferent | 15-45 min | 120 min initial, dann laufend | 1-3 Tage | 30-60 min |
Participantsdifferent | 1-3 | 3-6 | 1-4 | 2-6 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | HEART-GSM Table, Dashboard | Architecture Views, Cross-view Notes, Rationale | Counter Metric List, Guardrail Definitions |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | MetricsUX researchMeasurementSatisfaction | DocumentationStakeholdersArchitecture | MetricsMeasurementStrategyExperiments |