Team Structures

Team structure determines how platform work is owned, adopted, and improved. Do not design the technical platform without designing the teams that operate and consume it.

Common team shapes

• Stream-aligned teams own product or business capabilities.
• Platform teams provide paved roads and shared capabilities.
• Enabling teams coach, unblock, and transfer skills.
• Complicated-subsystem teams own highly specialized domains.

Platform team responsibilities

A platform team typically owns:

• Golden paths and service templates.
• Runtime platform standards.
• CI/CD workflows and reusable modules.
• Observability and operational defaults.
• Security and compliance guardrails with security partners.
• Developer support, documentation, and adoption metrics.

Responsibility boundaries

Design questions

Ask:

• Which teams own production outcomes?
• Which teams build and support paved roads?
• Which work is self-service versus ticketed?
• Who approves exceptions?
• Who funds shared platform work?
• How are platform priorities selected?

Watchouts

• A platform team without product management becomes a ticket queue.
• Central teams can become bottlenecks if self-service is weak.
• Product teams still own their services after adopting platform tools.
• Governance without enablement creates bypass behavior.