Spotify Model

Also known as: Squads, Tribes, Chapters, Guilds

framework · computer science · organizing-schema

Organizational pattern from Spotify circa 2012, widely emulated and often misapplied.

An organizational pattern for scaling agile teams using cross-functional 'squads' grouped into 'tribes', with 'chapters' connecting people of the same discipline across squads and 'guilds' as voluntary communities of interest. Documented by Henrik Kniberg and Anders Ivarsson around 2012 based on Spotify's organizational structure at the time, the model became enormously popular as a template for scaling agile in technology organizations. Spotify itself has acknowledged that the model wasn't fully accurate even when documented and that the company has substantially evolved away from it; nonetheless the terminology persists in agile transformation contexts.

Originators

Henrik Kniberg; Anders Ivarsson high

Year / Decade

2012 high

Primary sources

Kniberg, H. & Ivarsson, A. (2012). 'Scaling Agile @ Spotify' (whitepaper) high

Band notes

Frequently cited and frequently misapplied; Spotify itself has acknowledged the model wasn't representative even at the time.

Core components

Squads (cross-functional autonomous teams)
Tribes (collections of related squads)
Chapters (discipline-aligned groups within tribes)
Guilds (cross-organizational communities of interest)

Primary use case

Reference template for scaling agile in technology organizations; often used in agile transformation initiatives.

Common criticisms

Was an aspirational snapshot, not a steady-state description, even when documented
Spotify itself moved away from key elements
widely cargo-culted without understanding the cultural prerequisites
treats organizational design as transferable when it depends on specific context.

Lineage

Siblings: Scrum, SAFe, LeSS, Holacracy
Derived from: Agile Manifesto