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 Personas |  Architecture Risk Storming |
|---|---|---|---|
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. | 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. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | 15-45 min | 1-3 Tage | 60-90 min |
Participantsdifferent | 1-3 | Internes Team | 4-12 |
Formatdifferent | Async | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Persona Profiles, Needs Summary, Scenario Notes | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ResearchCustomerSynthesis | RiskArchitectureWorkshopValidation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
