methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Value Stream Mapping workspace showing the question, observations, and next decision.
Delivery
Value Stream Mapping
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
Paper illustration for DACI
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.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.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
MediumMediumMediumLow
Timedifferent
1-3 h1-3 Wochen vom Draft bis zur Entscheidung1-3 h30-60 min
Participantsdifferent
4-103-20 Reviewer1-82-10
Formatdifferent
WorkshopAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Current-state map, Future-state map, Bottleneck listRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsArgument Map, Evidence Gaps, Decision RationaleDACI Matrix, Decision Owner, Decision Log
Tagsno overlap
LeanFlowWasteDelivery
ArchitectureDecisionAsyncGovernance
SensemakingDecisionRationale
DecisionRolesGovernanceAlignment
Add more methods