View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Decision Making DACI |  Innovation Design Sprint |  Architecture arc42 |  Architecture Request for Comments |
|---|---|---|---|---|
Purposedifferent | 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. | When the product question is unclear and time pressure is high, the method takes a team from an open idea to a testable solution. It connects problem understanding, decision, and learning in one compact format, lowering the risk of spending a lot of energy on a mere guess. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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 | High | Low | Medium |
Timedifferent | 30-60 min | 4-5 Tage | 1-2 Tage | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 2-10 | 5-8 | 1-4 | 3-20 Reviewer |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Async |
Outputdifferent | DACI Matrix, Decision Owner, Decision Log | Prototype, Test Findings, Decision Rationale | Architecture Document, Context View, Runtime View, Deployment View | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | DecisionRolesGovernanceAlignment | Design sprintPrototypeValidationInnovation | ArchitectureDocumentationCommunication | ArchitectureDecisionAsyncGovernance |