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 ARID (Active Reviews for Intermediate Designs) |
|---|---|---|---|
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. | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | 15-45 min | 1-3 Tage | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | 1-3 | Internes Team | Designers, developers as users, and facilitation |
Formatdifferent | Async | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Persona Profiles, Needs Summary, Scenario Notes | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ResearchCustomerSynthesis | ArchitectureEngineeringFeedbackValidationTasks |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
