GoKawiilThe agentic platform defines what needs to be provided. Team Topologies defines who provides it, and how teams interact to make it happen.
In the first article of this series, we asked the what: which systemic capabilities (context, guardrails, tooling) are needed to produce reliable applications at scale. The answer was the agentic platform, and at its core, the agentic factory: the mechanism where agents plan, code, test, and ship.
But a platform does not build itself, and more importantly, it is not consumed the same way it is built. A fundamental question remains: who does what?
The real problem: the cognitive load of agentic production
Before asking who does what, we need to understand why the question is different this time.
Building an application used to mean orchestrating roles over time: one person designed, another challenged the architecture, a third tested, a fourth deployed. The complexity was real, but distributed — across several people, and spread over time. Each role asked its questions in turn.
Agents change the equation. They do not ask questions: they produce answers, immediately. They never tire, never rest, never wait. Their speed is their strength, and their trap. All the questions that roles used to raise sequentially, the human steering the agent must now anticipate upfront, in parallel, in the short window of a prompt. Poorly framed, an agent does not slow down: it produces fast, and off target.
Cognitive load does not disappear with AI — it transforms. It first becomes an anticipation burden: everything the human must foresee before launching the agent, or the output will fall short. And because the agent produces continuously, without human rhythm, it also becomes a cognitive throughput problem: a sustained flow of decisions over time. The real challenge of agentic production at scale is not that complexity grows — it is that complexity compresses, onto a single person and into a timeframe they cannot absorb alone.
This is exactly what the platform addresses. It absorbs part of the anticipation burden by making itself queryable by the agent: “don’t worry about security” means the agent will ask the platform how to proceed, and deterministic controls will enforce the outcome downstream. The platform does not eliminate thinking — it narrows the set of questions the human must carry, letting them focus on what truly matters: the contested, structural decisions where human judgment remains irreplaceable.
Cognitive load is therefore no longer just, as Skelton and Pais describe, a quantity to distribute across teams. In the agentic world, it is also a throughput to regulate over time. Team Topologies tells us how to distribute; we still need to say how to absorb. That is the subject of this article.
... continue reading