The Label That Sticks
The ticket-taker label is a summary judgment about the nature of IT’s relationship with the rest of the business. It means: IT responds to requests from the business. It does not initiate. It does not advise. It does not challenge. It processes the requests in the queue, in the order they arrive, at the pace the queue allows. The business decides what it wants; IT executes what the business decided.
This label is not the result of IT’s incompetence. It is the result of a structure that was designed to produce exactly this dynamic. The service desk was designed to receive and process requests. The project management office was designed to execute the projects the business sponsors. The governance process was designed to ensure IT resources are allocated in response to business demand. The cost centre model was designed to measure IT’s efficiency at processing that demand. Every structural element of the traditional IT operating model produces and reinforces the ticket-taker dynamic.
Changing the label requires changing the structure. Announcing that IT is now a strategic partner without changing the structure that produces the ticket-taker dynamic is a communication programme, not a transformation. The communication will not hold against the gravity of the structure.
What the Structure Must Change
The structural changes that create the conditions for strategic partnership are distinct from the communication changes that signal the intent. Both are necessary. Only the structural changes are sufficient.
The funding model must change. The IT function funded entirely through project demand from business units is structurally positioned as a request processor. Each project brings its own sponsor, its own scope definition, and its own priorities. IT’s role is to deliver against those externally defined scopes. The IT function that has a proportion of its funding as discretionary investment, allocated by IT leadership to proactive capability development rather than reactive project delivery, has the structural foundation for strategic initiative. The discretionary funding allows IT to invest in capabilities before the business requests them, which is the structural prerequisite for proactive advice.
The delivery model must change. The project delivery model receives defined requirements and produces systems that match those requirements. It optimises for delivery against specification. It does not create the feedback loops that enable IT to learn from what the business needs and develop capabilities in advance of specific requests. The product delivery model maintains ongoing relationships with internal customers, observes how technology capabilities are used, and evolves those capabilities in response to observed needs rather than defined requirements. The shift from project to product delivery is the shift from request processor to proactive partner.
The planning cadence must change. IT organisations that plan on a project portfolio cycle are inherently reactive: the plan reflects the projects that business units have requested. IT organisations that participate in the business planning cycle are in a position to identify how technology capabilities can contribute to business priorities that are being defined, rather than being informed of business priorities after the business has determined how to address them.
The leadership behaviour must change. The IT leadership team that operates from behind the service desk, receiving and prioritising the demand that arrives, will not be perceived as a strategic partner regardless of the quality of its delivery. The IT leadership team that spends significant time with business unit leaders, understanding their strategic challenges and proactively identifying how technology capabilities can address them, is demonstrating the advisory behaviour that strategic partnership requires.
The Communication Strategy That Reinforces the Structure
The communication strategy for IT repositioning works when it is reinforcing structural changes that have already happened, not when it is announcing changes that have not yet been made.
The communication that lands is specific about what has changed. Not “IT is now a strategic partner” but “we have restructured IT delivery around product teams with ongoing relationships with each business unit, and here is what that means for how we work together.” Not “IT is no longer a ticket-taker” but “we are investing ten percent of our capacity in proactive capability development, and here is the first output of that investment: a proposal for how we can address the customer data challenge that has been on the executive agenda for the past two quarters.”
Specificity matters because the credibility of the repositioning is built through demonstrated behaviour rather than declared intent. The business leaders who have experienced IT as a ticket-taker organisation over many years will update their perception slowly and in response to evidence, not quickly and in response to announcement. The evidence accumulates through a sequence of specific interactions in which IT behaved differently from the ticket-taker pattern: brought an unsolicited recommendation, challenged a business assumption about what the technology could do, identified a capability need before the business articulated it.
The Metric That Proves the Transition
The metric that proves IT has transitioned from ticket-taker to strategic partner is not a satisfaction survey. It is whether business leaders bring IT into strategy conversations before they have decided what they want, rather than after.
The ticket-taker IT function is informed of business decisions and asked to execute them. The strategic partner IT function is consulted during business decision-making and expected to contribute. The test of whether the transition has been made is observable in the business leadership’s behaviour: are they coming to IT with open questions or with defined requirements?
This transition does not happen through a programme or a communication strategy. It happens through a sequence of engagements in which IT proves that it is worth consulting before decisions are made, because its input changes the quality of those decisions. The IT function that consistently proves this will be consulted. The one that does not will continue to receive requirements to execute.
The strategic partner identity is earned through performance, not declared through announcement. The structural changes create the opportunity to perform differently. The performance earns the identity. There is no shortcut between them.