Skip to content

Blog

Teams that rebuilt their org chart got more out of AI

McKinsey surveyed about 300 enterprises on AI adoption. Top performers were 7x likelier to run AI-native workflows, while 70 percent have not changed roles at all. Pod restructuring is an upstream investment.

Written by

Organization and roles

Published: 30 April 2026 Updated: 2 min read

McKinsey studied enterprise AI adoption across hundreds of companies.

Seventy percent have not changed their roles at all. The top performers were seven times more likely to run AI-native workflows across the whole lifecycle.

An org chart effect, not a tool effect

Same industry. Same talent pool. Same models. Same vendor contracts.

One bank in the dataset restructured into pods and saw merges up 51 percent, and agent consumption up 60x.

This is an org chart effect, not a tool effect.

Why the 2020 topology breaks

Teams of 8 to 12 with two-week sprints, story points and burndown charts were designed for human-paced delivery. Coordination overhead was the dominant cost. That made bigger teams worth it. Story points were a way to amortise that overhead.

When a 3-person pod with a clear spec and an agent fleet ships in two days what a 10-person team scheduled for two weeks, the math inverts:

  • Coordination is now the bottleneck, not capacity.
  • Spec quality determines velocity, not story-point estimation.
  • Verification gates determine throughput, not standup attendance.
  • The smallest unit that ships independently is the team.

Pods are an upstream investment

Pod restructuring is an upstream investment in the same pattern that works for agents themselves: small unit, focused task, sharp interface, verifiable output.

It takes 3 to 6 months of organisational work. There is no shortcut. The companies skipping that work are paying for AI usage that their org chart will not let them realise.

The signal for CTOs

If the team topology you ran in 2024 is still the team topology you run in 2026, the AI budget is funding overhead, not output. The redesign is the unlock. The tools are the consequence.

McKinsey frames this as a structural shift on the order of waterfall to agile. They are not wrong. The 2020s topology is being replaced the same way the 2000s topology was. The companies that move first set the price for the ones that wait.

Are you funding tools, or funding the org chart that makes them work?

Further reading

  1. Moving faster with AI only happens when it is a goal A software factory gives you output speed. Outcome speed needs the organization to change around it, and a change that isn't a goal loses to every change that is. 2 min readShort post
  2. AI adoption is a leadership problem Teams with every AI tool available still drop them within weeks. Three leadership responsibilities decide whether adoption sticks: unblock usage, make adoption visible, reduce fear. 1 min readShort post
  3. If agents can run a company, what is a company for? A panel on responsible agentic development ended on a question it could not answer: follow the efficiency logic all the way to zero employees, and what is left of a company? 2 min readShort post

All 15 posts on Organization and roles

ClientsCase study: A large DIY retailer in Germany

Test the constraint in your system

The Factory Readiness Assessment connects this research to your value stream, your data, and the next decision.

Training on this topic: Agentic Engineering for Engineering and Product Leaders
See the assessment

Want to check one team first? The self-check: twelve yes or no questions, three minutes, instant result, no account. Take the self-check