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 Argument Mapping
Decision Making
Argument Mapping
Paper session grid with two time blocks, three rooms, colored session cards and an open topic pool.
Facilitation
Barcamp
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 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.When many people can contribute knowledge and the flow should stay open, Barcamp provides a framework for self-organized sessions. The format channels energy without defining the content too narrowly in advance.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 Entscheidung1-3 hHalber Tag bis 2 Tage30-60 min
Participantsdifferent
3-20 Reviewer1-815-2002-10
Formatdifferent
AsyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
RFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsArgument Map, Evidence Gaps, Decision RationaleSession Board, Session Notes, Community LearningsDACI Matrix, Decision Owner, Decision Log
Tagsno overlap
ArchitectureDecisionAsyncGovernance
SensemakingDecisionRationale
FacilitationLarge groupLearning
DecisionRolesGovernanceAlignment
Add more methods