IT has spent thirty years trying to shed the cost centre label, mostly by getting better at the wrong things.
The standard approach is to improve operational metrics: drive up uptime, drive down ticket resolution time, deliver projects closer to schedule. All worth doing, and none of it changes the perception, because none of it speaks the language the business uses to decide what matters. A faster ticket queue is a better cost centre, not a business partner. The label does not move, because the thing the label describes has not moved.
The Cost Centre Label Is Earned by the Metrics You Choose
A function is perceived through what it measures and reports, and IT has historically measured itself in the vocabulary of cost and operations. Uptime, tickets, project delivery: these are the metrics of a service to be consumed and minimised, and reporting them faithfully every month reinforces exactly the perception IT says it wants to escape. The business hears a department accounting for its costs, not a partner accounting for its contribution.
Changing the perception starts with changing the measures, but not to vanity metrics. It means reporting IT in terms of the business outcomes it enables: revenue supported, time-to-market improved, risk reduced, customer experience moved. That shift is uncomfortable, because outcome metrics are harder to claim cleanly and force IT to connect its work to results it does not fully control. The discomfort is the point. It is the difference between a department that reports its activity and a partner that reports its impact.
Three Shifts That Actually Move the Perception
Repositioning IT rests on three shifts, and skipping any one of them leaves the label intact. The first is from reactive service delivery to proactive value creation: IT stops waiting to be asked and starts bringing opportunities to the business, which is what partners do and suppliers do not. The second is from infrastructure ownership to capability enablement: IT measures itself by the capabilities it puts in the hands of the business, not the assets it controls. The third is from IT-defined metrics to business-outcome metrics, so the conversation happens in the board’s language rather than the datacentre’s.
None of these is a tooling change, and that is why so many repositioning efforts fail. They invest in a better service catalogue or a slicker portal and wonder why the perception holds. It holds because the underlying relationship did not change. IT still behaves as a supplier, and suppliers are managed as costs no matter how good their portal looks.
The Three Levers That Make It Real
Three levers turn the shifts from slogans into a changed relationship. The first is operating model design: how IT is structured, funded, and held accountable has to reflect a partner that owns outcomes, not a supplier that fulfils requests. The second is financial transparency: IT has to show, credibly, what its spend produces in business terms, because a partner that cannot account for its value in the business’s own language is still treated as a cost. The third is executive communication: the relationship is partly a narrative, and IT leaders who cannot tell the value story to the board will be assigned the cost-centre story by default.
These levers reinforce each other. Transparency without operating model change is a better report on the same old supplier. Communication without transparency is spin the business eventually sees through. Pulled together, they change not just how IT is perceived but how it actually operates, which is the only change that lasts.
A 90-Day Programme to Start
The repositioning is a campaign, not an announcement, and it can start inside a quarter. In the first thirty days, establish the baseline: how does the business currently describe IT, and which outcomes does the business actually care about. In the next thirty, build the financial transparency to connect IT spend to those outcomes, even imperfectly, because an honest first attempt beats waiting for a perfect model. In the final thirty, change the communication: replace the operational status report to leadership with an outcomes conversation, framed in business terms, owned by the IT leader personally.
Ninety days will not finish the job, but it will start the only thing that ever changes the label: a visible, sustained shift in what IT talks about and how it behaves. The perception follows the behaviour on a lag, and the lag is why this has to be a programme and not a memo.
The Label Changes Last
The hardest thing to accept about repositioning IT is that you cannot do it directly. You cannot communicate your way out of a cost centre, or announce a partnership into existence. The label is a lagging indicator of behaviour, and it changes last, after the metrics change, after the transparency arrives, after IT has spent enough quarters bringing outcomes to the business that the business quietly updates its mental model. Do the work in the right order and the label takes care of itself. Reach for the label first, and you get a department that calls itself a partner while everyone else still files it under cost.