Spotify model
The Spotify model is an organisational structure for engineering teams — described in two 2012 papers by Henrik Kniberg and Anders Ivarsson — that arranges engineers into Squads (cross-functional 6-12 person teams, each owning a slice of the product), Tribes (collections of squads in a related area), Chapters (cross-squad communities of practice for a discipline, e.g., all backend engineers), and Guilds (broader interest-based communities).
The model spread widely because it offered a vocabulary for the structural decisions every scaling engineering org makes. Worth noting: Spotify itself has explicitly stated the model was a snapshot of a moment in 2012, not a steady-state blueprint, and the company evolved past it. The pattern of squad autonomy + chapter expertise + cross-cutting guilds remains influential even where the specific labels aren't used. Modern formulations (Team Topologies' stream-aligned + enabling teams; the Inverse Conway Maneuver) generalise the underlying insight: large engineering orgs need explicit decisions about which axis (product, technology, customer segment) drives the team boundaries.
Related terms
- Team Topologies
Team Topologies, codified in the 2019 book by Matthew Skelton and Manuel Pais, is a framework for organising engineering teams using four team types and three interaction modes.
- Conway's Law
Conway's Law, formulated by Melvin Conway in a 1968 paper, states that any system's design mirrors the communication structure of the organisation that built it.