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 |  Engineering Kanban |  Decision Making DACI |  Decision Making RAPID |
|---|---|---|---|---|
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. | When work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable. | 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. | In complex management decisions, clarity is often missing about who recommends, who agrees, and who makes the decision. RAPID creates this assignment and stabilizes decisions across several levels. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 15-45 min | Ongoing | 30-60 min | 45-90 min |
Participantsdifferent | 1-3 | 2-12 | 2-10 | 3-12 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Kanban board, WIP policies, Flow metrics | DACI Matrix, Decision Owner, Decision Log | RAPID Role Map, Recommendation, Decision Log |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | FlowVisual managementDelivery | DecisionRolesGovernanceAlignment | DecisionRolesGovernance |