Org Web Adapter

Editing pages/failed_squadgoals_at_spotify.org

:PROPERTIES:
:ID:       50eb9c0a-b21e-46e5-b50f-8f69b02fcbf1
:END:
#+TITLE: Failed #SquadGoals at Spotify

- source :: https://www.jeremiahlee.com/posts/failed-squad-goals/
- tags :: [[id:a866bddb-50c9-4632-a274-8528bd823bfc][Software Lead Weekly]] [[id:5edece3e-8e0d-490d-b715-94c65c67e487][Company]] [[id:96180642-e796-4cc1-8462-e9fbb57416bc][Organization]] [[id:be2f35e5-1d09-4cd8-af9e-65e0fe12d616][Agile]] [[id:4bb8bd34-313b-4b4a-94c3-4043ddeac511][The Spotify Model]]
- related :: [[id:465c51ae-8103-4301-a2bc-9e80e5ce4641][Don't Do the Spotify Model]]

* Why Squads didn’t work at Spotify
:LOGBOOK:
CLOCK: [2020-05-01 Fri 13:09]--[2020-05-01 Fri 13:28] =>  0:19
:END:
#+BEGIN_QUOTE
1. Matrix management solved the wrong problem
2. It fixated on team autonomy
3. Collaboration was an assumed competency
4. Mythology became difficult to change
#+END_QUOTE

* Fixating on team autonomy over collaboration

#+BEGIN_QUOTE
With more teams, the need for a team to shift initiative decreases in frequency.
Both of these changes allow for teams to think more deeply and long term about
the problems they are scoped to solve. Faster iteration, however, is not
guaranteed. *Every responsibility a team cedes to increase its focus becomes a
new cross-team dependency.*
#+END_QUOTE

Autonomy leads to dependency graphs that become hard to control. Off sprint
cycles, different modes of working lead to resource starvation between groups (squads).

* Autonomy requires accountability

If every team is slightly different in how they work, you wind up with weird
subcultures within one company.