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 |  Decision Making DACI |  Architecture Software Architecture Canvas |  Architecture Request for Comments |
|---|---|---|---|---|
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. | In cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 1-3 Tage | 30-60 min | 1-2 h | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | Internes Team | 2-10 | 3-10 | 3-20 Reviewer |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Async |
Outputdifferent | Persona Profiles, Needs Summary, Scenario Notes | DACI Matrix, Decision Owner, Decision Log | Architecture Canvas, Goals, Constraints, Quality Attributes | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | ResearchCustomerSynthesis | DecisionRolesGovernanceAlignment | CanvasArchitectureAlignmentWorkshop | ArchitectureDecisionAsyncGovernance |