The Cost of Being Seen as IT Support
Language shapes reality in organizations. When the business refers to IT as "support" — and when the CIO accepts that framing — it sets in motion a logic that is difficult to escape. Support functions are essential, respected, and definitionally subordinate. They serve strategies set by others. They are funded at levels the business deems adequate. They are evaluated on responsiveness, not vision.
:::kicker Module 1: The Influence Gap · Article 2 of 14 :::
The damage done by the IT support framing is not primarily to the CIO's career. It is to the organization's decision quality. Technology decisions made without technology leadership produce predictable, expensive outcomes. This article maps those costs — and identifies the specific patterns that CIOs need to recognize in their own organizations before they can address them.
How the Framing Gets Established
The IT support framing is rarely imposed consciously. It accumulates through a series of defaults, each individually reasonable, collectively defining.
A new business initiative is planned by the business unit. IT is brought in to "support" the implementation. The initiative runs over budget and schedule — as most IT projects do — and the business concludes that IT is slow and expensive. The next initiative is planned with a smaller IT footprint, or with a SaaS vendor that promises to reduce IT dependency. The CIO's scope narrows. The perception calcifies.
:::callout The framing trap in practice: A business unit leader decides to implement a new CRM platform. They select the vendor, negotiate the contract, and then bring IT in to "handle the technical integration." When the integration takes longer than expected, it confirms the business leader's prior: IT is a bottleneck. What is invisible in this narrative is that IT was never given the opportunity to shape the decision that created the complexity they are now blamed for. :::
This pattern — late involvement, narrow scope, blame for consequences of decisions made before IT arrived — is the mechanism by which the support framing sustains itself.
The Tangible Costs
The support framing produces specific, measurable costs that CIOs can point to when making the case for repositioning.
Cost 1: Suboptimal architecture from uncoordinated decisions. When business units select technology without IT input, the enterprise ends up with fragmented architecture: multiple CRM instances, overlapping data platforms, integration debt that compounds with every new system. The cost of this fragmentation — in duplicate licenses, integration maintenance, and data quality problems — is typically far larger than the cost of the IT involvement that would have prevented it.
Cost 2: Failed transformations. The most expensive consequence of the IT support framing is digital transformation failure. When the CIO is not present at the strategy table when a transformation is planned, the technology constraints and capabilities that should shape the plan are not surfaced. The result is a transformation built on assumptions about what technology can do that turn out to be wrong — discovered at implementation, when the cost of revision is high.
:::inset McKinsey estimates that 70% of large-scale transformation programs fail to meet their objectives. A disproportionate number of those failures trace to misalignment between business strategy and technology capability — a misalignment that CIO exclusion from strategy-setting makes inevitable. :::
Cost 3: Shadow IT proliferation. When the business experience of IT is slow, expensive, and bureaucratic, business units find alternatives. They purchase SaaS tools on corporate cards. They engage boutique consultants for technology projects. They build capabilities in Excel or low-code platforms that become unmaintainable. Shadow IT is not just a security and compliance problem — it is evidence of a failed relationship between IT and the business, and it reinforces the perception that IT is an obstacle rather than a partner.
Cost 4: Talent drain from IT. High-performing technology professionals want to work on meaningful problems. When IT is positioned as a support function, the work is reactive, the career ceiling is low, and the interesting technology work happens on the business side — in digital teams, data teams, and innovation labs that sit outside IT. The CIO who cannot attract and retain strong technologists cannot build the capability to escape the support framing. The trap is self-reinforcing.
Recognizing the Signs in Your Own Organization
:::comparisonTable
| Signal | Support-Framed CIO | Strategic CIO |
|---|---|---|
| When IT is involved in major initiatives | After vendor selection | During problem definition |
| Primary executive relationship | CFO (budget negotiation) | CEO + peers (strategy alignment) |
| IT budget framing | Cost to minimize | Investment to optimize |
| CIO meeting invitations | Project reviews, operational updates | Strategy sessions, board preparation |
| How peers describe IT | "Our IT team handles that" | "We work with IT on..." |
| CIO's primary communication | Status reports, uptime metrics | Business outcome narratives |
| Shadow IT level | High and growing | Low and declining |
| ::: |
Most CIOs reading this table will recognize their organization somewhere in the middle — not pure support framing, but not fully strategic positioning either. The gradient matters: each signal is an opportunity for repositioning, and repositioning on multiple signals simultaneously produces faster perception change than working on any one in isolation.
The Conversation That Reveals Everything
There is a single conversation that reveals a CIO's organizational positioning more clearly than any org chart or job description. It is the conversation a peer executive has about the CIO when the CIO is not in the room.
:::pullQuote "When the CFO and COO are discussing next year's strategy and one of them says 'we should loop in [CIO] on the technology side' — that is the support framing. When one of them says 'this is a capability question; we need [CIO] to co-own this' — that is strategic positioning." :::
CIOs who want to understand their actual positioning should ask: what conversations am I not being invited to? The absence is more revealing than the presence. Every strategy conversation, M&A discussion, or major operational decision that proceeds without CIO input is a data point about how the organization has categorized the role.
What CEOs Think (But Rarely Say Directly)
:::callout What CEOs think when CIOs operate in support mode:
- "I need someone who brings me solutions, not updates"
- "If I wanted an IT status report, I'd read the dashboard"
- "Why is every technology conversation about cost and risk rather than opportunity?"
- "My peers in other companies have CIOs who are genuinely co-owning strategy. Mine is managing vendors."
- "I'm not sure technology is a strategic advantage for us — it feels more like maintenance" :::
These thoughts — rarely spoken directly, frequently present — create the ceiling on CIO influence. The CIO who doesn't know this ceiling exists cannot address it. The one who recognizes it can begin to dismantle it.
Escaping the Framing: The First Moves
Escaping the support framing is not a single bold action. It is a series of consistent moves that gradually shift what peers expect from the CIO.
Stop leading with technology. In every executive conversation, start with the business problem. "Our customer retention is declining in the 25–34 segment" is a business observation. "We need to upgrade our CRM" is a technology request. The CIO who consistently leads with the business problem signals that they think like a business leader, not a technologist serving business leaders.
Claim accountability for business outcomes. When an IT initiative is being discussed, volunteer accountability for the business outcome it is designed to achieve — not just for the technology delivery. "I want to own the customer retention improvement metric, not just the CRM implementation" repositions the CIO as a business co-owner.
Build peer relationships outside the IT context. The CIO who only interacts with the CFO about budget and with other executives at project reviews is forever associated with those contexts. Schedule conversations with the CMO about growth strategy, with the COO about operational efficiency, with the Chief Revenue Officer about customer experience — conversations where technology is one input, not the primary agenda.
The detailed playbook for each of these moves fills the rest of this series. The next article begins the reframing: from technology leader to business architect.
Next: From Technology Leader to Business Architect
Previous: Why CIOs Are Still Not at the Strategy Table
Related reading: Managing Stakeholders Across the C-Suite · Measuring What Matters: KPIs for Strategic CIOs