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 Spotify Model Mapping with its method-specific working model.
Team Design
Spotify Model Mapping
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
When a team landscape has grown without clear grouping, it maps roles and relationships onto the Spotify model. It clarifies responsibility, interaction, and load between teams. The result is captured as a Spotify model map and action list.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
MediumMediumMediumLow
Timedifferent
90-180 min1-3 h45-90 min15-45 min
Participantsdifferent
5-151-83-121-3
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Spotify Model Map, Action ListArgument Map, Evidence Gaps, Decision RationaleRAPID Role Map, Recommendation, Decision LogADR File, Decision Log, Rationale
Tagsno overlap
TeamOrganizationAlignmentDiagnosis
SensemakingDecisionRationale
DecisionRolesGovernance
ArchitectureRationaleDocumentationGovernance
Add more methods