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 |  Facilitation Decision Jam |  Operations 8D Problem Solving |
|---|---|---|---|---|
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. | When a decision is stuck, Decision Jam loosens the knot through structured separation of problem, idea, and selection. The format creates movement without jumping prematurely at the first seemingly elegant answer. | 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. |
Complexitydifferent | Medium | Low | Low | High |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 45–90 min | 60-90 min | 1-6 Wochen |
Participantsdifferent | 3-20 Reviewer | 3-10 | 4-10 | 4-10 |
Formatdifferent | Async | Workshop | Workshop | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Theme clusters, Insight statements, Opportunity areas | Problem Cluster, Prioritized Challenge, Experiment | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | SynthesisQualitativeRoot cause | FacilitationDecisionProblem solvingWorkshop | QualityProblem solvingRoot cause |