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 Architecture Decision Record |  Innovation Solo Brainstorming |  Architecture Request for Comments |  Decision Making DACI |
|---|---|---|---|---|
Purposedifferent | 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. | For an individual thinking problem with no counterpart immediately available, the method creates a protected space for one's own approaches. It prevents outside opinions from narrowing thinking too early. This lets ideas mature before they go into a group format. | 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. | In cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 15-45 min | 15-60 min | 1-3 Wochen vom Draft bis zur Entscheidung | 30-60 min |
Participantsdifferent | 1-3 | 1 | 3-20 Reviewer | 2-10 |
Formatdifferent | Async | Async | Async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Personal Idea List, Sketches or Mind Map, Pre-Read for Group Session | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | DACI Matrix, Decision Owner, Decision Log |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | BrainstormingIdeationAsync | ArchitectureDecisionAsyncGovernance | DecisionRolesGovernanceAlignment |