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.
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?- How does organizational modularity affect the value of AI predictions?
- Why do enterprise AI deployment plans outpace governance readiness across sectors?
- Why do company AI adoption rates outpace governance frameworks?
- How do organizations redesign workflows to capture AI economic value?
- How does workflow redesign create more value than improving agent sophistication?
- Why model AI integration as organizational socialization rather than tool installation?
- How do management practices shape whether AI adoption pays off?
- Why do older firms struggle more than startups with AI transitions?
- Do organizational changes need to precede or follow AI adoption?
- How do power structures and corporate agendas shape AI deployment outcomes?
- Why do organizations fail to integrate AI into existing work cultures?
- What accountability structures should govern AI agent developers and deployers?
- How mature are governance structures compared to agentic AI deployment timelines?
- How do traditional IT governance models fail with autonomous AI systems?
- What governance discipline did HPE apply to keep agentic experiments controlled?
- How do organizational policies shape human agency around agentic AI?
- What operational tensions emerge from agentic AI's dual nature?
- Should automation design match a workflow's standardization level rather than defaulting to agents?
- How much do simpler automation tools outperform agents in standardized workflows?
- How can governance structures catch up to agentic AI deployment timelines?
- What governance decisions depend on treating agenticness as dimensional rather than categorical?
- Does offloading AI maintenance to external vendors reduce or increase organizational accountability?
Related concepts in this collection 6
This note in its neighbourhood — explore the map, then jump to a related concept in the list below.
Click a node to walk · click center to open · click Open in graph to see this note in the full knowledge graph
-
Why are companies deploying agents faster than governance matures?
Enterprise leaders are racing to deploy agentic AI within two years, but only 21% report mature governance models. This gap between deployment intent and oversight capability raises questions about how companies are managing the risks of rapid scaling.
same Deloitte survey program; this chapter names the specific infrastructure obstacles behind that governance gap
-
Why do production AI agents stay deliberately simple?
Production AI agents operate far simpler than research suggests—most execute under 10 steps and avoid third-party frameworks. What explains this gap between research ambition and deployment reality?
contrasts: practitioners constrain scope rather than redesign end to end, against Deloitte's more ambitious redesign argument
-
How should organizations supervise autonomous AI agents?
Explores what structural and technical mechanisms organizations need to maintain meaningful human oversight as AI agents gain decision-making autonomy, and whether designed handoff points and audit trails can prevent oversight degradation.
sibling claim from the same chapter, on how redesigned processes are then staffed and governed
-
Can AI agents truly operate above the loop at enterprise scale?
McKinsey proposes a radical organizational shift where AI agents handle end-to-end workflows with humans positioned for strategic oversight. This exploration examines whether that model reflects current practice or remains aspirational.
Extends: McKinsey's AI-first workflow model, replacing silos and repositioning humans above the loop, exemplifies Deloitte's call for process redesign
-
Does agent quality matter more than workflow redesign?
When organizations deploy agentic AI, should they prioritize perfecting the agent itself, or does the real value come from redesigning how workflows integrate people, processes, and technology? This question matters because it shapes where teams invest effort and resources.
Evidence for: McKinsey's 50+ agentic AI builds confirm Deloitte's claim that value comes from workflow redesign, not agent quality
-
When should you actually deploy an AI agent instead of simpler automation?
This explores how to match automation type to workflow characteristics. Understanding when agents add value versus when simpler tools suffice helps teams avoid over-engineering solutions and wasting resources on unnecessary complexity.
Qualifies: McKinsey ties automation choice to task variance, so agents suit only high-variance work, not every redesigned process
Related papers in this collection 8
Papers most semantically related to this note, ranked by cosine similarity in the embedding space.
- Tech Trends 2026 (chapter: The agentic reality check: Preparing for a silicon-based workforce)
- One year of agentic AI: Six lessons from the people doing the work
- A Practical Guide for Designing, Developing, and Deploying Production-Grade Agentic AI Workflows
- AI Agents Need Memory Control Over More Context
- Unraveling Human-AI Teaming: A Review and Outlook
- Explaining AI Agents Through Execution Traces
- Institutional AI: Governing LLM Collusion in Multi-Agent Cournot Markets via Public Governance Graphs
- The Emerging Agentic Enterprise: How Leaders Must Navigate a New Age of AI
Original note title
Deloitte argues agentic AI succeeds through redesigning end-to-end processes rather than layering agents onto existing workflows