SYNTHESIS NOTE
Topics›AI at Work›this note

Does agentic AI succeed through process redesign or workflow layering?

Explores whether organizations deploying agents should redesign end-to-end operations or integrate agents into existing workflows. Matters because the choice affects ROI, architecture investment, and governance requirements.

Synthesis note · 2026-10-19 · sourced from AI at Work

Deloitte's Tech Trends 2026 chapter argues that "many agentic AI implementations are failing" because organizations are "layering agents onto old workflows" instead of redesigning operations around them. "True value comes from redesigning operations, not just layering agents onto old workflows," which means "building agent-compatible architectures, implementing robust orchestration frameworks, and developing new management approaches for digital workers." The chapter names three "fundamental infrastructure obstacles": data architectures built around ETL and warehouses that are not positioned for agents that "need to understand business context and make decisions"; governance and control frameworks, since "traditional IT governance models don't account for AI systems that make independent decisions and take actions"; and processes still "designed around human staff" rather than entities that "don't need breaks or weekends" and can "complete a high volume of tasks continually." Deloitte's own 2025 survey found "nearly half of organizations cited searchability of data (48%) and reusability of data (47%) as challenges to their AI automation strategy."

The chapter's reasoning is that inserting an agent into an existing process captures only incremental value, because the process itself was built for human execution. The companies it profiles illustrate the alternative: HPE selected "an end-to-end process where we could truly transform rather than just solve for a single pain point," now running "a dozen agentic proofs of concept" across sales, services, supply chain and engineering, gated by a rule that "we require material ROI signed off by the finance partner and the head of that business unit" — discipline that "kept experiments as experiments." Toyota is extending an agentic tool from visibility into vehicle estimated-time-of-arrival toward resolving supply issues and drafting emails, replacing a process that "used to involve 50 to 100 mainframe screens."

Deloitte's companion survey work found that Why are companies deploying agents faster than governance matures?; this chapter supplies a mechanism behind that gap, pointing to specific data-architecture and governance obstacles rather than treating "immature governance" as a single undifferentiated problem. It also sits in tension with Why do production AI agents stay deliberately simple?, where practitioners keep deployed agents narrow and off-the-shelf rather than redesigning processes end to end — Deloitte's case examples suggest a more ambitious trajectory is available, but only once ROI discipline and architecture investment are in place first.

The excerpt does not measure how many organizations actually attempt end-to-end redesign versus layering, nor does it quantify any success-rate difference between the two approaches; HPE and Toyota are illustrative cases rather than a representative sample, and the 48%/47% figures are self-reported survey challenges, not independently verified architecture audits. The claim that process redesign is the dividing line between agentic AI success and failure remains Deloitte's own diagnosis rather than a tested causal finding.

Inquiring lines that read this note 32

This note is a source for these research framings, grouped by the broader line of inquiry each explores. Scan the bold lines of inquiry; follow any specific question forward.

What organizational practices enable successful AI tool adoption? When does governance become the bottleneck for agentic AI? How should control and autonomy be allocated in human-AI collaboration? Can AI agents learn to improve performance from experience? Can individually safe agents collectively violate system-level constraints? When do multi-agent systems outperform single agents? Does generative AI replace coordination with individual productivity? Can AI systems autonomously pursue unstated objectives or circumvent design constraints? How should organizational structure guide multi-agent system design? How should conversational agents balance proactive goal-pursuit with user autonomy? Can verification capability keep pace with AI generation speed?

Related concepts in this collection 6

This note in its neighbourhood — explore the map, then jump to a related concept in the list below.

Concept map
12 direct connections · 76 in 2-hop network ·medium cluster Open in graph ↗

Click a node to walk · click center to open · click Open in graph to see this note in the full knowledge graph

your link semantically near linked from elsewhere

Related papers in this collection 8

Papers most semantically related to this note, ranked by cosine similarity in the embedding space.

Original note title

Deloitte argues agentic AI succeeds through redesigning end-to-end processes rather than layering agents onto existing workflows