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 Decision Rights Mapping |  Architecture Architecture Decision Record |
|---|---|---|---|
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 organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement. | 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. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | Ongoing | 90-180 min | 15-45 min |
Participantsdifferent | 2-12 | 4-12 | 1-3 |
Formatdifferent | Workshop + async | Workshop | Async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Decision Rights Matrix, Agreement | ADR File, Decision Log, Rationale |
Tagsno overlap | FlowVisual managementDelivery | DecisionGovernanceAlignmentResponsibility | ArchitectureRationaleDocumentationGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
