Members' shelf
All 9 nodes on Naming & Classification are for members only.
Pay with the email you sign in with here, so the Pass is linked to this account.
Members' shelf
All 16 nodes on System Protection & Threat Modeling are for members only.
Pay with the email you sign in with here, so the Pass is linked to this account.
Team topologies
- Holds when
- When several teams build one system and must decide how they collaborate and where their boundaries fall.
- Evidence
- Conceptual framework; Bibliography checked
- Breaks down when
- Treated as a law that guarantees some setup is faster, applied by table, or used for one person or a tiny team, it misleads.
1. What happened
Whether two teams should explore closely together, or one should turn its work into a service the other helps itself to, is a question whose answer changes with the stage. This book starts from Conway's Law: if system structure mirrors the communication structure of an organisation, then deliberately designing team boundaries is itself an instrument of architecture[1]Skelton, M. & Pais, M. (2019-09-17). Team Topologies: Organizing Business and Technology Teams for Fast Flow. IT Revolution Press. Bibliographic details checked against the official record. First edition published 17 September 2019; second edition published 23 September 2025, with the subtitle changed to Organizing Business and Technology for Fast Flow of Value (see reference [5]). The names of the four team types and three interaction modes were checked against the two authors' website; the text of the book itself was not checked here..
The first thing it gives is four shapes along the axis of division of labour: teams aligned directly to a stream of value, teams whose job is raising the capability of others, teams owning a difficult subsystem, and teams that turn shared capability into a platform others help themselves to[1]Skelton, M. & Pais, M. (2019-09-17). Team Topologies: Organizing Business and Technology Teams for Fast Flow. IT Revolution Press. Bibliographic details checked against the official record. First edition published 17 September 2019; second edition published 23 September 2025, with the subtitle changed to Organizing Business and Technology for Fast Flow of Value (see reference [5]). The names of the four team types and three interaction modes were checked against the two authors' website; the text of the book itself was not checked here.. Those four are not ranks. They are shapes of function.
The second is three modes along the axis of relationship: high-frequency joint exploration, turning your output into a service the other side consumes on its own, and one side helping another build a capability[1]Skelton, M. & Pais, M. (2019-09-17). Team Topologies: Organizing Business and Technology Teams for Fast Flow. IT Revolution Press. Bibliographic details checked against the official record. First edition published 17 September 2019; second edition published 23 September 2025, with the subtitle changed to Organizing Business and Technology for Fast Flow of Value (see reference [5]). The names of the four team types and three interaction modes were checked against the two authors' website; the text of the book itself was not checked here.. That axis is the book's real contribution.
The third is that it asks for the relationship to be written down: each team publishes an explicit document describing how to work with us, which the book calls the Team API[1]Skelton, M. & Pais, M. (2019-09-17). Team Topologies: Organizing Business and Technology Teams for Fast Flow. IT Revolution Press. Bibliographic details checked against the official record. First edition published 17 September 2019; second edition published 23 September 2025, with the subtitle changed to Organizing Business and Technology for Fast Flow of Value (see reference [5]). The names of the four team types and three interaction modes were checked against the two authors' website; the text of the book itself was not checked here..
The fourth is the criterion for a boundary: cognitive load. What one team can genuinely hold has an upper limit, and overload is itself a signal to split[1]Skelton, M. & Pais, M. (2019-09-17). Team Topologies: Organizing Business and Technology Teams for Fast Flow. IT Revolution Press. Bibliographic details checked against the official record. First edition published 17 September 2019; second edition published 23 September 2025, with the subtitle changed to Organizing Business and Technology for Fast Flow of Value (see reference [5]). The names of the four team types and three interaction modes were checked against the two authors' website; the text of the book itself was not checked here.. In an article, the two authors attribute the characterisation of the concept to Sweller's 1988 work on cognitive load[4]Skelton, M. & Pais, M. (2021-01-19). Team Cognitive Load. IT Revolution. Bibliographic details checked against the publisher's record. Claims matched against the full text. In an article on the publisher's website, the two authors attribute the characterisation of cognitive load to the psychologist Sweller's work of 1988 and build team-level cognitive load on it. How the book itself cites that theory was not checked here..
And the item most easily skipped, which is also the most useful: interaction modes are expected to evolve[3]The two authors' website states that relationships between teams will change as new goals are set and teams discover new things. This site therefore presents the relationship axis as something that can step up and down, not as a fixed arrangement.. Joint exploration is for the discovery period, and once the boundary has been felt out, the relationship should step down to consuming a service. Stepping a relationship up and down is the organisational version of refactoring an architecture.
2. Why this matters to you
Swap team for each of your own lines and the page lands, whether the line has another person behind it, another of your own roles, or a model.
The first thing that transfers is the Team API declaration document. When you work with a line, what the other side (or your future self) needs to know comes down to a few items: what this line is responsible for, what it is not responsible for, how to hand it work, and what situations require asking you first. Write those down and you have an interface document. Most friction in collaboration is not a matter of capability. It is that this document does not exist, so the terms get renegotiated every time.
The second thing that transfers is more counter-intuitive, and it is the headline on this page: collaboration is not better for being closer. Each of the three modes has its moment. At the start of something, with the boundary still unclear, you need frequent back and forth. Once it is clear, continuing to go back and forth is waste, and what belongs there instead is fixing it into given this input, return this output, after which you stop taking part in the process.
That is especially visible when working with a model. Exploring a new task, you will go twenty rounds, and the value of those twenty rounds is finding the boundary. The problem most people have is that after finding it they keep going twenty rounds, because nothing was ever fixed down. What this page says is that this is not diligence. It is a relationship that never stepped down.
The third is the cognitive load line. When you find that the scope you hold has reached the point where every switch means loading it all again, that is not a failure of will. The scope has passed its limit. The limit is a criterion, not a shortcoming.
If you work alone or in a very small team, the part of this page you can use most is the second item above; there is no need to rush to fit the shapes of division of labour onto yourself.
Lab cases Written only where there is evidence
No field record for this node yet.
- A common retelling, Team API is a term the two authors coined: this site can say only that the book put it forward and popularised it, and neither claims nor denies the coinage. #
- A common retelling, this is a set of empirical laws: it is an organisational design taxonomy from an industry publisher, not peer-reviewed theory. It works as vocabulary, not as law. #
- A common retelling, the four shapes are four kinds of team, so just apply them: a taxonomy is not an algorithm. When to step a relationship down from joint exploration to consuming a service remains a matter of judgement. #
How to read the source notes “Bibliographic details checked” means author, year, title and venue were confirmed. It does not mean the source's claims were checked. “Matched against the full text” means the claim was compared with the text of the source itself. Definitions as of 2026-09-20.
- [1] Skelton, M. & Pais, M. (2019). Team Topologies: Organizing Business and Technology Teams for Fast Flow. IT Revolution Press. ↩
- [3] Skelton, M. & Pais, M. (2019). Team Topologies: Organizing Business and Technology Teams for Fast Flow. IT Revolution Press.
- [4] Skelton, M. & Pais, M. (2021). Team Cognitive Load. IT Revolution. Published 19 January 2021. ↩
Tell me when a new shelf opens
Tell me when a new shelf opens
Shelf notices are sent only when a new shelf opens or when the reading rules change.
Tell the editor privately: a correction, a counter-example or where it applies
Submissions are read only by the editor, and nothing is published before they are handled. Once a note is handled, a summary and response written by the editor are published. No sign-up is needed, and the nickname may be left blank.
We have your note