Purpose
Helps clarify team boundaries, interfaces, and collaboration in concrete terms. It clarifies responsibility, interaction, and load between teams. The result is captured as a Spotify model map and action list.
Team Design
Spotify Model Mapping
Moves team boundaries, interfaces, and collaboration toward a concrete result through "prepare a template with the four structures", "place current teams as squads", and "derive actions".
How is our engineering org actually structured into squads, tribes, chapters and guilds, and where do friction or gaps emerge?
MediumWorkshop90-180 min
How it works
The team follows the steps "prepare a template with the four structures", "place current teams as squads", "discuss tribe and chapter assignments", "name guilds explicitly", "mark gaps and friction", and "derive actions". Each step is made visible. At the end, a Spotify model map and action list are available so decisions, tests, or actions can continue directly.
Visual orientation
Method sketch for a quick mental model.
Flow
- 1Prepare a template with the four structures
- 2Place current teams as squads
- 3Discuss tribe and chapter assignments
- 4Name guilds explicitly
- 5Mark gaps and friction
- 6Derive actions
The runsheet guides execution with 5 phases, timeboxes, 5 pitfalls, and clear stop criteria.
Open runsheetIdeal for
- Engineering org diagnosis
- Scaling workshops
Not good for
- Very small organizations
Deep dive
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.
Output artifacts
Spotify-Modell-KarteAktionsliste
Artifact templates
Spotify Model Mapping Working TemplateCompact working template for Spotify Model Mapping with context, input, output artifacts, and next step.canvas
Spotify Model Mapping Working TemplateCompact working template for Spotify Model Mapping with context, input, output artifacts, and next step.
canvasspotify-model-mapping-working-template.md
Compact working template for Spotify Model Mapping with context, input, output artifacts, and next step.
Spotify Model Mapping Canvas
Context
What is this method used for?
Core question
Which question should be answered at the end?
Input
Which data, observations, or materials are available?
Working area
- Area 1:
- Area 2:
- Area 3:
- Relationships / patterns:
Output artifacts
- Spotify model map:
- Action list:
Open questions
- ...
Next step
Owner, date, success signal.
When to choose differently
Short decision aid for existing alternatives.
Team Topologies Interaction Modes
Statt Spotify Model Mapping, wenn ihr die Zusammenarbeit zwischen Teams als dauerhaften Interaktionsmodus gestalten wollt.
Similar methods
All methodsTeam Design
Team Topologies Interaction Modes
Moves team boundaries, interfaces, and collaboration toward a concrete result through "prepare the team list", "explain the three modes with examples", and "document agreements per pair".
Statt Spotify Model Mapping, wenn ihr die Zusammenarbeit zwischen Teams als dauerhaften Interaktionsmodus gestalten wollt.
Team Design
Team Cognitive Load Assessment
Moves team boundaries, interfaces, and collaboration toward a concrete result through "explain the scale and categories", "run an anonymous team survey", and "derive and track actions".
Team Design
Team API
Moves team boundaries, interfaces, and collaboration toward a concrete result through "provide the template", "clarify responsibilities and non-responsibilities", and "anchor it visibly in the wiki".
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
Turns group input, selection, and decision into a tangible result by clarifying team purpose, capturing goals and stakeholders, and reviewing the charter over time.
Facilitation
Expectation Mapping
Turns group input, selection, and decision into a tangible result by clarifying stakeholders and scope, collecting expectations silently, and deriving agreements.