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 Usability Testing | ![]() Architecture Request for Comments | ![]() Decision Making DACI | ![]() Architecture Architecture Inception Canvas |
|---|---|---|---|---|
Purposedifferent | When a product is built but people get stuck on tasks, usability testing shows the friction at concrete points. Observed use instead of self-report makes visible where orientation, understanding, or interaction breaks down. | 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. | 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 Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-2 h je Session | 1-3 Wochen vom Draft bis zur Entscheidung | 30-60 min | 1-2 h |
Participantsdifferent | Based on research question | 3-20 Reviewer | 2-10 | 3-8 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop |
Outputdifferent | Usability Issues, Severity List, Recommendations | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | DACI Matrix, Decision Owner, Decision Log | Inception Canvas, Risks, Goal List, Open Questions |
Tagsno overlap | ValidationUXPrototype | ArchitectureDecisionAsyncGovernance | DecisionRolesGovernanceAlignment | AlignmentArchitectureCanvas |



