What if the most disruptive change to enterprise software is not another application, but needing fewer humans to operate the applications we already own?
For decades, we digitized work, integrated systems and moved applications to the cloud. Now we are entering a different era: software is beginning to participate in the work itself.
This changes more than productivity. It changes architecture, economics, security, governance, and ultimately the enterprise operating model.
For most of my career, enterprise application strategy began with these four familiar questions:
- What capability does the business need?
- Should we build, buy or integrate it?
- How does it fit the architecture?
- Can we secure, operate, scale and afford it?
Those questions remain important. But they are no longer enough.
Enterprise applications have historically been places where people perform work. Employees navigate screens, enter information, reconcile exceptions, move between systems and trigger workflows.
The relationship has been remarkably consistent: The application provides capability. The human orchestrates the work.
AI and agentic AI begin to change that relationship.
The strategic question is therefore no longer simply, “What functionality should the application provide?” It is becoming: “Who or what should perform the work?”
We are moving from applications people operate toward outcomes people increasingly supervise.
Gartner has predicted that by the end of 2026, 40% of enterprise applications will feature task-specific AI agents, up from less than 5% in 2025, and anticipates agent ecosystems spanning applications and business functions.
I call this discipline required to manage that transition Enterprise Work Architecture (EWA): The deliberate design of how an enterprise outcome moves across human judgment, machine intelligence, applications, data and authority from intent through execution and evidence.
EWA is not another application architecture, process map or AI governance framework. It starts with the work itself.
The problem is the work between applications
Traditional architecture organizes capabilities around discrete systems: ERP, CRM, HCM, ITSM and procurement. Business outcomes rarely respect those boundaries.
Today, humans often bridge those systems, searching, reconciling, interpreting and escalating. AI Agents can now compress those seams by gathering context, interpreting intent and coordinating authorized actions. The opportunity therefore is not simply AI inside applications; it is redesigning how work travels across them.
I learned through my experience that across complex transformations, some of the greatest productivity constraints lived between systems, teams, approvals, data and exceptions.
Modernizing the platform does not necessarily modernize the work. Put an agent over a broken 12-step process, and you may simply automate the friction.
Automation without work redesign can turn process debt into machine-speed process debt.
EWA: A CIO methodology
I would make EWA discipline operational through six connected steps:
Outcome → Work → Authority → Execution → Evidence → Economics
- Outcome: What measurable business result are we trying to produce?
- Work: Which activities are necessary, which should disappear, and which require human judgment?
- Authority: What may a person, application or agent recommend, prepare, approve or execute?
- Execution: Which systems, APIs, data and workflows must participate?
- Evidence: Can consequential actions be observed, reconstructed, challenged and recovered?
- Economics: Did redesigning the work improve time, cost, quality, risk or experience?
The sequence matters here because many AI initiatives begin in reverse: choose a model, deploy a copilot, connect applications and then search for value.
EWA begins with the outcome and designs backward.
Before and after EWA: A customer billing dispute
Consider a customer whose invoice does not match delivery.
Today, an employee moves across CRM, ERP, fulfillment and contracts, often involving finance or operations before a credit can be approved. One outcome becomes a journey across systems, teams and controls.
EWA discipline redesigns this process:
- Step 1: Outcome. Resolve valid disputes quickly, accurately and within financial controls.
- Step 2: Work. Machines gather and reconcile evidence; humans handle ambiguity, exceptions and consequential judgment.
- Step 3: Authority. Agents recommend or execute within defined thresholds; exceptions escalate.
- Step 4: Execution. Actions flow through governed APIs into authoritative systems.
- Step 5: Evidence. Data, decisions, actions, authority and human intervention remain traceable.
- Step 6: Economics. Measure resolution time, human touches, exceptions, rework, cost and customer impact.
That is the difference between automating a task and rearchitecting the work. And that is the EWA discipline.
The innovation is not an agent writing a faster email. It is redesigning end-to-end work while preserving the integrity of the systems underneath it.
Four disciplines make EWA scalable
Turning EWA into an enterprise capability requires four disciplines.
1. Decompose work before deploying agents
Map intent to outcome. Identify judgment, deterministic activity, waiting, handoffs, exceptions and unnecessary steps. Then decide whether AI should retrieve, interpret, recommend, prepare, execute or escalate.
Remember: Do not automate what you have not first challenged.
2. Separate engagement from systems of record
Employees should increasingly be able to express an outcome: resolve this dispute, investigate this variance, restore this service without manually navigating every underlying application.
That does not diminish ERP, CRM, HCM, SCM or ITSM. It makes their data integrity, APIs, transactional controls and resilience more important.
Systems of record remain authoritative; intelligent orchestration increasingly becomes the engagement layer above them. Gartner similarly describes a progression toward agents operating across applications and business functions.
3. Treat agents as governed enterprise participants and not software features
Once an agent can cross application boundaries and act, connectivity is insufficient. It requires identity, delegated permissions, purpose, data boundaries, transaction limits, segregation of duties, observability, escalation and lifecycle controls.
Retrieving an account balance is not changing a customer record. Preparing a purchase order is not releasing it. Diagnosing an incident is not changing production.
Remember: Capability cannot silently become authority.
The NIST AI Risk Management Framework organizes AI risk management around Govern, Map, Measure and Manage. For CIOs, the practical implication is that as machine agency increases, controls must increasingly operate at runtime, not only at project approval.
4. Measure work redesigned — not AI deployed
Counting agents, prompts, licenses or automated tasks tells a board little about whether enterprise economics improved. Measure time-to-outcome, human touches, exception rates, rework, cost per governed outcome, control overhead and value created.
Gartner has estimated that $234 billion in enterprise application software spending is at risk from agentic AI as organizations reconsider how software capabilities are consumed and work is executed.
The goal is not to make every task faster, but to determine which should disappear, which should be redesigned, which machines can safely perform and which still deserve human judgment.
Applications may become less visible — and more important
This creates a paradox.
Enterprise applications may become less visible to users while becoming more important operationally. Meaning, instead of opening five applications to achieve one outcome, an employee may interact with an intelligent workspace orchestrating those systems underneath. ERP still protects financial integrity. CRM maintains customer context. HCM protects workforce records. SCM coordinates fulfillment. ITSM governs services.
What changes here is the human relationship with them.
That affects application portfolios, integration architecture, licensing economics, cyber exposure, resilience and technical debt. The modernization question becomes not simply, “Which applications should we replace?” but “Which application interactions should humans still have to perform?”
The same issue matters during M&A, where enterprises can inherit duplicate ERP, CRM, HR, identity, data and workflow estates. Agents may provide orchestration while rationalization proceeds, but can also amplify inconsistent permissions, fragmented data and unresolved control ownership.
Deloitte’s Generative AI in M&A research examines generative AI across the deal lifecycle alongside considerations including integration, security, trust and human involvement.
The CIO’s mandate is becoming the architecture of work
This cannot belong to IT alone because work does not belong to IT.
Business owns outcomes. Operations understands process reality. Finance measures enterprise economics. Security establishes trust boundaries. Risk and Legal define obligations. HR understands workforce consequences. Audit tests controls. Enterprise Architecture connects them to systems, data and execution.
The CIO’s opportunity is to make those disciplines coherent.
Start with a work inventory, and not another AI inventory.
Find where employees bridge systems, exceptions concentrate, approvals create latency, repetitive activity consumes capacity and application boundaries become organizational boundaries. Then apply EWA discipline: Outcome. Work. Authority. Execution. Evidence. Economics.”
That creates a repeatable methodology for deciding not merely where AI can be deployed, but where enterprise work should be redesigned.
Boards can then ask a more consequential question: “Are we funding AI features or redesigning how the enterprise operates?”
The first can produce a larger technology portfolio.
The second can change productivity, operating leverage, experience, risk and ultimately enterprise value.
Do not begin with how many agents you can deploy. Begin with the work your enterprise should no longer perform the same way.
Redesign the outcome. Remove unnecessary work. Define authority. Connect execution. Instrument evidence. Establish the economics. Protect human judgment where consequence demands it. Then scale.
The enterprises that lead this transition will not necessarily have the most autonomous software. They will be those that most deliberately determine where humans create judgment, where machines create leverage and where the combination creates measurable enterprise value.
The next generation of enterprise applications will not simply run the business. They will increasingly participate in running it. The CIO’s responsibility is to redesign the work without surrendering the judgment, trust and accountability on which the enterprise depends.