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 two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration of Team API with its method-specific working model.
Team Design
Team API
Paper illustration of Spotify Model Mapping with its method-specific working model.
Team Design
Spotify Model Mapping
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Purposedifferent
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.When expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document.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.The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails.
Complexitydifferent
LowLowMediumLow
Timedifferent
15-45 minHalf day initial, dann laufend90-180 min1-2 h
Participantsdifferent
1-3Ein Team plus Stakeholder5-153-8
Formatdifferent
AsyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
ADR File, Decision Log, RationaleTeam API DocumentSpotify Model Map, Action ListInception Canvas, Risks, Goal List, Open Questions
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
TeamAlignmentCommunicationService
TeamOrganizationAlignmentDiagnosis
AlignmentArchitectureCanvas
Add more methods