Why CIOs Are Still Not at the Strategy Table
There is a persistent paradox at the top of most large enterprises. Technology is now the primary engine of competitive differentiation, operational resilience, and customer experience. And yet the person responsible for technology — the CIO — is frequently absent from the conversations where the company's direction is set.
Not absent from the room. Absent from the decision.
:::kicker Module 1: The Influence Gap · Article 1 of 14 :::
This is the starting point of the series: an honest diagnosis of why the influence gap exists, what sustains it, and what it costs the organizations that live with it. The prescription comes in the articles that follow. But the diagnosis has to come first — because CIOs who don't understand why they lack influence tend to pursue remedies that don't address the actual problem.
The Gap Is Structural, Not Personal
The most common explanation CIOs give for their limited strategic influence is a political one: "The CEO doesn't value technology," or "The CFO controls the agenda." These explanations locate the problem in other people. They are almost always incomplete.
The more accurate explanation is structural. The CIO role, as it was designed and as it typically operates, creates the conditions for its own marginalization.
:::inset In 2024, only 34% of CIOs reported directly to the CEO. The majority report to the CFO or COO — a structural positioning that signals "operational function" rather than "strategic partner" before the CIO has said a word in any executive meeting. :::
The structural issues compound each other:
Reporting line. A CIO who reports to the CFO is, organizationally, two levels removed from strategy. Their agenda is filtered through a finance lens. Their priorities are framed around cost and risk. The conversations they are invited to are operational, not strategic.
Role definition. Most CIO job descriptions are centered on delivery: systems reliability, project execution, vendor management, security. These are legitimate responsibilities. They are also entirely reactive — defined by what the business asks of IT, not by what IT could offer the business if positioned differently.
Performance metrics. If a CIO is measured on uptime, ticket resolution time, and project on-time delivery, those are the things they will optimize for. And when they walk into an executive conversation, those are the metrics they will lead with — metrics that are invisible to the business unless they fail.
Budget framing. When IT appears in the P&L as a cost center, the default conversation about IT is "how do we reduce this?" A CIO defending a budget in a cost-center frame is always playing defense. The strategic question — "what does this investment enable?" — never gets asked because the framing doesn't invite it.
The Perception Problem
Beyond structure, there is a perception problem that compounds the structural one. Business leaders have spent decades experiencing IT as a bottleneck — slow to deliver, expensive to maintain, prone to scope creep, and reliably unable to explain its own value in terms the business cares about.
These experiences create a prior: technology is a complicated necessity, best managed by specialists and kept as far as possible from strategy conversations where it might slow things down or complicate decisions with technical objections.
:::pullQuote "The CIO's most persistent credibility challenge is not what technology can do. It is what their predecessors failed to deliver — and the scar tissue that left on the business." :::
This prior is unfair to the CIO who has inherited it. It is also real. Ignoring it doesn't make it go away. The CIOs who build influence understand that they are not just selling a vision of technology's strategic potential — they are also overcoming a specific history of disappointment that their peers carry into every room.
What CEOs Actually Want from CIOs
Understanding the gap requires understanding what the CEO — the person whose judgment of the CIO ultimately determines their strategic standing — actually wants.
:::callout What CEOs expect from strategic CIOs:
- A clear line from technology investment to business outcome
- Fewer surprises (in cost, timeline, and risk)
- Technology that accelerates the company's competitive position — not just maintains it
- A peer who speaks about business problems first and technology second
- Someone who can say "no" to low-value technology spending with the same conviction they say "yes" to high-value opportunities :::
The gap between what CEOs want and what they experience is not usually a capability gap. Most CIOs are capable of delivering on these expectations. The gap is a communication and framing gap — one that this series is designed to close.
The Cost of the Gap
The influence gap is not just a CIO career problem. It is an enterprise performance problem.
When technology decisions are made without CIO input at the strategic level, the consequences show up in predictable ways: enterprise software acquisitions that don't integrate with existing systems; digital transformation programs that fail because they weren't designed for the organization's actual capability; AI initiatives that die in pilot because nobody addressed the data infrastructure problem the CIO knew about.
:::didYouKnow Gartner research found that organizations where the CIO has a direct seat in strategy-setting are significantly more likely to report successful digital transformation outcomes — not because the CIO is the transformation leader, but because technology constraints and opportunities are surfaced before strategic commitments are made. :::
The organizations that pay the highest price for the influence gap are not the ones where the CIO has no voice. They are the ones where the CIO has enough presence to be informed but not enough influence to redirect — where they can see the strategy-technology mismatch coming and cannot stop it.
Three Traps That Keep CIOs Stuck
Most CIOs experiencing the influence gap are caught in one or more of three traps. Naming them is the first step toward escaping them.
Trap 1: The Expert Trap. The CIO becomes the organization's most knowledgeable person about technology — and defaults to demonstrating that expertise in every conversation. The result is that peers come to see the CIO as a technical resource, not a strategic peer. Expertise is necessary but insufficient. It becomes a trap when it substitutes for business judgment rather than complementing it.
Trap 2: The Service Trap. The CIO defines success as satisfying the business's technology requests. Every conversation begins with "what do you need?" rather than "here is what I think we should be doing." A CIO in the service trap is permanently reactive. They cannot lead because they have positioned themselves as followers.
Trap 3: The Proof Trap. The CIO is perpetually trying to prove IT's value — publishing dashboards of uptime metrics, celebrating project completions, sending quarterly "look what we accomplished" communications to the business. The effort is real, but it is directed at the wrong audience using the wrong currency. Uptime metrics don't make business leaders feel strategic confidence in their CIO. Business outcomes do.
The Path Forward
The articles in this series address each dimension of the influence gap — structural, perceptual, and behavioral — with specific, actionable frameworks for CIOs who are ready to change their positioning.
The progression is deliberate:
- Diagnose the specific form the gap takes in your organization (this article and the next)
- Reframe the role from technology leader to business architect (Articles 3–4)
- Build credibility with business peers by speaking their language (Articles 5–6)
- Deliver visible impact that registers with executive audiences (Articles 7–8)
- Execute strategically and manage upward with skill (Articles 9–10)
- Lead organizationally in ways that compound your influence (Articles 11–12)
- Sustain and measure influence over time (Articles 13–14)
The influence gap is not inevitable. It is a condition — one that is sustained by structural defaults, reinforced by perception patterns, and maintained by CIO behaviors that, with intention, can change.
The next article examines the specific cost of being framed as "IT support" — and how that framing shapes every interaction a CIO has with the rest of the executive team.
Next: The Cost of Being Seen as IT Support
Related reading: Building an AI-Ready Organization · What Enterprise AI Actually Means