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 | ![]() Operations Root Cause Analysis |
|---|---|---|---|
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. | When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | 15-45 min | 120 min initial, dann laufend | 1-4 h |
Participantsdifferent | 1-3 | 3-6 | 3-8 |
Formatdifferent | Async | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | HEART-GSM Table, Dashboard | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | MetricsUX researchMeasurementSatisfaction | Root causeProblem solvingQualityIncident |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






