## Metadata - Author: [[jason-yip|Jason Yip]] - Full Title:: My Critique of “The Spotify Model”: Part 1 - Category:: #🗞️Articles - URL:: https://jchyip.medium.com/my-critique-of-the-spotify-model-part-1-197d335ef7af - Finished date:: [[2023-02-04]] ## Highlights > I think originally, there was a valid assumption that Squads had enough Agile background to make pretty good calls. As Spotify, and really the overall industry, has grown, there are more and more people with a shallow or warped understanding of Agile. ([View Highlight](https://read.readwise.io/read/01grcn42fajexk5a8rtf71nnpj)) > Squads” at Spotify are not a synonym for “team” but specifically a cross-disciplinary, autonomous, product development team. Marty Cagan calls this an [Empowered Product Team](https://www.svpg.com/empowered-product-teams/) ([View Highlight](https://read.readwise.io/read/01grcn9dvssgq5261cp6p2x0a9)) ##### Common mistakes I saw with some Squads > • Insufficient cross-pollination amongst Squads leading to unnecessary variation and relearning; > • Missing context for how the Squad’s mission fits within broader strategy — which can lead to Squads lasting longer than appropriate ([View Highlight](https://read.readwise.io/read/01grcnb0g4vd75h98e73p4zd44)) > When faced with these problems, newly hired leaders might suggest “there’s too much autonomy” when the actual correct answer is “[aligned autonomy](https://jchyip.medium.com/why-aligned-autonomy-is-an-ongoing-struggle-efa62e272d5d)” (see later). ([View Highlight](https://read.readwise.io/read/01grcnc0cj81cftzmjxpfy90wn)) - Note: I have literally heard this answer > services are supposed to have clear Squad owners, if the owning Squad is too busy, a requesting Squad can make their own changes and submit it for review ([View Highlight](https://read.readwise.io/read/01grcngsaz8645wys60fmrpptw))