Agile guide · Scaling Agile
Squads, Tribes, Chapters and Guilds: The Spotify Model Explained
Squads, tribes, chapters and guilds are terms from the so-called Spotify model, described in a 2012 paper by Henrik Kniberg and Anders Ivarsson. It shows one way to keep many Agile teams autonomous while still aligned.
Key takeaways
- Squads deliver, tribes coordinate, chapters develop skills, guilds share knowledge.
- The model balances team autonomy with organisational alignment.
- Copy the principles, not the labels.
The building blocks
| Unit | What it is | Purpose |
|---|---|---|
| Squad | A small, cross-functional, self-organising team with a long-term mission | Deliver a part of the product end to end |
| Tribe | A group of squads working in a related area, kept small enough for people to know each other (the paper suggests under about 100) | Coordinate related squads |
| Chapter | People with the same skill within a tribe, such as testers or designers, led by a chapter lead who is also their line manager | Maintain skills and standards |
| Guild | A voluntary community of interest across the whole organisation | Share knowledge across tribes |
How it balances autonomy and alignment
Squads decide how to build their part of the product; leaders provide a clear mission and context. Chapters give people a professional home and consistent practices across squads. Guilds spread knowledge informally. The result is a matrix in which delivery is organised by squad and tribe, and people development by chapter.
Important caveat
The paper described how Spotify worked at one point in time. Spotify has said its organisation kept evolving and that the model was never meant to be copied as a framework. Organisations that adopt the labels without the underlying culture of trust, autonomy and continuous improvement often struggle.
When to consider it
- Several product teams need autonomy but must share technology and standards.
- You want people to grow their craft while working in cross-functional teams.
- Leadership is ready to trust teams and decentralise decisions.
Frequently asked questions
Is the Spotify model a framework?
No. It was a description of one company's way of working at one time, not a prescriptive framework.
In the Spotify model, what is the difference between chapters and guilds?
A chapter is a formal group of people with the same skill within one tribe, with a chapter lead. A guild is an informal, voluntary community across the whole organisation.
What is the Spotify model?
A description, published by Spotify in 2012, of how it organised engineering into squads, tribes, chapters and guilds to balance team autonomy with alignment.
What are squads in the Spotify model?
A small, cross-functional, self-organising team with a long-term mission for part of the product, similar to a Scrum team.
What is a tribe in the Spotify model?
A group of squads working in a related area, kept small enough for people to know each other; the paper suggested under about 100 people.
What is a chapter in the Spotify model?
People with the same skill within a tribe, such as testers, led by a chapter lead who is also their line manager.
What is a guild in the Spotify model?
A voluntary community of interest across the whole organisation, used to share knowledge on topics such as testing or web development.
Does Spotify still use the Spotify model?
Spotify has said its organisation kept evolving and that the model described one point in time. It was never meant to be copied as a fixed framework.
Why do companies struggle with the Spotify model?
Many adopt the labels without the culture of trust, autonomy and continuous improvement that made it work, so little actually changes.
What is a chapter lead in the Spotify model?
The line manager for people in a chapter, responsible for their growth and for consistent practices, while usually also working in a squad.
What can I learn from the Spotify model?
Small autonomous teams with clear missions, communities of practice and leaders who provide context rather than control. See Agile team structures.