How Agentic Systems Are Changing Organisations

What is How Agentic Systems Are Changing Organisations?

Tony Wood analyses how agentic AI dissolves the coordination layer that defines modern organisations. The coordination tax, the execution layer shift, the verification flywheel, and what genuinely human work survives..

What is I. The Coordination Tax?

What is II. The Execution Layer Shift?

What is III. The Org Is Moving to Code?

What is IV. The Verification Flywheel?

Key concepts in How Agentic Systems Are Changing Organisations

How do how agentic systems are changing organisations relate to agentic commerce?

  1. Agency requires intentional delegation — every agentic system begins with a designed act of delegation
  2. Trust is the primary material — AXD works in trust rather than attention
  3. Absence is the primary use state — the most consequential experiences happen when no one is watching
  4. Relationships have temporality — agentic experiences accumulate history over time
  5. Outcomes replace outputs — AXD designers specify results, not interfaces
DimensionTraditional UXAgentic Experience Design (AXD)
Primary materialAttention and affordanceTrust and delegation
User statePresent, navigatingAbsent, delegating
Design outputScreens and interfacesOutcomes and constraints
Temporal modelSession-basedRelationship-based
Success metricTask completionTrust calibration

Frequently Asked Questions

How do agentic AI systems change organisational structure?

Agentic AI systems do not automate tasks within existing organisational structures - they delete the need for organisations to be structured the way they currently are. When AI agent harnesses can go directly from insight to code in a single loop, the coordination layer that existed to manage human-to-human handoffs disappears. Not because the handoffs are automated, but because the handoffs no longer happen. The roles that existed to manage those handoffs - project managers writing PRDs, engine

What is the verification flywheel in agentic organisations?

The verification flywheel is a compounding dynamic that emerges when organisations shift their execution layer from human teams to agent harnesses. As coordination roles are removed, the remaining work becomes more verifiable by agents. As remaining work becomes more verifiable, agents can do more of it. As agents do more, less coordination is needed. Each turn of the flywheel accelerates the next. This flywheel pushes organisations relentlessly toward a structure where humans manage teams of ag

What human work survives in agentic organisations?

The work that survives the coordination tax elimination is the thin layer of genuine judgment under uncertainty: product vision (not the PRD, but the upstream conviction about what the product is and who it is for), brand as deep thought work (not the guidelines document, but what the company means), genuine care in customer relationships, engineering architecture as systems thinking, and designing agentic systems themselves. The typical product leader spends at best 5–10% of their week on produ

How do agentic AI systems change organisational structure?

Agentic AI systems do not automate tasks within existing organisational structures - they delete the need for organisations to be structured the way they currently are. When AI agent harnesses can go directly from insight to code in a single loop, the coordination layer that existed to manage human-to-human handoffs disappears. Not because the handoffs are automated, but because the handoffs no longer happen. The roles that existed to manage those handoffs - project managers writing PRDs, engine

What is the verification flywheel in agentic organisations?

The verification flywheel is a compounding dynamic that emerges when organisations shift their execution layer from human teams to agent harnesses. As coordination roles are removed, the remaining work becomes more verifiable by agents. As remaining work becomes more verifiable, agents can do more of it. As agents do more, less coordination is needed. Each turn of the flywheel accelerates the next. This flywheel pushes organisations relentlessly toward a structure where humans manage teams of ag

Key Takeaways

Now count the hours doing the thing you were actually hired to do. Writing the code. Designing the interface. Closing the deal. Building the strategy. Creating something that did not exist before you sat down. If your ratio resembles the research - and it does, because the research describes a structural condition, not a personal failing - you spend roughly sixty per cent of your time on the first two categories and forty per cent on the third. On a good week. That ratio is not a management problem. It is not a tooling problem. It is not a culture problem. It is the Every organisation pays a tax that appears on no balance sheet. The AXD Institute calls it the The coordination tax is not a symptom of bad management. It is a design constraint imposed by the material properties of the execution layer. When the execution layer is human, every participant carries a private model of the world inside their head - partial, decaying, shaped by their role and their recent conversations. No two models are identical. The entire apparatus of organisational coordination exists to align these models closely enough that collective action becomes possible. Meetings exist because humans cannot merge mental models asynchronously. PRDs exist because the person with the insight is rarely the person with the implementation skill. Sprint planning exists because humans cannot dynamically reallocate effort without explicit negotiation. Status updates exist because the state of work, when performed by humans, is opaque to everyone except the person performing it. Strip away the management jargon and what remains is a simple truth: The coordination tax is not a bug in organisational design. It is the price of human collaboration at scale. And it is about to be repriced. Consider what happens when a new engineer joins a team. For weeks, they produce almost nothing. Not because they are incompetent, but because they are absorbing context. Every decision the team made in the past year lives in s

References and Citations

Gartner: Machine Customers as Strategic Technology Trend Stanford HAI: Human-Centered AI Research NIST AI Risk Management Framework About the AXD Institute Contact Us Email the AXD Institute Tony Wood on LinkedIn Tony Wood on X (Twitter)