The Entry Fee for McKinsey's 60 Percent Smaller Teams
The agentic delivery numbers are real. The preconditions underneath them are the part nobody will quote.
McKinsey just published the stat that every AI strategy deck will be quoting for the next year. In Rewiring software delivery for the agentic era, the firm reports that organizations adopting agentic delivery models are seeing threefold to fivefold productivity improvements alongside a 60 percent reduction in average team size. Teams of eight to twelve become pods of three or four: a product owner, a tech lead, and an AI-enabled engineer supervising a factory of agents that works through the night.
The accepted read writes itself. AI makes teams smaller and faster. Buy the agents, shrink the teams, collect the productivity.
But the article also lists, almost in passing, what the model requires before any of it works, and that list is the part worth reading twice. The business needs a clear enough vision of what is being built that agent output can be judged against it. The technical environment has to be standard and consistent. The path from requirements to code has to follow a structure agents can reliably interpret. Requirements, guardrails, and specifications have to be codified in machine-readable formats instead of scattered across disconnected documents. And the same core stakeholders have to stay engaged across the entire value stream, or everything downstream turns into rework.
Strip out the agent vocabulary and read that list again. It describes a team that has made its own work completely legible to itself. Decomposed operations, explicit intent, defined review gates, and shared context that lives in the system rather than in someone’s head. The agents are downstream of all that. So is the 60 percent.
Nimbleness is a visibility property
“Nimble” usually gets read as small and fast, which is why the team-size stat will travel further than anything else in the article. But team size was never the constraint. The constraint is whether anyone can see the work structurally.
A team that understands its own work as a system of operations — what gets produced, what gets handed off, what intent governs each piece, where judgment is non-negotiable — can re-form around a new mission in days. A team that experiences its work as a continuous stream of tasks, meetings, and messages is rigid at any size, and handing it a factory of agents produces exactly what McKinsey warns about: fragmented output that nobody trusts. The small team is a consequence of the legible one.
Structure is a fossil of coordination cost
There is a reason team structure resists this, and Ronald Coase named it in 1937. The Nature of the Firm argued that firms exist because coordinating through the open market costs something: finding people, negotiating, enforcing agreements. The same logic shapes structure inside the firm. Layers, roles, and handoffs exist to manage the cost of communication, translation, and oversight. The professional services pyramid is the cleanest example anywhere — juniors produce, seniors review, and the ratio between them is priced directly into the business model. Org charts are fossils of what coordination used to cost.
When a technology collapses specific coordination costs, structure sized for the old costs turns from scaffolding into drag. McKinsey’s own pipeline analysis makes this concrete: the bulk of delivery effort sits in requirements through coding, where humans spend their days translating intent from one artifact to another. Every translation is a coordination cost. The agentic model removes the human from those handoffs entirely, with review concentrated at defined gates. The structure built to manage the handoffs does not dissolve on its own. Someone has to notice it is now load without purpose.
Intent travels better than instructions
If detailed structure recedes, something has to replace it, and the strongest answer is older than software. After Napoleon dismantled the Prussian army at Jena in 1806, the reformers who rebuilt it concluded that battlefield conditions changed faster than orders could travel. Helmuth von Moltke the Elder later gave the principle its lasting form: no plan of operations survives first contact with the enemy. So commanders stopped issuing detailed instructions and started transmitting intent — what must be achieved and why — leaving subordinate officers to decide how, on the ground, as conditions shifted. The Prussians called it Auftragstaktik. The modern term is mission command.
McKinsey’s daily sprint is mission command in a different uniform. During the day, humans resolve ambiguity, set guardrails, align stakeholders, and define what acceptable looks like. Overnight, execution runs against that intent at scale. In the morning, review happens at the gates. Intent travels into the night shift; instructions never would.
This is the actual design principle for team nimbleness in the agentic era: a mission plus short-term goals. The mission states what must be true and why it matters. The short-term goals create checkpoints where intent gets recalibrated against what execution revealed. The compression from two-week sprints to daily cycles matters less than what made it possible — clearly transmitted intent needs far less planning apparatus wrapped around it.
Getting legible
None of this tells a leader how to make a team legible to itself, and I am suspicious of anyone selling a template for it. The honest version is a set of questions, asked of the team’s work rather than its org chart. What operations does this team actually perform — operations, not roles? Where does intent currently live: written somewhere a system could read it, or in the heads of two senior people? Which handoffs in the workflow are translation, and which are judgment? What does “done” mean for each operation, and who decides?
Most teams cannot answer these today. That is not a failing; nobody has ever asked them to see their work this way. The structural view is developed, not installed, and there is no vendor for it. Which is precisely why it is the work behind the agentic numbers rather than a line item in the deployment budget.
The harder case
Software is the easy case, and McKinsey says so directly: the way agents are being used in software development is a harbinger for broader delivery models. Decades of version control, ticketing systems, and CI/CD have already made software work partially legible. Requirements and code leave trails by default.
Professional services work mostly does not. In a law firm, intent lives in precedent files, marked-up drafts, and the accumulated judgment of senior practitioners. The pyramid prices translation in as oversight and calls it development. The legibility debt is far larger than in software, which means the work behind the numbers is heavier — and the advantage for any firm that does it is correspondingly larger, because almost nobody in the market has started.
There is also a structural bind worth naming. Re-decomposing a team’s structure requires someone to sign for it, and in conservative institutions nobody wants their name on the new org chart. Missions carry less weight. A mission expires; a structure has to be defended indefinitely. That makes mission-based nimbleness more available to a regulated institution than restructuring. A three-month mission with short-term goals and defined review gates asks nothing of the org chart, and it quietly builds the legibility that any future structure will depend on.
The 60 percent will circulate as proof that AI shrinks teams. Read the preconditions instead and it proves something quieter: the organizations collecting those numbers did an unglamorous body of work first. They made the work visible and the intent explicit before any agent touched it. The team got smaller because the work got legible.
AI doesn’t make teams nimble. It exposes which teams already did the work of seeing themselves clearly.
If this resonated, subscribe to get the next piece on the work behind the work — the human capability development that AI adoption quietly depends on.