View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery Value Stream Mapping |  Architecture Request for Comments |  Decision Making Decision Rights Mapping |  Decision Making DACI |
|---|---|---|---|---|
Purposedifferent | When delivery work dissolves into wait times, handoffs, and hidden effort, Value Stream Mapping makes the actual flow visible. The method exposes bottlenecks, idle time, and feedback loops so lead time and improvement levers become tangible. | 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 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. | 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 | Medium | Low |
Timedifferent | 1-3 h | 1-3 Wochen vom Draft bis zur Entscheidung | 90-180 min | 30-60 min |
Participantsdifferent | 4-10 | 3-20 Reviewer | 4-12 | 2-10 |
Formatdifferent | Workshop | Async | Workshop | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Decision Rights Matrix, Agreement | DACI Matrix, Decision Owner, Decision Log |
Tagsno overlap | LeanFlowWasteDelivery | ArchitectureDecisionAsyncGovernance | DecisionGovernanceAlignmentResponsibility | DecisionRolesGovernanceAlignment |