How agentic AI changes the unit of work in enterprise teams

Last updated: July 2026

The unit of work is changing. For decades, teams organised around tasks a person executes; agentic AI reorganises them around outcomes an agent owns and a person reviews. Already, 46% of business leaders say their organisation uses agents to fully automate workstreams. This post covers what that shift means for roles, workflow design, and the operating model behind the agentic AI workflow services we define in our pillar guide.

Key takeaways

• 46% of leaders say their organisation already uses AI agents to fully automate entire workstreams, and 82% expect digital labour to expand workforce capacity within 12 to 18 months (Microsoft Work Trend Index, 2025).
• Usage data leans collaborative: Anthropic's Economic Index measured 57% of AI interactions as augmentation and 43% as automation. The unit of work is shared, not surrendered.
• Gartner predicts 15% of day-to-day work decisions will be made autonomously by agentic AI in 2028, up from 0% in 2024. Review capacity, not build capacity, becomes the team's bottleneck.
• Gartner also expects over 40% of agentic AI projects to be cancelled by the end of 2027. The survivors redesign the workflow around the agent instead of bolting an agent onto the old one.
• From our own delivery work: a Semantic Kernel agent that converts plain-language questions into SQL against Snowflake replaced a reporting queue measured in days with answers in seconds, and moved the analyst's job from writing queries to validating them.

What is the unit of work, and why is it changing?

The unit of work is the smallest chunk of value a team plans, assigns, and tracks. For fifty years that chunk was a task performed by a person: write the query, reconcile the ledger, draft the summary. An agent changes the shape of the chunk. Software that plans, calls tools, observes results, and retries can own an outcome, with a person setting the goal and judging the output.

The shift is collaborative rather than wholesale. Anthropic's Economic Index, built from millions of anonymised Claude conversations, measured 57% of usage as augmentation, where the model checks, iterates, and teaches alongside a person, against 43% as direct task automation. Teams are not handing work over. They are splitting each unit of work into a part the agent executes and a part a human owns.

What changes for team roles when agents own tasks?

Three responsibilities appear on every team that delegates to agents: setting scope, reviewing output, and owning exceptions. None of them sat on an org chart in 2023, and all three are becoming ordinary. In Microsoft's 2025 Work Trend Index, a survey of 31,000 workers across 31 countries, 82% of leaders said they expect to use digital labour to expand workforce capacity within 12 to 18 months, and leaders expect their teams to be training agents (41%) and managing them (36%) within five years. Microsoft's name for the emerging role is the "agent boss."

The practical consequence: job descriptions shift from throughput to judgment. A senior analyst who once produced twenty reports a week now defines the templates, sets the guardrails, and reviews the drafts an agent produced overnight. The skill being paid for is no longer execution speed. It is knowing what correct looks like, and catching the 1-in-20 output that isn't.

How does workflow design change?

Delegating to an agent is not assigning a ticket to a junior engineer. Three design changes separate workflows that hold up in production from demos that stall.

Every delegation needs a contract

An agent needs the goal, the boundaries, and the escalation rule written down: what it may read, what it may change, and when it must stop and ask. Across the agents we shipped in 2025-26, the workflows that failed internal review were rarely failing on model quality. They failed because nobody had defined who is accountable when the agent is wrong. Write the contract before the prompt.

Exceptions become the design centre

Human workflows hide their exceptions inside experienced heads; the veteran in accounts knows which supplier's invoices always arrive malformed. An agent forces those cases into the open. The real design work is deciding which inputs route to a human queue and making that queue somebody's job. In the production agents we run, a low-single-digit percentage of items routing to human review is a healthy pattern. Zero usually means the thresholds are too loose to catch anything.

Review becomes a first-class activity

Gartner predicts 15% of day-to-day work decisions will be made autonomously through agentic AI in 2028, up from 0% in 2024. Read the other side of that number: 85% of decisions still involve a person, and a growing share of them are reviews of agent output. Teams that do not budget review time convert it into unplanned rework. Plan review capacity the way you plan compute.

What does the new unit of work look like in production?

One example from our own delivery work. For a European enterprise customer, we used Microsoft's Semantic Kernel to build an agent that takes a plain-language question, interprets the intent, writes the corresponding SQL, executes it against the company's Snowflake warehouse, and returns the answer with the underlying data attached. It qualifies as an agent because it plans and selects its own tools, even though it mostly interacts with itself.

The engineering is deliberately unremarkable: the language model handles language, SQL handles retrieval, and the warehouse's existing permissions handle access. The operating-model change is the point. A reporting request that previously queued for days behind a data team now returns in seconds, and the data team's unit of work moved up a level, from writing queries to curating the semantic layer and reviewing the queries the agent writes. We reused the same framework for a second customer to generate documents and working HTML prototypes on demand. The pattern transfers because the delegation contract, not the use case, is the reusable part.

What stays with humans?

Accountability, ambiguous goals, and anything that crosses an organisational boundary. An agent can reconcile the ledger; it cannot decide that the reconciliation policy is wrong. It can draft the customer response; it should not decide to waive the fee. The dividing line we apply in practice: agents own outcomes whose success criteria can be written down and tested, people own outcomes where the criteria themselves are in dispute. That line moves every year as evaluation tooling improves, but it moves by deliberate decision, not by drift. Letting it drift is how organisations end up in the incident reviews.

How do you adopt the new unit of work without joining the 40%?

Start with one workflow, redesign it around the agent, and staff the review loop before scaling to a second. Gartner expects over 40% of agentic AI projects to be cancelled by the end of 2027 on escalating costs, unclear business value, or inadequate risk controls. McKinsey's State of AI research points at the same root cause from the other direction: workflow redesign correlates with EBIT impact more than any other organisational factor, yet only 21% of organisations using gen AI have redesigned any workflows at all. The pattern that fails is adding an agent to an unchanged process and expecting the process to improve.

This operating-model work is what our AI and agents practice is built around, and it pairs with the team-shape question we examine in building autonomous teams with less process and more impact: smaller teams, clearer ownership, fewer handoffs for agents to inherit.

The same Gartner forecast says 33% of enterprise software applications will include agentic AI by 2028, up from less than 1% in 2024. When that lands, the unit of work stops being a metaphor and becomes a line in the resource plan: teams will estimate, price, and staff around outcomes delegated to agents. The teams practising that arithmetic on one workflow today are the ones who will find 2028 unremarkable.