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
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
Paper illustration for RAPID
Decision Making
RAPID
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Purposedifferent
The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly.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.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
LowMediumMediumLow
Timedifferent
1-2 h1-3 h45-90 min15-45 min
Participantsdifferent
3-101-83-121-3
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Architecture Canvas, Goals, Constraints, Quality AttributesArgument Map, Evidence Gaps, Decision RationaleRAPID Role Map, Recommendation, Decision LogADR File, Decision Log, Rationale
Tagsno overlap
CanvasArchitectureAlignmentWorkshop
SensemakingDecisionRationale
DecisionRolesGovernance
ArchitectureRationaleDocumentationGovernance
Add more methods