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
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Paper illustration for Affinity Estimation.
Agile
Affinity Estimation
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
Paper illustration for DACI
Decision Making
DACI
Purposedifferent
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 many tasks need to be classified quickly, it sorts them by perceived effort and similarity. It reduces the effort of fine-grained estimation for large volumes.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 Wochen vom Draft bis zur Entscheidung30-90 min1-3 h30-60 min
Participantsdifferent
3-20 Reviewer3-121-82-10
Formatdifferent
AsyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
RFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsAffinity Size Map, Grouped Estimates, Unclear ItemsArgument Map, Evidence Gaps, Decision RationaleDACI Matrix, Decision Owner, Decision Log
Tagsno overlap
ArchitectureDecisionAsyncGovernance
EstimationBacklogRelative sizing
SensemakingDecisionRationale
DecisionRolesGovernanceAlignment
Add more methods