Skip to content
BENIBIX Learn

Complicated-Subsystem Team

Also known as Complicated Subsystem Team, Complicated-Subsystem Teams

A small expert team that owns one hard part, so other teams need not learn it.

Think of it like

It is like the one person on a ship who fixes the engine. Everyone else does not need to know how.

Example

A music app has a team of four that owns the song match tool. The other teams call it to suggest songs and never touch the maths inside.

Why it matters

Some work needs skills that are rare and slow to learn. One team keeps that load off every other team.

Definition

A complicated-subsystem team looks after one part that needs rare, deep skill. It is one of the four team types in Team Topologies. The part might be a video engine, a pricing model or a face match tool. Only a few experts can build it well. So one small team owns it, and the other teams use it without learning the hard parts. Most firms have few of these teams, or none.
This team works side by side with the teams that use its part. That is most true at the start.

Common mistake

Making one for every shared part. It is only for parts that truly need rare skill.

Key takeaways

  1. 1
    Rare skill. The part needs deep skill.
  2. 2
    Use, not learn. Others use it, not learn it.
  3. 3
    Few of them. Most firms need few of these.