A Question With No Universal Answer
The centralised versus decentralised debate resurfaces in almost every large ITSM engagement we undertake. And the honest answer is that neither model is universally superior — the right approach depends on organisational structure, culture, regulatory environment and strategic direction.
What we can say with confidence is that most organisations get this wrong in one of two predictable ways: either over-centralising to the point where local teams lose the agility they need to serve their users, or decentralising to the point where consistency, visibility and cost efficiency are sacrificed for local autonomy.
The Case for Centralisation
Centralised ITSM delivers significant advantages when done well. Consistency of process and tooling across the organisation makes reporting meaningful, enables genuine benchmarking, and reduces the cost and complexity of training and knowledge management. Centralised capabilities — particularly the service desk, change management and problem management — benefit from economies of scale that decentralised models cannot match.
Centralisation also creates the conditions for AI adoption. AI requires consistent, high-quality data across the organisation. A decentralised model with multiple ITSM tools and inconsistent processes cannot provide that foundation.
The Case for Decentralisation
Decentralised models have genuine advantages in organisations where business units or regions have significantly different service requirements, regulatory obligations or operating rhythms. Local ownership can drive stronger engagement and accountability than a central function that is seen as remote and unresponsive.
The failure mode of over-centralisation is well documented: a central ITSM function that is theoretically efficient but practically disconnected from the needs of the business units it serves, generating compliance at the expense of genuine service quality.
The Model That Actually Works
In practice, the most effective approach in complex organisations is a federated model — centralised standards, governance and tooling with local operational flexibility. Global process standards and a single ITSM platform ensure consistency and comparability. But service ownership, SLA negotiation and continual improvement are managed locally, by people who understand their users' needs.
"Centralise the standards. Decentralise the accountability. That combination tends to get the best of both worlds."
The federated model requires more governance effort than either pure centralisation or pure decentralisation — but it is significantly more likely to deliver both the consistency that senior leadership needs and the responsiveness that users actually experience.
Getting the Balance Right
The starting point for any organisation grappling with this question is an honest assessment of the current state — not just of processes and technology, but of culture and capability. The right model for a heavily regulated financial services firm with operations in fifteen countries is different from the right model for a rapidly growing professional services firm that has made three acquisitions in two years.
There is no shortcut past that contextual analysis. Organisations that adopt a model because it worked for a peer organisation, rather than because it fits their own structure and culture, tend to find themselves revisiting the decision within three years.
Is your ITSM as good as it should be?
Our independent benchmarking assessment gives IT leaders a clear, evidence-based picture of where their service management stands — and exactly what to do about it.
Book a Free Strategy Session →