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 arc42 |  Decision Making Decision Rights Mapping |  Architecture Request for Comments |
|---|---|---|---|---|
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. | 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 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 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. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 1-3 h | 1-2 Tage | 90-180 min | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 4-10 | 1-4 | 4-12 | 3-20 Reviewer |
Formatdifferent | Workshop | Workshop + async | Workshop | Async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Architecture Document, Context View, Runtime View, Deployment View | Decision Rights Matrix, Agreement | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | LeanFlowWasteDelivery | ArchitectureDocumentationCommunication | DecisionGovernanceAlignmentResponsibility | ArchitectureDecisionAsyncGovernance |