The Label That Determines the Decisions
The cost centre designation is not merely an accounting classification. It is a governance model, an incentive structure, and a cultural signal that shapes how IT leaders make decisions, how technology teams understand their purpose, and how the rest of the organisation perceives the value of technology investment.
When IT is a cost centre, every decision it makes is optimised for cost management rather than value creation. The infrastructure investment that would enable a new digital product is evaluated as a cost line rather than as an investment with expected return. The security programme that would reduce the organisation’s risk exposure is funded from an overhead budget that finance looks to reduce rather than from an investment budget calibrated to the risk reduction it delivers. The platform team that would accelerate the engineering organisation’s delivery velocity competes for the same budget reduction targets as every other IT overhead.
These are not the decisions that technology leadership makes when it has freedom to make them. These are the decisions that the cost centre model produces regardless of who is making them, because the model’s constraints and incentives are structural. Changing the decisions requires changing the model, not changing the decision-makers.
This is the first article in a three-part series on IT operating model transformation. It argues that cost centre thinking is the root cause of most enterprise IT performance problems, not a symptom of insufficient technology investment or management capability. Understanding it as a root cause changes what the solution looks like.
How Cost Centre Thinking Embeds Itself
Cost centre thinking embeds itself in enterprise IT through three structural mechanisms that reinforce each other.
The governance mechanism is the budget process. Annual budget cycles that allocate IT spending as a percentage of revenue or as a flat overhead target disconnect technology investment from business outcome. The IT budget is approved based on what last year’s budget was, adjusted for inflation and the most visible cost pressures, rather than based on what technology investment the organisation’s business strategy requires. This governance mechanism makes it structurally impossible for IT to make the case that a given technology investment should be increased because the business outcome it enables justifies the investment. The budget process is designed to reduce the overhead, not to optimise the investment.
The incentive mechanism is the performance management framework. IT leaders in cost centre models are measured on cost adherence, project delivery against plan, and operational metrics: uptime, ticket resolution times, project completion percentages. These metrics measure whether IT is managing its cost efficiently. They do not measure whether IT is enabling business value. When cost management metrics are the primary performance measures, cost management becomes the primary organisational objective, and value creation competes against it.
The cultural mechanism is the perception of IT’s role. In organisations where IT is a cost centre, the business relationship between IT and the lines of business is a service relationship: IT provides services that the business uses, and the business evaluates those services primarily by their cost and reliability. In this relationship model, IT is a supplier rather than a partner, and its contribution to business strategy is evaluated as service quality rather than as strategic capability. The cultural distance between IT and the business that characterises most large enterprises is an output of this service relationship model.
Why These Three Mechanisms Must Be Addressed Together
The reason most IT operating model transformation efforts fail to durably change IT’s positioning from cost centre to value engine is that they address one or two of these mechanisms without addressing all three.
Measurement redesign without governance change produces new metrics that are collected and reported but that do not affect the budget decisions that continue to be made on cost overhead principles. The CIO can show the CFO metrics demonstrating IT’s contribution to business revenue, but if the budget process continues to evaluate IT as an overhead to be managed, those metrics do not change the budget outcome.
Governance change without incentive realignment produces a budget process that in theory could fund IT as a value investment but that in practice continues to fund IT as a cost overhead because the IT leaders participating in the budget process are still measured on cost efficiency. They advocate for the investments that their performance management framework rewards them for managing.
Incentive change without cultural change produces IT leaders who are trying to behave as value-focused partners in a relationship model that the business still experiences as a service relationship. The business units that expect IT to respond to their requests do not change their expectations because IT’s internal performance metrics have changed.
Durable transformation requires addressing all three mechanisms: changing the budget governance to evaluate technology investment against business outcome, redesigning IT performance management to measure business value contribution, and changing the business-IT relationship model from service to partnership. These changes reinforce each other, and they require executive engagement at a level above IT leadership because the governance and incentive mechanisms that need to change are owned by the CFO and the board, not by the CIO.
The Board and Executive Level Change Required
The most important implication of understanding cost centre thinking as a root cause rather than a symptom is that the change required begins above the IT function.
IT leaders cannot change the budget process that evaluates their investment. They cannot redesign the performance management framework that measures their outcomes. They cannot redefine the relationship model that determines how the business treats them. All of these changes require the CFO’s participation in redesigning the budget and financial governance process, the CEO’s endorsement of the new operating model and its implications for how technology is governed, and the board’s approval of a technology investment philosophy that recognises the strategic value of technology capability alongside its operational cost.
This is why operating model transformation that begins and ends within the IT function rarely produces durable change. The root cause is not IT’s behaviour or IT’s measurement. The root cause is the governance model that the board and executive team have established for technology, and changing it requires their active participation.
The second article in this series examines what designing IT as an internal service provider looks like in operational terms, and why even this intermediate model represents a significant improvement over the cost centre starting point. The third article provides the metrics framework that proves the transformation is delivering.
What this first article establishes is the most important premise: the change is not primarily a technology change. It is a governance change that requires the board and executive team to decide that technology is a strategic capability and fund it accordingly.