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 Six Thinking Hats | ![]() Architecture Architecture Decision Record | ![]() Architecture Request for Comments |
|---|---|---|---|
Purposedifferent | When a topic gets stuck too quickly in the same thinking mode, Six Thinking Hats deliberately separates the perspectives. This means facts, risks, creativity, and emotional signals get worked through one after another instead of mixed together. | 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. | 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 | Medium | Low | Medium |
Timedifferent | 45-90 min | 15-45 min | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 4-12 | 1-3 | 3-20 Reviewer |
Formatdifferent | Workshop | Async | Async |
Outputdifferent | Perspective Notes, Decision Inputs, Action Items | ADR File, Decision Log, Rationale | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | FacilitationOptionsDecision | ArchitectureRationaleDocumentationGovernance | ArchitectureDecisionAsyncGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






