📎 Webclip
Spotify’s Failed #SquadGoals
Spotify’s squad model is presented as an aspirational way of working that was never fully implemented, then later copied as if it were a finished framework. The post says the model failed at Spotify itself and should not be treated as a template for other companies.
Reading notes#
- The original Spotify model used unusual names such as squads, tribes, guilds, and chapter leads for a matrix organization.
- Product managers and designers were managed in the team structure, but software engineers were managed through chapter leads across teams.
- The matrix structure created more coordination problems than it solved because product managers lacked a single engineering peer accountable for delivery.
- Spotify’s autonomy focus left cross-team collaboration, success measures, and alignment underdefined.
- Many teams lacked basic Agile knowledge, so they were left to experiment with process changes without shared guidance or enough coaching.
- The post argues that collaboration is a skill and cannot be assumed as an existing competency.
- The post says Spotify’s special vocabulary made the model seem more novel than it was and obscured the fact that it was mostly cross-functional teams with weak management structure.
- The author concludes that companies should keep researching organizational design instead of copying Spotify’s model.
