
Part 1
Why Federated Design Systems Keep Failing
Why do federated design systems keep failing? I watched it happen twice at Spotify. Here's what actually happened, where they broke down, and why centralised models usually work better.
Posts Series
I spent nine years at Spotify leading design systems and accessibility. During that time, I learned as much from what failed as from what succeeded. I'm sharing these insights not to critique decisions made at the time, but because I believe they're valuable and can help others navigate similar challenges.

Part 1
Why do federated design systems keep failing? I watched it happen twice at Spotify. Here's what actually happened, where they broke down, and why centralised models usually work better.

Part 2
Sometimes decisions are made for you. They're clearly wrong, and you can't change them. This is about how you lead anyway.

Part 3
Where you put your design system team within your organisation determines how they think, what they build, and whether the system stays a platform or the teams become a UI feature factory.

Part 4
Six years after introducing the system of systems model, what it became in practice, where the original vision held, and where it gave way.

Part 5
The costs we never planned for: the hidden load on the core team, local systems that stalled, a programme that came apart, and success the model had nowhere to put.
Does this sound like your organisation? I'd love to hear from you. I offer a free 30-minute conversation to explore whether I can help.
Shaun BentStudio 53° · 53°N · Preston & Manchester