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 |  Operations 5 Whys |
|---|---|---|---|---|
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. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. |
Complexitydifferent | Low | Medium | High | Low |
Timedifferent | 45–90 min | 1-3 Wochen vom Draft bis zur Entscheidung | 1-6 Wochen | 15-30 min |
Participantsdifferent | 3-10 | 3-20 Reviewer | 4-10 | 2-6 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop |
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 | Root cause notes, Countermeasures |
Tagsno overlap | SynthesisQualitativeRoot cause | ArchitectureDecisionAsyncGovernance | QualityProblem solvingRoot cause | Root causeIncidentLeanProblem solving |