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 for RAPID
Decision Making
RAPID
A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls Retrospective
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.In complex management decisions, clarity is often missing about who recommends, who agrees, and who makes the decision. RAPID creates this assignment and stabilizes decisions across several levels.When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time.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 h45-90 min45–75 min15-45 min
Participantsdifferent
1-83-12Team members involved1-3
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopAsync
Outputdifferent
Argument Map, Evidence Gaps, Decision RationaleRAPID Role Map, Recommendation, Decision Log4Ls Board, Learning Themes, Improvement ActionsADR File, Decision Log, Rationale
Tagsno overlap
SensemakingDecisionRationale
DecisionRolesGovernance
RetrospectiveLearningReflectionTeam
ArchitectureRationaleDocumentationGovernance
Add more methods