Foundational Investment
For example:
-
Data
-
AI platforms
-
Architecture
-
Cybersecurity
-
Infrastructure
-
Governance
-
Skills
-
Monitoring
What an AI Target Operating Model Should Include
The operating model decisions that turn AI from a collection of pilots into an enterprise capability.

Before designing structures, committees or roles, clarify what the organisation wants the model to achieve.
For example:
Faster adoption of valuable AI opportunities
Consistent governance
Better reuse of technology and data
Stronger risk management
Clearer accountability
Reduced duplication
Better investment decisions
Faster movement from pilot to production
More reliable enterprise-scale operation
The operating model should support those outcomes.
It should not become an organisational design exercise detached from the reason AI matters.
Governance is important.
But governance alone does not explain how AI gets delivered.
A complete operating model should answer questions such as:
Who identifies opportunities?
Who owns business outcomes?
Who decides whether AI is appropriate?
Who assesses risk?
Who approves architecture?
Who owns data?
Who builds the solution?
Who operates it?
Who monitors it?
Who funds it?
Who decides when it should be changed or retired?
If those questions remain unclear, governance committees alone will not create scalable adoption.
AI should not become something that technology teams do to the business.
Each meaningful AI use case needs clear business ownership.
That owner should understand:
The problem being solved
The expected outcome
The affected process or capability
The risks
The required organisational change
How value will be measured
Technology may enable the solution.
But accountability for the business outcome should remain with the business.
Without that ownership, AI can become a portfolio of interesting technical activity with weak connection to organisational value.
Enterprise AI introduces responsibilities across several groups.
These may include:
Business leadership
AI specialists
Data
Technology
Enterprise architecture
Cybersecurity
Legal
Risk
Procurement
Finance
Transformation
Operations
The operating model should make clear who is:
Accountable
Responsible
Consulted
Informed
for the major decisions in the AI lifecycle.
Ambiguity creates either delay or uncontrolled activity.
Both make scale harder.
One of the most important design choices is which AI capabilities should sit centrally.
Potential central capabilities may include:
AI strategy
Architecture standards
Common platforms
Model-provider standards
Governance frameworks
Risk controls
Cybersecurity standards
Shared tooling
Reusable components
Specialist expertise
Supplier frameworks
Enterprise monitoring
Centralisation can improve:
Consistency
Reuse
Control
Efficiency
Enterprise learning
But too much centralisation can create bottlenecks.
The goal is not central control for its own sake.
It is to centralise where enterprise consistency creates value.
Business units and functions often need enough freedom to identify and pursue relevant AI opportunities.
Federated responsibilities may include:
Opportunity identification
Business ownership
Domain expertise
Local process change
Adoption
Benefits realisation
Some delivery capability
Federation helps keep AI close to the problems it is intended to solve.
But it should operate within clear enterprise guardrails.
Otherwise the organisation may create:
Duplicate solutions
Conflicting suppliers
Inconsistent architecture
Weak governance
Uncontrolled data use
Repeated investment
For many enterprises, the practical answer will be a hybrid model.
For example:
Central capability
Strategy
Architecture
Standards
Common platforms
Risk frameworks
Security
Reusable technology
Specialist expertise
Federated capability
Business ownership
Opportunity identification
Domain expertise
Adoption
Benefits realisation
Selected delivery activity
This can create a balance between:
Control and speed
Consistency and flexibility
Enterprise reuse and local relevance
The exact balance should reflect the organisation's structure, maturity and risk profile.
An AI operating model should explain how an idea moves from initial opportunity to operational use.
A practical lifecycle may include:
Identify → Assess → Prioritise → Design → Govern → Build → Deploy → Monitor → Improve → Retire
Each stage should have clear ownership and decision criteria.
The first question should be:
What problem are we trying to solve?
Opportunities may emerge from:
Business teams
Strategy
Transformation
Customer insight
Operational teams
Technology
Data teams
AI specialists
The operating model should make it easy for useful ideas to enter the process without creating an uncontrolled backlog of speculative use cases.
Before prioritisation, the organisation should assess whether AI is an appropriate solution.
Questions may include:
What outcome is expected?
Is AI genuinely required?
What data is needed?
Is that data available?
What risks are involved?
What architecture is required?
What suppliers may be involved?
What change will the business need to make?
Is the organisation technically ready?
This prevents enthusiasm from becoming automatic approval.
Not every valuable idea can be funded at once.
AI opportunities should be compared using factors such as:
Strategic relevance
Business value
Feasibility
Risk
Data readiness
Technical readiness
Cost
Dependency
Reusability
Time to value
The purpose is not simply to score use cases.
It is to understand which opportunities should move first and what foundational investment they depend on.
The organisation should define the intended solution within its wider enterprise architecture.
That may require decisions around:
Models
Data
Integration
APIs
Identity
Security
Cloud
Hosting
Monitoring
Human oversight
Reusable services
The design should fit the enterprise rather than becoming an isolated technical implementation.
The organisation should determine the appropriate level of control.
Governance may consider:
Data sensitivity
Business consequence
Model autonomy
Customer impact
Regulatory exposure
Security
Bias
Explainability
Human oversight
Supplier risk
Not every use case should require the same level of governance.
A proportionate model is usually more practical.
Delivery responsibilities should be clear.
The organisation needs to know:
Who builds
Who configures
Who integrates
Who tests
Who approves
Who deploys
Who signs off operational readiness
This may involve:
Internal teams
Central AI capability
Business-unit teams
Partners
Technology suppliers
The operating model should make those interactions explicit.
AI does not stop being a governance concern once it goes live.
Operational monitoring may need to consider:
Performance
Accuracy
Model behaviour
Security
Data changes
Usage
Cost
Business value
User adoption
Risk indicators
Monitoring responsibilities should therefore be designed into the operating model from the start.
AI solutions will change.
Models improve.
Business requirements evolve.
Suppliers change.
Costs move.
Some solutions will become more valuable.
Others should be retired.
The operating model should therefore define how AI services are:
Reviewed
Updated
Revalidated
Replaced
Retired
Enterprise AI needs lifecycle management just like other strategic technology.
A practical governance model should make clear:
What requires approval
Who approves it
What evidence is required
How risk is classified
Which decisions can be delegated
What needs escalation
How exceptions are handled
How deployed AI is reviewed
Governance should support responsible progress.
It should not exist simply to create more committees.
Different AI uses create different levels of consequence.
For example:
An internal assistant summarising non-sensitive information may create relatively low risk.
An AI system affecting:
Employment decisions
Customer eligibility
Financial outcomes
Safety
Critical operations
Sensitive personal data
may require significantly stronger controls.
The operating model should therefore support different governance pathways based on risk and consequence.
This reduces unnecessary friction while maintaining appropriate control.
An AI Target Operating Model should connect directly to architecture.
Relevant decisions may include:
Approved model providers
Model hosting
Cloud
Data access
APIs
Integration
Identity
Access control
Security
Logging
Monitoring
Development environments
Deployment environments
Reusable AI services
Without architectural consistency, every use case can create a new technical pattern.
That increases:
Complexity
Cost
Supplier dependence
Security exposure
Support overhead
The operating model should therefore clarify where teams have architectural freedom and where enterprise standards apply.
AI operating models need a clear relationship with enterprise data governance.
Questions include:
Who owns the data?
Who approves its use?
How is quality assessed?
How is sensitive data classified?
How is access controlled?
How is provenance understood?
How are retention requirements handled?
What data can be used with external services?
Many AI initiatives fail to scale because data decisions remain unclear.
The operating model needs to make those responsibilities explicit.
Cybersecurity should not become a final approval step before deployment.
It should be part of the lifecycle.
Relevant considerations can include:
Identity
Access
Sensitive information
Data leakage
Supplier security
API security
Model access
Monitoring
Logging
Incident response
Prompt handling
External connectivity
Early involvement reduces the likelihood that a technically successful AI solution becomes impossible to deploy.
AI introduces new supplier questions.
The organisation may rely on:
Foundation-model providers
Cloud providers
Specialist AI platforms
SaaS providers
Data providers
Consulting partners
Systems integrators
The operating model should define how suppliers are:
Selected
Assessed
Approved
Contracted
Monitored
Reassessed
Relevant considerations may include:
Security
Data handling
Commercial terms
Intellectual property
Portability
Resilience
Jurisdiction
Exit options
Supplier concentration
Procurement therefore becomes part of the AI operating model rather than a separate downstream process.
AI architecture may create important strategic dependencies.
For example:
AI Service → Model Provider → Cloud Provider → Jurisdiction
or:
Business Capability → AI Platform → Proprietary API → Supplier Dependency
Those relationships may affect:
Strategic control
Resilience
Data handling
Portability
Future choice
Jurisdictional exposure
The operating model should define where sovereignty considerations need to enter AI decision-making.
Enterprise AI requires a combination of specialist and general capability.
Specialist skills may include:
AI engineering
Data science
Machine learning
Architecture
Data engineering
Cybersecurity
Model risk
But wider organisational capability may also be required across:
Business analysis
Product management
Change
Procurement
Legal
Risk
Leadership
Operations
The operating model should clarify:
Which skills should exist internally
Which can be provided by partners
Which should be central
Which should exist in business teams
Where capability needs to be developed
External partners can accelerate AI adoption.
But the organisation should avoid becoming dependent on partners for knowledge it needs to operate AI sustainably.
The operating model should therefore clarify:
What partners will provide
What knowledge must remain internal
How capability transfer will work
Who retains accountability
How supplier dependency will be managed
Partners should strengthen enterprise capability rather than substitute indefinitely for it.
AI funding can become fragmented if every use case requires a separate business case. The operating model should distinguish between:
For example:
Data
AI platforms
Architecture
Cybersecurity
Infrastructure
Governance
Skills
Monitoring
For example:
Individual business solutions
Process automation
Customer-facing applications
Decision-support capability
This distinction matters because foundational investment may support many future opportunities. Without it, the organisation may repeatedly fund pilots while failing to build reusable capability.
AI activity should be measured against the outcome it is intended to create.
Depending on the use case, measures could include:
Revenue
Cost reduction
Productivity
Cycle time
Service quality
Customer experience
Risk reduction
Decision speed
Error reduction
Employee experience
Technical measures also matter.
But a model performing well technically does not necessarily mean the organisation is creating value.
The operating model should clarify who owns benefits and how they will be measured.
Once AI becomes part of normal business operations, someone needs to support it.
Questions include:
Who responds when it fails?
Who investigates poor output?
Who monitors supplier issues?
Who handles user support?
Who manages access?
Who responds to model changes?
Who manages incidents?
Who maintains integration?
Who owns service continuity?
These responsibilities are often invisible during pilots.
They become important at scale.
The operating model should clarify where human involvement is required.
That may include:
Approval
Review
Escalation
Exception handling
Quality assurance
High-consequence decisions
The level of human oversight should reflect the consequence of the AI use.
The objective is not to insert manual approval everywhere.
It is to ensure accountable judgement remains where it matters.
A good operating model makes decision rights explicit.
For example:
Who can:
Approve an AI use case?
Select a model provider?
Authorise sensitive data use?
Approve architecture exceptions?
Accept AI risk?
Commit investment?
Deploy into production?
Stop an AI service?
Without clear decision rights, organisations often create either:
or:
Clarity improves both speed and control.
An organisation can design an excellent operating model that its existing technology environment cannot support.
For example:
A governance process may require strong data lineage.
But the organisation may not have it.
A deployment model may assume reusable APIs.
But integration capability may be weak.
A monitoring model may require enterprise observability.
But the required tooling may not exist.
The operating model should therefore be designed alongside an assessment of technical readiness.
Xirocco's AI Technical Readiness Score, or AiTRS, focuses on areas including:
Data
Cybersecurity
Infrastructure
IT capability
The purpose is to identify where the intended operating model depends on capabilities the organisation does not yet have.
AI touches many existing enterprise functions.
The target model therefore needs to connect with:
Business strategy
Technology strategy
Data governance
Cybersecurity
Enterprise architecture
Procurement
Legal
Risk
Finance
Transformation
Existing delivery models
Creating an entirely separate AI organisation can generate unnecessary duplication.
Where possible, AI should become integrated into the existing enterprise operating environment.
Not every AI responsibility requires a new committee.
Existing mechanisms may already govern:
Technology architecture
Cybersecurity
Data
Investment
Risk
Procurement
Change
The better question is:
Which existing governance mechanisms can absorb AI, and where are genuinely new capabilities required?
This can make the operating model simpler and more sustainable.
An AI Centre of Excellence can be valuable.
But only if its role is clear.
It may provide:
Specialist expertise
Standards
Architecture
Governance support
Reusable components
Coaching
Delivery support
Knowledge sharing
But it should not automatically become the owner of every AI decision.
If all activity has to pass through one central team, the organisation may create a permanent bottleneck.
The role of any central AI function should therefore be defined within the wider operating model.
AI capability will evolve quickly.
The operating model should therefore support learning across the enterprise.
That means preserving knowledge such as:
Which use cases worked
Which did not
What data was required
Which technical constraints appeared
Which suppliers performed well
Which governance decisions created friction
Which architecture patterns should be reused
What benefits were achieved
Without institutional learning, each new AI initiative begins too close to zero.
A strong AI operating model should reflect how the organisation really works, not only what process documents say. That means using three forms of enterprise knowledge.
Formal information such as:
Applications
Data
Infrastructure
Suppliers
Projects
Investment
Risks
Business capabilities
Structured assessment from:
Business leadership
AI specialists
Technology
Architecture
Cybersecurity
Data
Legal
Risk
Procurement
The context held in people's heads about:
How decisions are really made
Which governance processes work
Where informal workarounds exist
Which teams have hidden capability
Which suppliers are difficult to manage
Why previous AI projects struggled
Where accountability is unclear
This tacit knowledge is particularly important when designing a model that needs to work in practice rather than only on paper.
AI will continue to change.
The operating model therefore should not be designed as a fixed structure that assumes today's:
Technology
Suppliers
Models
Regulations
Skills
Risks
will remain unchanged.
It should establish durable principles while allowing specific processes and controls to evolve.
Leadership should be able to revisit:
Governance
Architecture standards
Supplier choices
Skills
Investment
Roles
Risk thresholds
as the environment changes.
Xirocco helps connect the enterprise context behind the operating model.
That can include:
Business priorities
Capabilities
AI opportunities
Data
Applications
Technology
Architecture
Cybersecurity
Suppliers
Risks
Investment
Existing operating-model capability
This helps identify whether the intended model fits the organisation around it.
For example:
AI Opportunity → Business Owner → Data Dependency → Architecture → Governance
or:
Operating-Model Responsibility → Required Capability → Current Gap → Investment
or:
AI Service → Supplier → Security Requirement → Operational Responsibility
The value is in designing the model around the connected enterprise rather than around an abstract AI framework.
Maeros AI can help interrogate the enterprise context behind operating-model decisions.
Questions might include:
Where are accountability gaps?
Which AI responsibilities should be centralised?
Which existing governance structures could be reused?
What technical weaknesses could prevent the operating model from working?
Which business capabilities need local AI ownership?
Where are supplier dependencies concentrated?
Which skills are missing?
What should leadership address first?
Follow-up questioning helps test the model against the realities of the organisation.
A complete model should usually address at least the following areas:
Business ownership
AI strategy
Opportunity identification
Prioritisation
Decision rights
Governance
Risk management
Architecture
Data
Cybersecurity
Delivery
Deployment
Operational support
Monitoring
Human oversight
Procurement
Supplier management
Skills
Partner model
Investment
Benefits realisation
Knowledge capture
Continuous improvement
The exact structure will vary.
What matters is that these responsibilities connect into a coherent operating system for enterprise AI.
A useful AI operating model should make it possible to answer:
If a business leader identifies a valuable AI opportunity tomorrow, what happens next?
Who assesses it?
Who owns it?
Who governs it?
Who designs it?
Who funds it?
Who builds it?
Who approves deployment?
Who operates it?
Who measures value?
Who remains accountable?
If the answers are unclear, the organisation does not yet have a complete operating model.
The goal is not to create the perfect diagram.
It is to create a model that lets the organisation repeatedly move valuable AI opportunities from idea to responsible enterprise operation.
Start a Conversation
Share what is on your agenda and we'll explore, without obligation, whether we can help.