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 Affinity Diagramming |  Operations 8D Problem Solving |  Operations Root Cause Analysis |
|---|---|---|---|---|
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 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. | 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. | When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another. |
Complexitydifferent | Medium | Low | High | Medium |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 45–90 min | 1-6 Wochen | 1-4 h |
Participantsdifferent | 3-20 Reviewer | 3-10 | 4-10 | 3-8 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Theme clusters, Insight statements, Opportunity areas | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | SynthesisQualitativeRoot cause | QualityProblem solvingRoot cause | Root causeProblem solvingQualityIncident |