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 Request for Comments |  UX Research Card Sorting |  Decision Making Decision Rights Mapping |
|---|---|---|---|
Purposedifferent | 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. | When content only makes sense internally and users can't find the structure again, card sorting exposes their mental order. Terms, groups, and naming are then aligned with the target group's expectations. | In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 20-45 min | 90-180 min |
Participantsdifferent | 3-20 Reviewer | Based on research question | 4-12 |
Formatdifferent | Async | Workshop + async | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Content groups, Label set, IA hypotheses | Decision Rights Matrix, Agreement |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | Information architectureNavigationStructure | DecisionGovernanceAlignmentResponsibility |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
