In 30 seconds
- Squads, tribes, chapters and guilds organize autonomous teams.
- It described Spotify's culture at one point in time, not a framework.
- Spotify itself evolved beyond it; copy the principles, not the labels.
The structure
| Unit | What it is |
|---|---|
| Squad | Small, autonomous, cross-functional team, similar to a Scrum team |
| Tribe | Group of squads working in a related area |
| Chapter | People with the same skill across squads in a tribe |
| Guild | Voluntary community of interest across the company |
Where it came from
Henrik Kniberg and Anders Ivarsson described the structure in a 2012 paper and later videos. It captured how Spotify was working at the time, with a strong emphasis on autonomy and alignment.
Why copying it fails
Organizations often rename teams as squads and tribes without the culture of trust, autonomy and cross-functional teams underneath. Spotify itself has said the model was never a framework and has kept changing.
Myth vs reality
Myth · The Spotify model is a framework to install.
Reality · It was a snapshot of one company's culture.
Myth · Renaming teams creates autonomy.
Reality · Autonomy comes from decision rights and trust.
Myth · Spotify still runs exactly this way.
Reality · It has evolved considerably since 2012.
FAQ
What's worth borrowing?
Autonomous teams, communities of practice, and aligning on goals rather than tasks.
How does it relate to Scrum?
Squads often use Scrum or Kanban internally.
Is it suitable for small companies?
The structure is overkill; the principles still apply.