Reimagining IT’s Mandate in an Age of Intelligent Systems
The most disruptive change to enterprise software may not be new applications, but rather how we need fewer humans to operate what we already own. After decades of digitization and cloud adoption, we’re entering a new era where software actively participates in the work itself.
From Human-Operated Apps to Intelligent Workflows
Traditionally, enterprise application strategy focused on:
- What capabilities are needed?
- Build, buy, or integrate?
- Architectural fit?
- Security, operations, and cost?
These questions remain important, but they’re no longer sufficient. Applications have evolved from places where people perform work to platforms capable of delivering outcomes with minimal human intervention.
With AI and agentic AI rapidly advancing (Gartner predicts 40% of enterprise apps will feature task-specific agents by 2026), the strategic question shifts from “What functionality should it provide?” to “Who or what should perform the work?”
Introducing Enterprise Work Architecture (EWA)
I call this emerging discipline Enterprise Work Architecture – 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 isn’t just another framework; it begins with the work itself. Traditional architectures organize capabilities around discrete systems (ERP, CRM), while business outcomes rarely respect those boundaries. AI agents can compress these seams by gathering context, interpreting intent, and coordinating actions – redesigning how work travels across applications.
The Six Pillars of EWA:
- Outcome: What measurable result are we trying to achieve?
- Work: Which activities are necessary, which should be eliminated, and where human judgment is required?
- Authority: Who or what can recommend, prepare, approve, or execute at each step?
- Execution: Which systems, APIs, data, and workflows must participate?
- Evidence: Can consequential actions be observed, reconstructed, challenged, and recovered?
- Economics: How does redesigning the work impact time, cost, quality, risk, and experience?
The sequence matters – EWA starts with the desired outcome and designs backward, rather than selecting a technology and searching for value.
Real-World Example: Customer Billing Disputes
Today, resolving a mismatched invoice often requires employees to navigate multiple systems (CRM, ERP) across departments. With EWA:
- Agents automatically gather and reconcile data
- Humans handle exceptions and complex cases
- Authority is clearly defined for recommendations and approvals
- Actions flow through governed APIs into authoritative systems
- Complete traceability of decisions and interventions
- Measurable improvements in resolution time, cost, and customer satisfaction
The innovation isn’t just AI inside applications; it’s redesigning end-to-end work while maintaining appropriate controls.