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 Argument Mapping |  Delivery Cost of Delay |
|---|---|---|---|---|
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. | When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on. | Helps clarify scope, order, and delivery flow in concrete terms. It makes work, constraints, and sequence manageable. The result is captured as a Cost of Delay table and prioritization sequence. |
Complexitydifferent | Medium | Medium | Medium | High |
Timedifferent | 1-3 h | 1-3 Wochen vom Draft bis zur Entscheidung | 1-3 h | 90-180 min |
Participantsdifferent | 4-10 | 3-20 Reviewer | 1-8 | 3-8 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Argument Map, Evidence Gaps, Decision Rationale | CoD Table, Prioritization Sequence |
Tagsno overlap | LeanFlowWasteDelivery | ArchitectureDecisionAsyncGovernance | SensemakingDecisionRationale | PrioritizationDeliveryEconomicsDecision |