View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Kanban |  Decision Making RAPID |  Architecture arc42 |  Decision Making DACI |
|---|---|---|---|---|
Purposedifferent | 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 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. | 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. | 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 | Medium | Medium | Low | Low |
Timedifferent | Ongoing | 45-90 min | 1-2 Tage | 30-60 min |
Participantsdifferent | 2-12 | 3-12 | 1-4 | 2-10 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | RAPID Role Map, Recommendation, Decision Log | Architecture Document, Context View, Runtime View, Deployment View | DACI Matrix, Decision Owner, Decision Log |
Tagsno overlap | FlowVisual managementDelivery | DecisionRolesGovernance | ArchitectureDocumentationCommunication | DecisionRolesGovernanceAlignment |