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 Affinity Diagramming |  Architecture Request for Comments |  Operations 8D Problem Solving |  Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly. | 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. |
Complexitydifferent | Low | Medium | High | Low |
Timedifferent | 45–90 min | 1-3 Wochen vom Draft bis zur Entscheidung | 1-6 Wochen | 15-45 min |
Participantsdifferent | 3-10 | 3-20 Reviewer | 4-10 | 1-3 |
Formatdifferent | Workshop | Async | Workshop + async | Async |
Outputdifferent | Theme clusters, Insight statements, Opportunity areas | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan | ADR File, Decision Log, Rationale |
Tagsno overlap | SynthesisQualitativeRoot cause | ArchitectureDecisionAsyncGovernance | QualityProblem solvingRoot cause | ArchitectureRationaleDocumentationGovernance |