A sales operations analyst spends a Tuesday afternoon building something with an AI agent. By five o'clock it can read a new inbound lead, check it against the CRM, pull the prospect's recent news, draft a first email in the account executive's style and drop the whole package into the right queue. It works. On Wednesday she shows her manager, who says it's great and that they should loop in the head of territory planning. The territory model was designed in 2019 and assumes leads arrive in a spreadsheet every Monday. Six months later the agent is still a demo.
Nothing in that story is a technology problem. The model did its part on the first afternoon. Everything that followed was people, and the structure those people sit inside.
The gap moved, and most companies didn't notice
For most of the last decade, the honest answer to "can we automate this?" was "partly, with a lot of engineering, and it will break on the edge cases". The bottleneck was capability. You could hold a strategy offsite about AI and nothing much would happen, because nothing much could.
That has changed. Agents can now draft, summarise, classify, reconcile and write working code well enough that, in most knowledge work, the limiting factor has become the organisation's willingness to let them. The capability gap closed faster than anyone planned for, and the adoption gap widened over the same period, because the thing that has to change on the other side isn't software.
Economists have a name for an earlier version of this. The Solow productivity paradox described computers showing up everywhere except in the productivity statistics. The usual explanation, in hindsight, is that firms bolted the new machines onto old ways of working, and the gains only arrived once the work itself was reorganised around them. That took years. We are watching the same film again, with a faster first act and an identical second one.
Your org chart is a map of old constraints
An organisation chart looks like a diagram of authority. It is really a fossil record. Every box exists because, at some point, a certain kind of work needed a certain number of people, and those people needed someone to coordinate them. The legal team reviews contracts because contracts needed reviewing by lawyers. Marketing operations exists because setting up a campaign took enough hours to justify a team.
Conway's law says systems end up mirroring the communication structure of the organisation that builds them. The corollary nobody enjoys is that an organisation also resists any system that doesn't mirror it. Put an agent in front of a process that crosses three departments and it will happily do the work end to end. The org chart will not. Each department still has its own approval step and its own definition of done, so the agent's output has to be chopped back into pieces that each box can process in turn.
The result would be comic if it weren't expensive. A machine produces a finished piece of work in four minutes, and then the work is carefully disassembled so it can travel through a structure built for a time when it took four people four days.
Meet the person who hasn't changed a process since 2019
Every company has one, and usually several. They are a VP or a director, often very good at their job, and they own a process that works. Not brilliantly, but reliably: the monthly forecast, say, or the vendor onboarding checklist. They built it, or inherited it and tamed it, and it has not had a serious redesign since before the pandemic.
This person is acting rationally. The process is part of their standing in the company. They know its quirks, and when it goes wrong they know which lever to pull. Replacing it with an agent-driven version asks them to give up the thing that makes them valuable in exchange for a promise. And the promise usually comes from someone more junior, holding a laptop.
There is a quieter fear too. A process that hasn't changed in years has accumulated workarounds, and the owner knows where they are buried. Redesigning it means digging them up. An agent that follows the official procedure will very quickly discover that nobody follows the official procedure, and that discovery lands on the owner's desk.
So the response is rarely a refusal. What you get instead is "interesting, let's do a proper evaluation", followed by a working group, followed by a pilot scoped so narrowly that it cannot fail and cannot matter.
Why buying more tools makes it worse
The instinctive fix is procurement. If adoption is slow, buy a better platform, hand out licences to everyone, run a lunch-and-learn. This mistakes availability for permission. Most employees in most offices already have access to capable AI tools, sanctioned or otherwise. What they don't have is the authority to change how their team's work flows.
A support agent who uses AI to draft replies twice as fast doesn't change the support operation. She finishes her queue early and gets assigned more tickets or, more likely, eases off a little so as not to make a fuss. The escalation rules and the handoff to billing are exactly as they were. Individual productivity rises and organisational throughput barely moves, because throughput was never governed by how fast one person typed.
This is where most AI programmes stall: plenty of personal use, a few impressive demos, and almost no change to how the company operates. The tools spread horizontally. The authority to change processes sits vertically, and it hasn't moved.
What changing the structure actually involves
If the bottleneck is structural, the fix has to be structural too, and that is less glamorous than buying software. A few things tend to work.
Start with a process, not a tool. Pick one workflow that crosses a departmental line and annoys everyone involved, such as the path from a signed deal to a customer being live. Map how it actually runs, not how the wiki says it runs. Then ask which steps exist only because a human used to be the slowest part. Those are the steps an agent can absorb, and they are more often handoffs and approvals than the work itself.
Give one person ownership of the whole flow, across the boxes. This is the uncomfortable bit. It means a manager in operations gets a say over a step that currently belongs to finance. Without it, every department optimises its own slice and the agent gets chopped back into pieces.
Bring the process owner in early and make them the author of the new version rather than its casualty. The director who has run the forecast since 2019 knows more about where it breaks than anyone in the building. Treat that knowledge as the specification. People defend what they helped build, and they stop defending the old thing once they've been allowed to redesign it.
Then measure the flow, not the tool. "Seats activated" tells you nothing. "Days from signature to go-live" tells you whether anything changed.
The hard part is now organisational
For a long time, being good at AI meant being good at the technology. That skill still matters, but it is no longer the scarce one. The scarce skill is redrawing a reporting line, retiring a sign-off, persuading a capable director to let go of a process they're proud of.
None of that shows up in a model release. It shows up in who is in the room when a workflow gets redesigned, and whether anyone in that room has the authority to delete a box from the chart. If your agent pilot is six months old and still a demo, don't wait for a better model. Find the meeting where the process gets decided, and check who isn't in it.
