View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  UX Research Personas |  Architecture Architecture Decision Record |  Operations Root Cause Analysis |  Operations Root Cause Tree Analysis |
|---|---|---|---|---|
Purposedifferent | When target groups stay too vague and teams talk about the same people differently, personas create a shared, solid picture of usage. Condensed profiles make needs, contexts, and differences tangible enough for decisions. | 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 problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another. | For a problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 1-3 Tage | 15-45 min | 1-4 h | 1-3 h |
Participantsdifferent | Internes Team | 1-3 | 3-8 | 2-8 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop |
Outputdifferent | Persona Profiles, Needs Summary, Scenario Notes | ADR File, Decision Log, Rationale | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | Cause Tree, Evidence Notes, Countermeasures |
Tagsno overlap | ResearchCustomerSynthesis | ArchitectureRationaleDocumentationGovernance | Root causeProblem solvingQualityIncident | Root causeTreeIncidentQuality |