Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Selected:Architecture Decision Record Spotify Model Mapping Request for Comments Team Topologies Interaction Modes

Criterion	Architecture Architecture Decision Record	Team Design Spotify Model Mapping	Architecture Request for Comments	Team Design Team Topologies Interaction Modes
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 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.	An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale.	When several teams collaborate repeatedly, it describes the right interaction mode for each interface between them. It clarifies responsibility, interaction, and load between teams. The result is captured as an interaction heat map and pairwise agreements.
Complexitydifferent	Low	Medium	Medium	Medium
Timedifferent	15-45 min	90-180 min	1-3 Wochen vom Draft bis zur Entscheidung	Half day
Participantsdifferent	1-3	5-15	3-20 Reviewer	Team-Leads plus Architecture
Formatdifferent	Async	Workshop	Async	Workshop
Outputdifferent	ADR File, Decision Log, Rationale	Spotify Model Map, Action List	RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets	Interaction Heat Map, Agreements per Pair
Tagsno overlap	ArchitectureRationaleDocumentationGovernance	TeamOrganizationAlignmentDiagnosis	ArchitectureDecisionAsyncGovernance	TeamAlignmentCollaborationOrganization

Add more methods