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 8D Problem Solving |  UX Research Affinity Diagramming |
|---|---|---|---|---|
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 an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly. | When research notes, feedback, or observations sit unconnected side by side, affinity diagramming sorts the raw material into solid themes. Many individual points turn into patterns that make decisions and opportunities clearer. |
Complexitydifferent | Medium | Low | High | Low |
Timedifferent | 1-3 Tage | 15-45 min | 1-6 Wochen | 45–90 min |
Participantsdifferent | Internes Team | 1-3 | 4-10 | 3-10 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop |
Outputdifferent | Persona Profiles, Needs Summary, Scenario Notes | ADR File, Decision Log, Rationale | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan | Theme clusters, Insight statements, Opportunity areas |
Tagsno overlap | ResearchCustomerSynthesis | ArchitectureRationaleDocumentationGovernance | QualityProblem solvingRoot cause | SynthesisQualitativeRoot cause |