Platform Team Vocabulary — Team Topologies Exercises

1 / 5

A VP of Engineering describes a team as "stream-aligned."
What best describes a stream-aligned team in Team Topologies?

Correct: B. In Team Topologies, a stream-aligned team is the primary team type — it is aligned to a flow of business value (a product area, customer journey, or service domain) and owns that stream end-to-end, including build, deploy, and operate. It is not about data streaming or sprint cadences.

Team type	Primary purpose
Stream-aligned	Owns a business domain or customer journey end-to-end
Platform	Provides self-service infrastructure and tooling to stream-aligned teams

2 / 5

An engineering director says: "We need a platform team to reduce cognitive load on our stream-aligned teams."
What is the primary goal of a platform team in Team Topologies?

Correct: B. A platform team's job is to make stream-aligned teams more productive by providing high-quality, self-service internal capabilities. The key measure of success is reducing cognitive load on consuming teams — not controlling or gatekeeping their work.

Role	Relationship to stream-aligned teams
Platform team	Enables faster delivery; self-service; reduces cognitive load
Old-model ops/infra	Acts as gatekeeper; teams raise tickets and wait for infrastructure work

3 / 5

A company forms an "enabling team" focused on helping squads adopt test automation practices.
How does an enabling team differ from a project team delivering features?

Correct: B. An enabling team's goal is to grow capability in stream-aligned teams, not to do the work for them indefinitely. It is a temporary, coaching-oriented engagement — the team embeds, transfers knowledge and practices, then steps back. This is distinct from a permanent shared service.

Team type	Engagement model
Enabling team	Temporary; transfers knowledge; exits when capability is established
Shared service / project team	Permanent provider; other teams depend on it for ongoing delivery

4 / 5

Your organisation has a separate team that owns the real-time recommendation engine. A colleague describes it as a "complicated-subsystem team."
What characterises this team type?

Correct: B. A complicated-subsystem team owns a part of the system that is intellectually complex — requiring rare specialist knowledge to work on safely. Examples include machine learning recommendation engines, physics simulations, digital signal processing, or cryptographic implementation. The team exists to contain and manage that complexity so stream-aligned teams don't need to understand it.

Complicated-subsystem team owns	Example
Deep specialist knowledge required	Real-time ML recommendation engine
Specialist knowledge required	Custom cryptographic protocol, physics simulation

5 / 5

A platform lead justifies a new internal CLI tool by saying it "reduces cognitive load for stream-aligned teams."
In Team Topologies, what does reducing cognitive load mean for a team?

Correct: B. Cognitive load in Team Topologies refers to the total mental capacity a team must apply to understand and operate its system. When a team has too much cognitive load — because it also owns infrastructure, CI/CD, observability, and security tooling — it cannot focus on its core domain. A platform team reduces this load by abstracting complexity behind a self-service interface.

Cognitive load type	Example
Intrinsic (keep)	Understanding the team's own business domain logic
Extraneous (reduce)	Managing Kubernetes config, setting up CI pipelines, writing observability instrumentation