IT Operating Model Framework

Why a Framework Matters When Designing and Building an IT Operating Model

There is no shortage of organisations that have attempted to transform their IT function and fallen short. Not because the ambition was wrong, or the investment insufficient, but because the work lacked a coherent structure. Teams were redesigned without reference to strategy. Technology was replaced before processes were understood. Governance was bolted on after the fact. The result, in too many cases, was significant expenditure with underwhelming outcomes and a workforce left wondering what had actually changed.

This is precisely why a structured framework matters when designing and building an IT operating model. Without one, transformation becomes a series of disconnected initiatives rather than a purposeful programme of change. With one, organisations can make confident, joined-up decisions about how their IT function should be structured, governed, staffed, and equipped to deliver.

What is an IT Operating Model and Why Does it Need a Framework?

An IT operating model describes how an organisation's technology function is designed to work, how it makes decisions, organises its people, delivers services, and aligns to the wider business. It is, in essence, the blueprint for how IT operates in practice rather than in theory.

The challenge is that operating models are complex. They span strategy, governance, people, processes and technology, and the decisions made in each of these areas are deeply interdependent. Change the organisational structure without updating the governance model and accountability becomes unclear. Invest in new technology platforms without defining the supporting processes and the investment fails to land. Articulate a bold technology strategy without mapping the skills needed to execute it and the ambition outpaces the capability.

A framework provides the structure needed to navigate this complexity. It ensures that every dimension of the operating model is considered, that design decisions are made in the right sequence, and that the resulting model is coherent rather than a patchwork of good ideas that do not quite fit together. It also gives clients and stakeholders a common language, which in our experience is one of the most underrated enablers of successful transformation.

Introducing the IT Operating Model Framework

I have developed a framework that organises the IT operating model across five interconnected domains: Strategy, Governance, People, Processes and Technology. Each domain contains a set of discrete capabilities that together define what a well-functioning IT operating model looks like in practice.

The framework is not a rigid template. It is a structured starting point that can be adapted to the specific context, ambition and constraints of each client engagement. What it provides is confidence that nothing important has been overlooked and that the design decisions made in one area are consistent with those made in others.

Strategy defines the direction, ambition and capabilities that ensure IT investment and delivery are aligned to the organisation's broader commercial goals. Without a clear and well-articulated strategy, the remaining layers of the operating model risk becoming disconnected from business value and difficult to prioritise. The Strategy domain encompasses four capabilities: Business & IT Strategic Goals, which anchors every other design decision to measurable outcomes; Technology Strategy & Innovation, which sets the direction for how technology creates competitive advantage; Capabilities, which maps what IT must be able to do well in order to deliver on the strategy; and Value Streams & Service Catalogue, which makes IT's contribution tangible and measurable by describing the end-to-end flows through which value is delivered.

Governance establishes the structures, controls and accountability mechanisms that enable IT to operate with confidence, consistency and appropriate oversight. Effective governance balances the rigour needed to manage risk with the agility required to make decisions at pace and deliver outcomes. The Governance domain covers eight capabilities spanning the Control Framework, Policy Framework, Governance Model, Risk Management Approach, Decision Rights & Accountability, Critical Success Factors, Performance Management Framework and Cybersecurity Framework. Together these capabilities ensure that IT operates within agreed boundaries, that performance is measured and acted upon, and that the organisation is protected from the threats that increasingly define the risk landscape.

People shapes the organisational design, culture, roles and skills that determine whether the operating model can be staffed, led and sustained in practice. Getting the people layer right is frequently the difference between a well-designed model that works on paper and one that genuinely takes hold across the organisation. The People domain addresses four capabilities: Organisational Model, which defines how IT is structured and how teams relate to one another; Culture & Behaviours, which shapes the values and mindsets that determine how people respond to change; Roles & Responsibilities, which provides the clarity needed for teams to work without duplication or gaps; and Skills & Competencies, which maps the technical and behavioural capabilities the workforce needs to deliver on its ambitions.

Processes defines the ways of working, delivery methodologies and operational processes through which IT consistently turns strategy into outcomes. Mature, well-understood processes reduce waste and variability, giving teams the clarity they need to collaborate effectively and improve continuously. The Processes domain covers Development & Delivery Methodology, which governs how IT plans, builds and releases products and services; Service Management Processes, which ensures services are reliably available and supportable; Programme & Project Lifecycle, which provides the structure through which larger initiatives are delivered and benefits tracked; and Collaboration & Knowledge, which prevents the siloing of expertise and accelerates institutional learning.

Technology provides the platforms, infrastructure, tooling and partner relationships that underpin reliable service delivery and enable the organisation to innovate at speed. The Technology layer must be actively managed to ensure it supports the operating model's current needs whilst remaining flexible enough to adapt as those needs evolve. The Technology domain encompasses Infrastructure & Operations, which provides the stable foundation upon which all services depend; Products & Platforms, which shifts the focus from project delivery to sustained value creation; Tooling & Observability, which gives teams the visibility they need to operate confidently and improve continuously; and Partners & Supply Chain, which ensures the organisation can access the skills and capacity it cannot sustain internally.

A Lifecycle Designed for the Real World

Alongside the framework itself, we use an Agile IT Operating Model Design, Build and Implement Lifecycle that guides clients through the end-to-end process of designing and embedding a new or updated operating model. The lifecycle moves through eight interconnected steps, from framing the business challenge and setting strategic direction, through establishing governance, designing the organisation, defining processes and implementing technology, to building the operating model blueprint and ultimately embedding it through ongoing delivery and support.

Critically, the lifecycle is circular rather than linear. Operating models are not a one-time deliverable. They need to evolve as business priorities shift, as technology advances, and as organisations learn what works. The lifecycle is designed to support that ongoing evolution, with the Build/Update the Operating Model Blueprint and Deliver & Support steps sitting at the centre as the continuous activities that hold everything together.

What This Means in Practice

When a clients need to design or redesign their IT operating model, the framework does several important things. It provides a structured lens through which to assess the current state, identifying which capabilities are mature, which are absent and which are misaligned to the organisation's strategy. It guides the target state design, ensuring that decisions across all five domains are coherent and mutually reinforcing. And it gives the transformation programme a clear scope, preventing the common failure mode where some dimensions of the operating model are addressed thoroughly whilst others are quietly set aside.

The organisations that get the most from their IT functions are not necessarily those with the largest budgets or the most advanced technology. They are the ones that have taken the time to think carefully about how they operate, and who have used a structured approach to turn that thinking into a model that their people can actually work within. That is what this framework is designed to help clients achieve.