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 for Argument Mapping
Decision Making
Argument Mapping
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Paper illustration for 1-2-4-All.
Facilitation
1-2-4-All
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Purposedifferent
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.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 people in a group too rarely get to speak, 1-2-4-All distributes thinking time more fairly. The format builds participation step by step and makes quiet or still-unformed thoughts usable faster.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.
Complexitydifferent
MediumMediumLowLow
Timedifferent
1-3 h1-3 Wochen vom Draft bis zur Entscheidung10-20 min15-45 min
Participantsdifferent
1-83-20 Reviewer4-100+1-3
Formatdifferent
Workshop + asyncAsyncWorkshopAsync
Outputdifferent
Argument Map, Evidence Gaps, Decision RationaleRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsIdea List, Shared Insights, Emergent ThemesADR File, Decision Log, Rationale
Tagsno overlap
SensemakingDecisionRationale
ArchitectureDecisionAsyncGovernance
FacilitationInclusionIdeation
ArchitectureRationaleDocumentationGovernance
Add more methods