Skip to content
Knowledge beta

Four Team Types

Team Topologies Organizational Design

Most teams in your org should be stream-aligned. The other three types exist for one reason: to make those stream-aligned teams faster.

In the Team Topologies framework, every team maps to one of four types. The premise is that teams are the unit of performance; the primary type is the stream-aligned team, and the other three exist to reduce cognitive load on stream-aligned teams so they can focus on delivering value. What follows is our consulting perspective on applying these ideas.

Stream-Aligned Team

A team aligned to a continuous flow of value for a specific product, service, or user journey, responsible for end-to-end delivery. This is the fundamental team type; most teams in a well-designed organization should be stream-aligned.

Examples: Mobile banking app team, customer onboarding team, mortgage origination team, fraud detection product team.

Anti-patterns: Team doesn’t have end-to-end ownership. Constantly waiting on other teams to deliver features. Split between multiple products or services.

Key practices: Product trios, dual-track agile, backend-for-frontend, contract testing, innersourcing.

Enabling Team

A team that helps stream-aligned teams adopt new capabilities, practices, or technologies through coaching, consulting, and facilitation. Enabling teams are temporary by design; the goal is to transfer capability, not create a permanent dependency.

Examples: Cloud/PaaS onboarding team, quality engineering guild, agile coaching team, ProductOps team.

Anti-patterns: Becomes a permanent dependency. Does the work FOR teams instead of WITH teams. Lots of building, limited interactions.

Key practices: Embedded enablement (temporarily join a stream team, 6-12 week engagements), import/curate/share (research emerging technologies, create playbooks, guide communities of practice), platform discovery (spot patterns across teams, identify capability gaps, advocate for platform investments).

Common evolution: Embedded Enablement -> Spot Coaching -> Platform Fills Gap.

Platform Team

A team that provides self-service, reusable capabilities (e.g., infrastructure, tooling, shared services, APIs) to reduce cognitive load for stream-aligned teams. The platform should be treated as a product with its own roadmap, adoption metrics, and feedback loops.

Examples: Internal developer portal/CI/CD, design system/customer research, shared business APIs, observability and monitoring.

Anti-patterns: “Build it and they will come.” Ticket-driven instead of self-service. Built for the platform team’s convenience, not consumers.

Key practices: Golden paths, platform as a product, feedback loops with stream-aligned consumers, value-based adoption (create demand by offering value, not mandating use).

Complicated Subsystem Team

A team focused on designing and maintaining highly specialized, complex, or algorithmically intense components that require deep expertise. This type is rare and intentional; most “complicated” work should live within stream-aligned teams unless it genuinely requires specialist knowledge that would overwhelm a generalist team.

Examples: Fraud detection algorithm team, real-time trading engine team, video encoding/transcoding team, computer vision team.

Anti-patterns: Created just because work is “hard” (not actually specialized). Becomes a bottleneck for stream-aligned teams. Byzantine, bureaucratic intake systems.

Resources