Platform Teams & Enabling Teams
A platform team builds and maintains shared internal infrastructure (Kubernetes, CI/CD, observability, service templates) as a product for other engineering teams. An enabling team temporarily embeds with or consults for stream-aligned teams to build a specific capability.
Platform team = the road construction crew. They don't deliver pizza, but every pizza delivery team goes faster because the roads are smooth. Enabling team = a driving instructor who rides along temporarily until you pass the test.
Platform teams reduce cognitive load on stream-aligned teams by abstracting infrastructure complexity. The platform team owns the 'paved road': opinionated, well-supported ways to deploy a service, add observability, and manage secrets. The platform must have a product mindset — track adoption, gather feedback, provide documentation and support SLAs. If stream-aligned teams bypass the platform (shadow IT), the platform is not meeting their needs. Enabling teams are time-limited: they work with a stream-aligned team for 2–3 months to establish a capability (e.g., adoption of OpenTelemetry), then exit — leaving the stream-aligned team self-sufficient.
The anti-pattern is a 'DevOps team' that is actually a platform team operating as a gatekeeper: stream-aligned teams raise tickets, the DevOps team deploys. This creates a bottleneck, destroys team autonomy, and violates the 'you build it, you run it' principle. The platform team should provide self-service tooling so stream-aligned teams can deploy, scale, debug, and roll back without raising a ticket. 'Platform as a product' means versioning the platform, providing a changelog, and deprecating old APIs with notice — the same practices used for external-facing products.
I staff a platform team at roughly 1 platform engineer per 10 stream-aligned engineers. The platform team owns: the Kubernetes cluster, CI/CD pipelines (Argo CD, GitHub Actions templates), the internal service catalog, the observability stack (Prometheus, Grafana, Tempo), and golden path service templates. Stream-aligned teams can deploy to production on day one using the golden path — no tickets required. The platform team's OKR is measured by platform adoption and by stream-aligned team deployment frequency.
Treating platform team headcount as overhead. A well-staffed platform team multiplies the velocity of every stream-aligned team they support — it is one of the highest-leverage engineering investments a company can make.