Why platform teams fail
A note on the gap between a platform that is technically correct and one that teams actually adopt.
- Topics
- Platform Engineering
- Adoption
- Org Design
- Tags
- platform
- teams
- adoption
The platform is not the product
Teams do not adopt a platform because it is well-architected. They adopt it because it removes a real, recurring pain faster than solving that pain themselves.
The most common failure mode I see is a platform team building the platform they wish existed, then lobbying engineering teams to change their workflow to fit it.
Adoption follows usefulness
Usefulness is measured in the language of the team that feels the pain: minutes saved per week, incidents avoided, cognitive load removed, time to first PR.
If the platform cannot name the pain it removes, it is a tax, not a tool.
What I am watching
How many capabilities were asked for twice before being productised. How many were pushed top-down. The ratio predicts adoption better than any architecture review.