IT Operating Model
What is IT Operating Model?
An IT operating model describes how an organization's technology function is structured and run, including its services, processes, teams, sourcing, governance, funding and the way it works with the business.
Updated November 2026 · 5 min read
An IT operating model explains how technology work actually gets done. It covers what services the IT function provides, how teams are organized, which work is done internally and which by partners, how decisions are made, how work is funded and how IT engages with business units. Two organizations with similar technology can operate very differently: one may run a central IT department that delivers projects for the business, while another embeds technology teams in product lines with their own budgets.
The operating model matters because it shapes cost, speed and quality as much as the technology itself. An organization moving to cloud services, product-based delivery or a shared services structure needs its operating model to change too, or the new technology will not deliver its expected benefits. For enterprise architecture and IT finance, the IT operating model determines where costs sit, who controls them and how technology investment decisions are made.
Definition of IT Operating Model
An IT operating model is a description of how the IT function creates and delivers value, covering people, processes, technology, sourcing, governance and finance. It is often documented as a set of principles, structures and responsibilities rather than a single diagram.
It is one part of the broader operating model of the organization and should reflect the IT strategy. A target operating model describes the future state the organization intends to move toward.
Core Elements
Services define what the IT function provides to the business, such as end-user support, applications, infrastructure, data and security. A clear service catalog makes these offerings visible.
Organization and roles define how teams are structured, such as by technology tower, by business unit, by product or by platform, and which responsibilities each role holds.
Processes and ways of working describe how demand is handled, how changes are delivered and how services are supported, such as agile delivery, service management and change control.
Sourcing, governance and funding describe which work is outsourced, how decisions are made and approved, and how IT costs are budgeted and allocated to the business.
Common Operating Model Patterns
A centralized model places most technology staff and budgets in one IT function, which delivers services to all business units. It supports consistency and economies of scale but can be slow to respond to individual needs.
A federated model splits responsibility, with central IT running shared platforms and standards while business units run their own technology teams for local needs.
A product-based model organizes persistent teams around products or value streams, each responsible for building and running its services, supported by shared platform teams. Many organizations mix these patterns in different areas.
Importance of the IT Operating Model in Enterprise Architecture
The operating model determines how architecture decisions are made and enforced. A strong central model may make standards easier to apply, while a federated model needs clear governance to avoid fragmentation.
It affects speed. Organizations whose operating model matches their strategy can deliver change faster than those where structures and processes work against it. Handoffs between teams, approval steps and funding cycles often account for more delay than the technical work itself.
It also affects cost, since the structure of teams, the level of outsourcing and the duplication of roles across units drive a large share of IT spending.
Funding and Cost Visibility
The operating model defines how IT is funded, whether through central budgets, project funding, persistent team funding or charges to business units.
It also determines how costs are made visible. Models that use IT showback or chargeback help business leaders understand the cost of the services they consume.
Frameworks such as technology business management connect operating model choices to cost data, showing how changes in structure or sourcing affect spending.
Moving from project funding to persistent team funding is one of the most common operating model changes, and it changes how investment decisions and benefits are tracked.
Common Challenges
Operating models often evolve without design, as new teams, tools and partners are added over time. The result can be duplicated roles, unclear responsibilities and gaps between teams.
Changing an operating model affects people's roles, reporting lines and ways of working, so it requires careful change management and leadership support. Clear communication about why the change is happening and what it means for each team reduces uncertainty.
A model copied from another organization may not fit. The right design depends on strategy, size, regulation and the capabilities of existing teams.
How to Design an IT Operating Model
Designing an operating model involves understanding the strategy, assessing the current model, defining the target and moving toward it in stages.
The design should start from the outcomes the business needs, not from an organization chart.
Assessing and Designing
Clarify the business and IT strategy, and identify what the operating model must achieve, such as faster delivery, lower cost or stronger control.
Document the current model, including services, teams, processes, sourcing, governance and funding, and identify problems such as delays, duplication or unclear ownership.
Design the target model, choosing patterns for each area and defining roles, decision rights and funding mechanisms. Use the business capability map to align technology teams with business capabilities where appropriate.
Implementing Change
Move to the target model in stages, starting with areas where the benefits are clearest or where pilots can show results. Lessons from early stages can then refine the design before it is applied more widely.
Update processes, governance and funding along with structures, since changing reporting lines alone rarely changes outcomes.
Track measures such as delivery speed, service quality, cost per service and employee engagement, and adjust the design based on results.
Examples of IT Operating Models in Enterprise Architecture
The examples below show operating model changes and their effects.
Both use illustrative figures. The first moves to product teams, and the second consolidates duplicated functions.
In each, structure, process and funding changed together.
Moving to Product Teams
A retailer's central IT department delivers projects for its digital channels, with an average of nine months from request to release.
It creates eight persistent product teams for its main digital products, funded annually rather than by project, with shared platform teams for infrastructure and data.
Average time from idea to release falls to about seven weeks, and business leaders gain clearer visibility of what each product costs to build and run.
Consolidating Duplicated Functions
A manufacturer has grown through acquisition, and each of its five divisions runs its own service desk, infrastructure team and security function.
A new operating model centralizes these shared services while leaving application teams in the divisions.
Over two years, the combined cost of the centralized functions falls by about $9 million a year, and service quality becomes consistent across divisions.
Conclusion
An IT operating model describes how the technology function is structured and run, covering services, organization, processes, sourcing, governance and funding. Common patterns include centralized, federated and product-based models.
In enterprise architecture, the operating model shapes how decisions are made, how quickly change happens and how much technology costs. Starting from strategy, documenting the current model honestly, designing the target with clear roles and funding, changing structures and processes together and measuring results help organizations build an operating model that supports their goals.
Related terms
IT Strategy
An IT strategy is a plan that sets out how an organization will use information technology to support its business goals, including priorities, investments, capabilities, operating model and measures of success.
Target Operating Model
A target operating model is a description of how an organization intends to operate in the future to deliver its strategy, covering its capabilities, processes, structure, people, technology, data, locations and governance.
Business Capability Map
A business capability map is a structured view of everything an organization must be able to do to carry out its strategy, organized into levels and independent of who performs the work or how.
Digital Twin of an Organization
A digital twin of an organization is a data-driven model of how an organization works, connecting strategy, capabilities, processes, people, systems and costs so leaders can test changes before making them.