Platform Team Anti-Patterns
You'll learn: How platform teams can accidentally undermine their mission by falling into common traps that hurt developer experience and platform adoption.
The Core Problem
Even well-intentioned platform teams can sabotage their own success. After building self-service capabilities, golden paths, and developer portals, teams sometimes drift into behaviors that contradict platform engineering principles. These anti-patterns typically emerge when teams lose sight of their "platform as product" mindset or when organizational pressures create misaligned incentives.
Common Platform Team Anti-Patterns
Becoming the Gatekeeper
When platform teams require approval for every infrastructure change or become bottlenecks for deployments, they've stopped enabling and started blocking. This defeats the self-service promise.
Over-Abstracting
Creating so many layers that developers can't understand what's happening underneath, or stripping away all flexibility. The platform becomes a black box that breaks mysteriously, with no escape hatches when golden paths don't fit.
Losing Touch with Users
Building features based on assumptions rather than user research and feedback loops. The platform team stops measuring developer experience metrics and ignores adoption signals showing pain points.
Feature Factory Mode
Treating the platform like a ticket queue instead of a product. Adding every requested feature without strategic prioritization or considering the maintenance burden, leading to a bloated, inconsistent platform.
Ivory Tower Syndrome
Platform team operates in isolation without inner source contribution models or clear interaction modes. Developers feel the platform is "done to them" rather than "built with them."
Key Takeaway: Platform teams must continuously guard against becoming gatekeepers, over-abstracting away context, or disconnecting from developer needs—the very behaviors that motivated platform engineering in the first place.