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 5 Whys |
|---|---|---|---|
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. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 1-3 Tage | 15-45 min | 15-30 min |
Participantsdifferent | Internes Team | 1-3 | 2-6 |
Formatdifferent | Workshop + async | Async | Workshop |
Outputdifferent | Persona Profiles, Needs Summary, Scenario Notes | ADR File, Decision Log, Rationale | Root cause notes, Countermeasures |
Tagsno overlap | ResearchCustomerSynthesis | ArchitectureRationaleDocumentationGovernance | Root causeIncidentLeanProblem solving |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
