# IT operating model: signs it no longer fits, and how to redesign it

> Most IT organisations were never designed; they grew. This guide gives you twelve warning signs that the operating model no longer fits, the eight lenses to assess it, the eight design choices to make before drawing any boxes, and a ten-week method to a target the executive committee can approve.

Source: https://ciohelm.com/guides/it-operating-model · By the CIO Helm team · Updated 2026-11-13

## What an IT operating model is

An IT operating model is how technology work actually gets done: who decides what, how the organisation is structured, how work flows from demand to running service, who does the work (your people or partners), how it is funded, and how performance is measured. The organisation chart is only one part of it.

Most IT operating models were never designed. They grew, one reorganisation and one acquisition at a time. That is not a problem in itself. It becomes one when the business has changed and the model has not.

## Twelve signs your operating model no longer fits

Count how many of these you recognise. Up to four suggest targeted fixes; five or more usually mean the model itself needs redesign.

| Area | Warning sign |
| --- | --- |
| Decisions | The same decision is taken twice, by a business unit and by IT, or by nobody |
| Decisions | Everything of any size is escalated to the CIO or the executive committee |
| Business partnership | Business leaders describe IT as an order taker, and IT describes the business as unclear |
| Structure | Regional or business-unit IT teams duplicate each other's work and systems |
| Structure | Technology staff outside IT are as numerous as some IT teams, with no common standards |
| Delivery | Projects hand over to operations teams that were not involved, and incidents follow go-live |
| Delivery | Work starts faster than it finishes; nobody can say how much is in progress |
| Sourcing | Dozens of providers, each managed separately, and nobody owns the overall result |
| Architecture | Every acquisition adds its own systems, and none are retired |
| People | Critical knowledge sits with a few people or a partner, and the skills you need next are not being built |
| Funding | Nobody can say what each business unit consumes, or what a service costs |
| Performance | IT measures activity (tickets, projects) and the business measures disappointment |

## Assess it through eight lenses

A useful assessment looks at the whole model, not just the structure, and scores each part on evidence, today and in the target.

| Lens | The question |
| --- | --- |
| **Strategy and value** | Is technology work tied to business outcomes, and is the value tracked? |
| **Governance and decisions** | Are decision rights clear, and taken at the right level? |
| **Structure and roles** | Does the organisation fit the work, without gaps or duplication? |
| **Services and delivery** | Does work flow from demand to running service without waste? |
| **Architecture and data** | Is the landscape simple enough to change, and is data owned? |
| **Sourcing and partners** | Is the split between your people and partners deliberate and well managed? |
| **People and culture** | Do you have, and keep, the skills and leaders the model needs? |
| **Funding and performance** | Are costs visible, funding aligned to priorities, and performance measured? |

Hear both sides. A short survey of IT and business leaders on the same statements often shows the most useful finding of all: where IT rates itself well and the business does not. Interviews then explain why.

## Eight design choices

There is no best operating model, only choices that fit your business. Make them explicit, each on a line between two ends, and agree where you are today and where you want to be:

| Choice | From | To |
| --- | --- | --- |
| Where technology decisions sit | Each business unit decides | One enterprise decision |
| How IT is organised | By technology tower | By business product or value stream |
| How change is funded | Project by project | Persistent product teams |
| What you do yourselves | Mostly in-house | Mostly partners |
| How standard you are across countries | Local variation | Global standard |
| Who builds technology | IT builds everything | Business builds on IT platforms |
| Plan, build and run | Separate teams hand over | Teams build and run what they build |
| How IT engages with the business | Delivers to agreed service levels | Co-owns business outcomes |

Both ends of every line are valid; the right position depends on your business. Most companies land somewhere in the middle on most lines, and that is fine. The value is in agreeing the position deliberately, with the executive committee, before drawing any boxes. An organisation chart drawn before the choices are made is a reorganisation looking for a reason.

In manufacturing, one more line matters: who owns the systems that run the plant. Our sister site FactoryHelm covers it in [IT/OT convergence governance: who owns what](https://factoryhelm.com/ot-security/it-ot-convergence-governance/)

## The method in ten weeks

| Weeks | Work | Output |
| --- | --- | --- |
| 1–2 | Charter, scope and governance; data request; survey launched | Agreed scope; baseline data |
| 3–6 | Interviews and focus groups; practices scored on evidence; survey closed; findings tested with the people closest to them | Scores by lens; findings |
| 7–8 | Findings to the executive committee; design principles and choices workshop | The five or so moves that matter; agreed principles and positions on the eight choices |
| 9–10 | Target model: structure, decision rights, forums, sourcing, people, funding; transition plan in waves, with risks and measures | Target model and transition plan for decision |

## Make the transition safe

- **Move in waves** with a review before each one, so that lessons from the first change the second.
- **Protect service** during the move: name who owns each critical service on every day of the transition.
- **Start consultation early** where employee representatives must be informed or consulted. It often sets the timetable in some countries.
- **Appoint the leaders of the new units before the announcement**, so that every team knows who it reports to on day one.
- **Publish decision rights** with the new structure, or the old habits will carry on inside the new boxes.
- **Measure the result**: the same survey a year later, decision speed, work in progress, and service and cost measures.

### Assess and redesign with the IT Operating Model Assessment Kit

A 16-sheet workbook scoring 40 practices across eight lenses today and in the target, with the stakeholder survey, interview notes, findings, organisation baseline, eight design choices, a decision rights matrix and the transition plan, plus findings and target model decks and nine documents from the charter to the transition plan. One-time price , no subscription.

[Download the kit](https://ciohelm.com/download/it-operating-model-assessment-kit)[See what is inside](https://ciohelm.com/toolkits/it-operating-model-assessment-kit)

## Questions

**How often should an IT operating model be reviewed?**

Look at it every year as part of the strategy refresh, and assess it in depth after a major change in the business: an acquisition, a new strategy, a new CIO, or a move to a different sourcing model. Redesign when the strategy, the business structure or the sourcing model changes, not on a fixed cycle.

**Should IT be organised around products or technology towers?**

It depends on the work. Product teams suit areas of steady change close to customers or core processes; towers still suit shared infrastructure and commodity services. Most companies end up with a mix, and that is a design choice rather than a compromise.

**Centralised or federated IT?**

Decide decision by decision rather than for IT as a whole. Platforms, security and data standards usually benefit from being enterprise decisions; local choices can stay local where business needs really differ.

**Who should run the operating model assessment?**

The CIO owns it, with a sponsor on the executive committee. An independent facilitator helps with interviews and the business survey, because people speak more openly to someone outside the line, and because the CIO's own team are interested parties in the outcome.

## Toolkits on this topic

- [IT Talent and Upskilling Kit](https://ciohelm.com/toolkits/it-talent-and-upskilling-kit): a ready IT upskilling plan and a learning path for 53 IT roles
- [GCC Cost Model](https://ciohelm.com/toolkits/gcc-cost-model): price a global capability centre in India or the Philippines four ways
- [GCC Setup Kit](https://ciohelm.com/toolkits/gcc-setup-kit): set up a global capability centre in India or the Philippines

## Related

- [Technology RACI: one owner for every IT activity](https://ciohelm.com/guides/technology-raci)
- [IT team skills review](https://ciohelm.com/guides/it-team-skills-review)
- [IT steering committee: terms of reference that make it decide](https://ciohelm.com/guides/it-steering-committee)
- [Digital Maturity Assessment](https://ciohelm.com/digital-maturity)
