Agentic AI and the New Operating Model for Work

The strategic promise of agentic AI is not that work gets faster. It is that organisations can start to redesign how work moves and what an agentic AI operating model actually looks like in practice.

For the first time, many businesses can hand bounded, knowledge-heavy tasks to enterprise AI agents that do more than answer questions. They can retrieve context, make decisions inside guardrails, trigger actions and hand work on. That changes more than productivity. It changes the shape of the operating model.

That is the shift running through the WSAI AI Workforce Playbook. Across the 2025 sessions and workshops that informed it, the same point kept surfacing: the organisations pulling ahead are not the ones with the most AI tools. They are the ones connecting agents to real processes, trusted data and clear human oversight so work can actually move inside the business.

This is where the conversation needs to get sharper. Most discussion about agentic AI still focuses on capability: what the agent can do, how many steps it can take, how autonomous it looks in a demo. The more important question for senior leaders is different: what happens to the organisation when parts of execution no longer sit neatly inside a human role?

The operating model shift behind agentic AI

The Playbook makes a useful distinction: assistants help people with work, while an AI workforce helps do the work inside systems, process and governance. That is not a semantic difference. It is what separates incremental productivity from operating model change.

Building on this, WSAI 2026 sessions such as “Orchestrating Agentic AI: Control, scale, and enterprise value” and “Your Processes Were Never Built for Agentic AI” frame the issue well. When agents begin to plan, retrieve, validate, route and act across workflows, the question is no longer where AI fits into the current process. The question becomes whether the current process was ever designed for a world where execution is shared between people and software.

That is why this is a leadership issue before it is a tooling issue. Once agents take on parts of execution, managers are no longer only directing people. They are setting boundaries, escalation paths, decision rights and quality controls for human-agent systems.

The management layer is what changes next

The interesting shift is not simply that agents can do more work. It is that they can absorb pieces of the coordination layer that sit between strategy and execution. In many organisations, a surprising amount of management time is still spent chasing updates, routing requests, reconciling inputs, checking exceptions and moving decisions from one queue to the next. Agentic AI can take on parts of that layer, but only if leaders redesign roles around judgment, intervention and accountability instead of assuming the old management model still holds.

This is why the Microsoft idea of the “Frontier Firm” matters here. Microsoft argues that a new kind of organisation is emerging around hybrid teams of humans and agents, and that leaders will increasingly need to manage intelligence on demand rather than just fixed capacity. The practical implication is not that every manager becomes an “agent boss” overnight. It is that leadership teams need to decide where autonomy is useful, where it is dangerous and how responsibility holds when work is completed through a chain of humans, systems and agents.

That is a more interesting strategic challenge than standard automation. Traditional automation removed steps from stable processes. Agentic AI starts to reshape who or what owns the middle of the workflow.

Where agents genuinely add value

Agents work best when tasks are repetitive but not rigid, when context changes, when several systems or documents must be consulted, and when judgment is needed inside clear limits.

That is why the experts from WSAI 2025 keep pointing to customer support, travel, audit, procurement, HR screening, logistics and internal research. The practical lesson for senior leaders is simple: start where the path varies, the cost of delay is real and the result can be measured. If the process is already fixed, conventional automation may still be the better answer. If the process is broken, an agent will not rescue it. It will expose the problem faster.

What leaders should redesign first

The first redesign is not the org chart. It is the logic of work in an agentic AI operating model. Before any large-scale rollout of enterprise AI agents, leadership teams need to get much clearer on five things.

Where judgment genuinely adds value and must stay human.
Where bounded execution can move safely to agents.
Where escalation should happen when confidence drops or context changes.
What data, systems and permissions agents need to do useful work.
How output quality, trust and recovery from failure will be measured in production.

The Playbook’s 90-day plan is especially useful here because it turns those questions into a real-world sequence. The first 30 days focus on identifying high-friction workflows and defining constraints early; the next 30 move into workflow design, permissions, evaluation and observability; the final 30 put the first use case into a live but controlled environment so teams can measure quality, trust and failure before scaling.

This year’s World Summit AI delves into “Inside the agent harness,” “From Prototype to Production: Scaling AI Systems That Deliver,” and “Engineering responsible AI systems at scale”, reinforcing the same message from different angles: governance, observability, evaluation and workflow integration are not add-ons. They are part of the operating model.

What usually goes wrong

Most agentic AI programmes do not stall because leaders lack ambition. They stall because the business is still organised around tools, not outcomes. Many organisations are still coordinated around tools, not outcomes. Functions buy point solutions and teams prototype in isolation, but few can explain in plain English how the workflow actually runs, where the agent fits, what success looks like, or who is responsible when it fails.

Across the WSAI 2025 discussions, three paths kept appearing: fragmentation, experimentation and AI-first redesign. Fragmentation creates disconnected workflows and inconsistent controls. Experimentation produces clever pilots that never survive contact with production. The stronger path starts with work, process, trusted data and guardrails, then scales only where early value is real.

This is also why agentic AI belongs on the board agenda. It sits across operating model, governance, workforce design and risk. It is not just a technology programme. It is a decision about how the enterprise will run.

What readiness looks like

The key question is not whether the organisation has deployed agents. It is whether the organisation is ready to run work through them. If accountability disappears once an agent acts, if managers still reward local tool ownership over system performance, or if nobody can explain where human judgment re-enters the flow, the operating model has not caught up.

EY offers a useful example of what readiness looks like at scale. The firm moved beyond scattered GenAI deployments by unifying its work into a single agentic AI operating system, connecting intelligence, orchestration, data and governance across service lines rather than leaving agents trapped in isolated tools.

EY had already deployed AI to more than 300,000 professionals, but found that scaling further required more than another assistant or model. It needed one enterprise system capable of supporting multistep workflows, permissioned data access, lifecycle management, auditability and responsible AI under growing regulatory pressure.

What makes that example useful is not the scale alone, but the design choices behind it. EY built a unified intelligence layer, an orchestration and workflow layer, and a governed data and trust foundation so agents could work across Microsoft 365, EY Fabric and other enterprise systems while remaining observable and controlled. In other words, it treated enterprise AI agents as part of an operating model, not a collection of experiments. That is exactly the distinction most organisations still miss.

The workforce piece is equally important. EY says more than 80% of its professionals use EY.ai EYQ and more than 80% have completed foundational AI training, while agentic innovation accelerated to more than 50,000 agents in nine months. The point is not simply that EY built a lot of agents. It is that the firm paired platform design with workforce readiness, governance and controlled deployment, testing systems in managed environments before broadening their role. That is much closer to what real readiness looks like than the usual claims about autonomy.

This is the operating model challenge of the next few years. Agentic AI will be won by companies that redesign work with enough clarity and discipline to make their enterprise AI agents useful, governable and worth trusting, while moving people upward into the parts of the workflow where judgment and creativity still matter most.

What do you think?

If this is something you’re actively navigating, the conversation doesn’t stop here.

Inside the InspiredMinds! Community Hub, you’ll find deeper insights, expert perspectives, and practical discussions from the people building and deploying AI across Europe and beyond.

Explore the Hub, access exclusive content, and stay connected to the conversations shaping what comes next.