Perspective 3
AI cannot be scaled through pilots, tools, or isolated centers of excellence. It requires a designed operating model: ownership, decision rights, governance, incentives, funding, and production control.
Executive Summary
Enterprise architecture has been protecting the wrong asset for thirty years.
Workflow systems were built to coordinate people around processes — predictable sequences, defined steps, governance structures wrapped around the procedure. This made sense when processes were stable, people were the intelligence layer, and automation meant encoding what humans already did.
AI does not operate on processes. It operates on data.
When AI reasons about an organization, it does not reason about the workflow. It reasons about the transactions, the decisions, the customer history, the operational state — the permanent record of what actually happened. The process is how the organization coordinated people. The data is what the organization actually is.
Companies still architected around process platforms are asking AI to optimize something that is already wrong. The ERP subscription fee is not protecting your competitive position. The data it generated is.
This has concrete structural consequences. Organizations that design architecture around data permanence — rather than process standardization — will have AI leverage that process-centric organizations cannot quickly replicate. The process platform can be rebuilt in eighteen months. The data model, the institutional knowledge encoded in the data, the decision history that trains the models: these compound over time and cannot be purchased.
The organizations that understand this are making different decisions today: about where intelligence lives, about what infrastructure is worth protecting, about which vendor dependencies are acceptable and which create structural lock-in on the wrong asset.
This paper sets out what data-driven architecture actually requires — not as a technology specification, but as a structural decision framework for leaders who are deciding today what their organizations will be capable of in three years.
Design Components
Name who owns the business outcome, data domain, model behavior, workflow impact, and operating risk.
Define who approves use cases, funding, deployment, escalation, changes, exceptions, and shutdown decisions.
Design different control paths by risk tier so governance enables learning without losing accountability.
Align performance measures with adoption, value capture, risk control, and cross-functional execution.
Move beyond pilot budgets. Fund platforms, operating redesign, data readiness, governance, and production support.
Specify monitoring, audit, escalation, model review, human intervention, and continuous improvement mechanisms.
Design Principles
The model is only one component. Value appears when the workflow changes and the organization can govern that change.
Pilots need speed. Production needs ownership, monitoring, escalation, resilience, and accountability.
Low-risk automation should move quickly. High-risk decisions require stronger review, auditability, and human control.
AI at scale requires shared infrastructure, data, policy, governance, and delivery mechanisms, not only use-case teams.
If no one owns the outcome, exception path, and failure mode, the capability is not ready for production.
Governance should shape how AI operates. It should not appear only at the end as a blocker.
The Operating Model Stack
AI execution fails when these layers are designed separately. The operating model has to connect them into one system.
Capital allocation
Governance model
Decision rights
Data ownership
Workflow design
Technology architecture
Risk controls
Performance measures
Relationship to Other Perspectives
The Operating Model Gap explains why organizations struggle to absorb technology change.
Why AI Transformation Fails shows what happens when these design choices are not made.
Frequently Asked Questions
Operating model design for AI defines how ownership, decision rights, governance, incentives, funding, workflows, and production controls work together so AI can be used safely and repeatedly at scale.
AI changes decision speed, data dependency, workflow design, risk exposure, and accountability. Traditional operating models often lack the governance and production controls needed for AI-enabled execution.
Leaders should define ownership, decision rights, risk tiers, funding model, production monitoring, escalation paths, and value-capture metrics before scaling AI workflows.
AI pilots often fail to scale because they prove technical feasibility without designing the operating model required for production ownership, governance, monitoring, funding, and accountability.
Structural Position
AI-ready operating models are designed before scale, not after failure. The work is not to add AI to the current system. The work is to redesign the system so AI can operate safely, repeatedly, and economically.
Papers