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 |  Decision Making RAPID |  UX Research Affinity Diagramming |
|---|---|---|---|
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. | In complex management decisions, clarity is often missing about who recommends, who agrees, and who makes the decision. RAPID creates this assignment and stabilizes decisions across several levels. | When research notes, feedback, or observations sit unconnected side by side, affinity diagramming sorts the raw material into solid themes. Many individual points turn into patterns that make decisions and opportunities clearer. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 45-90 min | 45–90 min |
Participantsdifferent | 3-20 Reviewer | 3-12 | 3-10 |
Formatdifferent | Async | Workshop + async | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | RAPID Role Map, Recommendation, Decision Log | Theme clusters, Insight statements, Opportunity areas |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | DecisionRolesGovernance | SynthesisQualitativeRoot cause |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
