Purpose
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.
Team Design Mapping tool
Spotify Model Mapping
Maps squads, tribes, chapters, and guilds to diagnose local organisational needs.
The published Spotify model describes a historical context, not a copyable framework. Mapping translates terms into local purposes, decision rights, and risks and marks deviations.
Which local structures do we need for autonomy, alignment, and craft exchange?
- Participants
- 5-15
- Time
- 90-180 min
Spotify Model Mapping uses map Spotify terms as hypotheses onto local product flows, communities, and leadership needs. Assessments remain justified and context-bound.
Establish context
Establish context
Make the historical Spotify context and local differences explicit.
Map product flow
Map product flow
Map long-lived teams to products and value streams.
Map communities
Map communities
Clarify chapter and guild needs, mandate, and participation.
Test hypothesis
Test hypothesis
Test the mapping against real decisions and dependencies.
After each organisational change, review flow, autonomy, and craft quality.
A good fit when
For organisational diagnosis with clear product flows; not as reorganisation by label.
Ideal for
- Engineering org diagnosis
- Scaling workshops
Not good for
- Very small organizations
Outputs
organisation mapping
organisation mapping with traceable sources, assumptions, and domain decisions.
Decision and review trail
Owners, dates, and next review for organisation mapping.
organisation mapping
Fictional worked example
map Spotify terms as hypotheses onto local product flows, communities, and leadership needs as a precise working structure with a fictional example.
Local unit
Team/community · purpose · product flow
Billing product team; long-lived product flow.
Spotify analogy
Squad · tribe · chapter · guild · none
Partly squad; no tribe.
Mandate
Decision right · leadership · participation
Security chapter with people responsibility.
Risk and test
Misapplication · measure · review
Review hand-offs per feature after eight weeks.
First step
Start with the core question: Which local structures do we need for autonomy, alignment, and craft exchange?
Good to do first
Deep dive
How it works
The current organization is mirrored against squads, tribes, chapters, and guilds, so that formal and lived structure can be told apart. This makes overlaps, gaps, and unnecessary coupling visible. The model serves as a conversation frame for adjustment, not as a rigid target picture.
In detail
Spotify Model Mapping brings the terms Squad, Tribe, Chapter, and Guild, made popular by Spotify's engineering culture, onto one shared map. It is often used critically because the myth around the model is often larger than the reality at Spotify itself. The method helps make chosen structures explicit and question them.
Facilitation
Define the four terms briefly and consistently. Ask what the terms should mean in your organization. Avoid copying them blindly.
The method guide walks execution through 4 phases, timing, 4 pitfalls, and clear stop criteria.
Open method guideYour perspective
Does this method help with your work?
Your feedback helps shape the next improvements to methodatlas.
Sources and topics
Artifact templates
Spotify Model Mapping: WorksheetPlan Spotify Model Mapping around its domain steps and the concrete decision question.canvas
Spotify Model Mapping: WorksheetPlan Spotify Model Mapping around its domain steps and the concrete decision question.
canvasspotify-model-mapping-working-template.md
Plan Spotify Model Mapping around its domain steps and the concrete decision question.
Spotify Model Mapping: Worksheet
Question
To be confirmed
Desired outcome
To be confirmed
Scope
Full initiative Time: 2 × 90 minutes
Complete this worksheet on paper or in your own document during the work.
Preparation for this scope
Method setup
- Materials: Product and value flows, current teams and communities, decision and dependency data, shared workspace, source links, and decision log.
- Roles: Leadership · team representatives · Product · People/Organisation
- Advance information: Collect Product and value flows, current teams and communities, decision and dependency data in advance and mark open assumptions.
- Overall time needed: 2 × 90 minutes
- Setup: Prepare map Spotify terms as hypotheses onto local product flows, communities, and leadership needs visibly and calibrate assessment terms before starting.
Prepare for the work steps
Establish context: Establish context
- Product and value flows
- current teams and communities
- decision and dependency data
Map product flow: Map product flow
- context boundaries
- current teams and communities
- decision and dependency data
Map communities: Map communities
- flow map
- current teams and communities
- decision and dependency data
Test hypothesis: Test hypothesis
- community map
- current teams and communities
- decision and dependency data
organisation mapping
Local unit
Team/community · purpose · product flow
...
Spotify analogy
Squad · tribe · chapter · guild · none
...
Mandate
Decision right · leadership · participation
...
Risk and test
Misapplication · measure · review
...
Spotify Engineering Culture, part 1
Establish context: Establish context
Expected artifact: context boundaries
context boundaries · source · uncertainty · next decision
Entry:
...
- Are terms marked as analogies?
Map product flow: Map product flow
Expected artifact: flow map
flow map · source · uncertainty · next decision
Entry:
...
- Does the boundary minimise hand-offs?
Map communities: Map communities
Expected artifact: community map
community map · source · uncertainty · next decision
Entry:
...
- Are people responsibility and voluntary exchange distinct?
Test hypothesis: Test hypothesis
Expected artifact: change hypothesis
change hypothesis · source · uncertainty · next decision
Entry:
...
- Is a measurable flow improvement named?
Open questions and next steps
...
Method guide: https://methodatlas.meierhoff-systems.de/en/methods/spotify-model-mapping/run-sheet
Alternatives and neighbors
Fitting alternatives with decision guidance, followed by other related methods.
Team Design
Team Topologies Interaction Modes
Instead of Spotify Model Mapping, choose Team Topologies Interaction Modes when you want to shape collaboration between teams as a lasting interaction mode.
Business Strategy
McKinsey 7S
Clarifies starting point, opportunities, and strategic options by framing the scope and target state, capturing the seven elements, and deriving change actions.
Facilitation
Team Charter
Clarifies purpose, roles, and working rules in a charter that makes collaboration tangible and verifiable.
Facilitation
Expectation Mapping
Surfaces stakeholder expectations, clusters conflicts, and turns them into concrete agreements.
Facilitation
Alignment Mapping
Makes goals, concerns, and open gaps visible so clarification steps can be planned deliberately.
Facilitation
Consensus Workshop
Condenses individual ideas into clusters, themes, and priorities so consensus grows out of individual contributions.
Constraints and origin
MediumWorkshop90-180 min
Profile
- Method form
- Mapping tool
- Participants
- 5-15
- Time
- 90-180 min
- Maturity
- Established
- Origin
- Spotify Engineering Culture
Next up: Team API