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 RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
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.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects.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
MediumLowHighLow
Timedifferent
1-3 h30 min Setup, dann laufend1-4 Wochen15-45 min
Participantsdifferent
1-81-3 maintaining, briefing for everyone1-61-3
Formatdifferent
Workshop + asyncAsyncAsyncAsync
Outputdifferent
Argument Map, Evidence Gaps, Decision RationaleRAID Log, Status Report SourceExperiment results, Decision log, Learning summaryADR File, Decision Log, Rationale
Tagsno overlap
SensemakingDecisionRationale
RiskTrackingStakeholdersGovernance
ExperimentsGrowthAnalyticsValidation
ArchitectureRationaleDocumentationGovernance
Add more methods