The Spotify story
As Spotify grew past a few hundred engineers, every team was inventing its own way to plan, ship, and review. Coordination cost was eating the speed advantage of being smaller than the incumbents.
Standardizing the work itself would slow good teams down. Leaving the rituals up to each team made it impossible for leadership to compare progress, share wins, or unblock dependencies fast.
The squad/tribe model gave each team autonomy on what to work on while standardizing how they reviewed, planned, and shared progress. Different objectives per team, same operating cadence across the company.
- Autonomous squads with their own missions and metrics
- Shared review and planning rituals across squads
- Visible roadmaps and metrics across tribes
- Practices spread by example, not mandate
- Chapters and guilds that carried craft knowledge across teams
The Spotify model became one of the most studied (and copied, and debated) operating frameworks in modern tech, and let the company move faster than its size would predict.
Standardizing the rhythm — not the work — is what lets a growing org keep its early speed.