An IT operating model describes how an organization’s IT function works: how it is structured, who decides what, which processes it follows, which work is done in-house versus by providers, where staff are located, how it is funded, and how it measures success. It turns an IT strategy into day-to-day practice. Every IT department has one, whether it was designed deliberately or grew over time, and redesigning it is common after mergers, cloud moves, large outsourcing decisions or new leadership.
At a glance
- An IT operating model covers structure, governance, processes, people, sourcing, location, funding and technology.
- It explains how IT delivers value, not which technology it buys.
- Common approaches include traditional functional or plan-build-run models, product-based models and platform-based models, often in combination.
- Sourcing choices, such as outsourcing, managed services or a company-owned offshore center, are part of it.
- A “target operating model” describes the intended future state, usually with a roadmap to reach it.
What problem it solves
IT departments tend to accumulate structure over years: teams formed around old systems, outsourcing contracts signed for one reason and kept for another, overlapping roles and unclear decision rights. The symptoms are familiar: slow delivery, disputes over priorities, duplicated tools, and a business that sees IT as a cost center rather than a partner.
Defining the operating model makes these choices explicit. It answers who owns each service, how demand is prioritized, which capabilities matter enough to keep in-house, how providers are governed, and how money flows. With that clarity, sourcing decisions and reorganizations can be judged against a shared target instead of made one at a time.
How it works
Components. Operating models are usually described across a few dimensions: organization and roles, governance and decision rights, processes such as IT service management (ITSM), sourcing and partners, locations, technology and tools, funding, and performance measures.
Organizing approaches. A traditional model groups IT by function, such as infrastructure, applications and support, often split into plan, build and run. A product operating model organizes long-lived teams around business products or capabilities, with ongoing funding. A platform approach groups shared services into internal platforms consumed by those teams, which links to platform engineering. Most organizations blend these.
Sourcing. The model decides which capabilities are retained, which are delivered by outsourcers or managed service providers, and which might sit in a global capability center (GCC). With several providers, a service integration and management (SIAM) layer may be needed to coordinate them.
Design and transition. A redesign typically assesses the current state, defines a target operating model, plans the transition (people, contracts, tools, processes) and tracks adoption. Enterprise architecture (EA) often informs the technology side.
When it matters for buyers
- Before a large outsourcing or managed services decision. Know what you want to retain before deciding what to buy.
- During mergers and divestitures. Combining or separating IT functions forces operating model choices, as in post-merger IT integration.
- When moving to the cloud or adopting DevOps. These change roles, skills and processes, not just technology.
- When a new CIO, CFO or CEO arrives. New leaders often review how IT is organized and funded.
- When provider contracts renew. Renewals are a chance to align sourcing with the intended model.
Questions to ask vendors
These questions apply to consultants helping design a model and to providers proposing to take over part of it:
- What current-state assessment do you perform, and what data do you need from us?
- How do you decide which capabilities we should retain versus outsource?
- What organizing approaches do you recommend for a company of our size, and why?
- How will the retained IT team manage you and other providers after the change?
- How do you handle the people side: role changes, transfers and retention of key staff?
- What does the transition plan include, and how are risks to service during the change managed?
- How will we measure whether the new model is working?
How it differs from IT service management
IT service management (ITSM) is the set of processes IT uses to deliver and support services, such as incident, request and change management. It is one component of the operating model. The operating model is broader: it also covers structure, decision rights, sourcing, location and funding, and it decides how ITSM processes are split between internal teams and providers. If you are weighing outsourced support as part of a redesign, see our help desk overview.