The top 3 points you should have paid attention to in the Spotify Engineering Culture videos that aren’t Squads, Chapters, Tribes, Guilds

Aligned autonomy

Alignment vs autonomy in a 2x2 matrix
Alignment vs Autonomy (picture extracted from part 1, drawn by Henrik Kniberg)

Creating trust-at-scale (across boundaries)

“Anything that is human is mentionable, and anything that is mentionable can be more manageable.”

Fred Rogers (aka Mr. Rogers)

Decoupling (to enable autonomy)

Stage #1: Market Development; Stage #2: Growth; Stage #3: Maturity; Stage #4: Decline
From “Exploit the Product Life Cycle” by Theodore Leavitt, Harvard Business Review Nov 1965
Product capability dependent on a single technical service (fine); product capability dependent on two technical services (fine); two product capabilities dependent on one technical service (might not be fine)
Don’t couple product capabilities (especially at different life cycle stages)
“Market Development” services can depend on “Growth” or “Mature” services; “Growth” services can depend on “Mature” services
Services should only depend on other services that are as stable or more stable

Spotify Models are for the obedience of fools and the guidance of the wise

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store