View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Decision Jam |  Architecture Architecture Decision Record |  UX Research Affinity Diagramming |  Architecture Request for Comments |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 60-90 min | 15-45 min | 45–90 min | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 4-10 | 1-3 | 3-10 | 3-20 Reviewer |
Formatdifferent | Workshop | Async | Workshop | Async |
Outputdifferent | Problem Cluster, Prioritized Challenge, Experiment | ADR File, Decision Log, Rationale | Theme clusters, Insight statements, Opportunity areas | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | FacilitationDecisionProblem solvingWorkshop | ArchitectureRationaleDocumentationGovernance | SynthesisQualitativeRoot cause | ArchitectureDecisionAsyncGovernance |