An IT manager reporting to a CFO, COO, executive director, or another nontechnical executive is not inherently a problem.
The arrangement may have been practical when it was created. Technology needed a place in the organization. Its visible responsibilities centered on devices, systems, support, contracts, budgets, and keeping operations available. Finance or operations provided executive supervision, while an IT manager or external provider handled the technical work.
Both sides may still be performing those roles well.
The risk appears when the responsibilities change but the leadership model does not. Technology begins shaping customer experience, data, cybersecurity, automation, workforce capacity, strategic partnerships, and nearly every major initiative. The operational team is asked to make recommendations with enterprise consequences. Its supervising executive is asked to approve decisions without an independent technology perspective for evaluating them.
At that point, the problem is not that the people are incapable. The structure is asking capable people to collectively cover a leadership function that neither role was designed to provide.
The structure may have made sense when it was created
Reporting lines are often the history of an organization written as a chart.
Technology may report to finance because technology spending once represented the most visible concern. It may report to operations because reliability and support were the priority. It may sit within administration because the organization was small and no separate executive role was justified.
Those choices can remain appropriate for years. A direct report to the CEO is not a universal requirement, and adding an executive title does not automatically produce better judgment.
What leadership should examine is whether the nature of the decisions has changed.
A request to replace laptops is not the same as deciding whether the organization can support a new operating model. Renewing a software contract is not the same as assessing how vendor concentration could affect resilience and negotiating power. Maintaining a database is not the same as determining who owns enterprise data or whether it can support reliable reporting and AI.
The reporting structure becomes strained when the decisions passing through it become broader than the perspective, authority, or access available within it.
Operational responsibility is not executive technology leadership
An effective operational technology leader understands the environment in detail. That person may know which systems are fragile, where support demand is growing, how vendors are performing, which controls require attention, and what the team can realistically deliver.
Executive technology leadership asks a related but different set of questions.
It connects the organization’s direction to its technology capacity. It weighs immediate need against lifecycle cost, integration, risk, data, talent, adoption, and future flexibility. It challenges whether a proposed solution addresses the business problem or simply makes one department’s work easier. It explains technical constraints as executive choices rather than isolated technical requests.
Some IT managers already possess much of this judgment. The issue is whether the organization gives them the mandate, context, access, and authority to exercise it. Asking an operational leader to carry executive accountability informally can create responsibility without the ability to shape the decisions that produce the outcome.
It can also leave the supervising executive in an unfair position. A CFO or COO may be an accomplished leader and still lack an independent way to test architectural claims, evaluate cybersecurity tradeoffs, assess a vendor’s proposed roadmap, or determine whether the current team and operating model can support a strategic plan.
Competence on both sides does not eliminate a missing capability between them.
Important information can lose meaning as it travels upward
Operational teams often see risk early. They know when a system is becoming difficult to support, when one employee holds too much critical knowledge, when integrations are unusually fragile, or when a vendor’s proposal introduces dependencies that will be expensive to reverse.
Those conditions do not always arrive in leadership discussions as business decisions.
A structural constraint may become a request for additional budget. A data-ownership problem may be described as a reporting defect. An unsustainable workload may appear as a temporary backlog. A cybersecurity exposure may be translated into a product purchase without a broader discussion of risk, process, and accountability.
The supervising executive receives technically accurate information but may not receive the context needed to compare it with other organizational priorities. The IT leader understands the context but may not be present when strategy, capital, staffing, and risk decisions are formed.
Nothing is necessarily concealed. Meaning is lost through the distance between the technical evidence and the executive decision.
This is why late involvement is so expensive. Once a vendor has been selected, a timeline announced, or a department committed to a preferred answer, technology is no longer being asked what the organization should do. It is being asked how to make an existing decision work.
Operational gravity usually wins
The most visible technology work is immediate.
People need access. Systems require maintenance. Incidents interrupt operations. Contracts expire. Projects reach deadlines. These needs are legitimate, measurable, and difficult to postpone.
Strategic work is easier to defer. Architecture, capability planning, data governance, succession, modernization sequencing, policy, and vendor strategy rarely create the same daily pressure. Their consequences emerge over time and often become visible only when the organization tries to change.
An IT manager carrying both operational delivery and informal executive leadership will naturally protect the work that keeps the organization functioning today. A nontechnical executive with several other functions to oversee will often engage most deeply when an approval, incident, or budget issue demands attention.
The resulting technology strategy can become a collection of urgent requests rather than an intentional view of what the organization needs, what it can sustain, and what it should decline.
That pattern is not evidence of laziness or weak leadership. It is what the structure is designed to produce.
Vendors can begin supplying the missing judgment
Vendors often become trusted partners because they bring expertise the organization does not maintain internally. That can be valuable.
It can also create a subtle shift. The provider that operates the environment, implements the platform, or sells the service may become the primary source of advice about what the organization needs next.
The vendor understands its product and delivery model. It may understand parts of the organization very well. It is still not accountable for balancing the full technology portfolio, internal capacity, long-term flexibility, competing business priorities, and the option of reducing or ending the commercial relationship.
As discussed in Ronin’s examination of vendor consolidation and concentration risk, a strong provider relationship can simplify operations while also increasing dependency. The concern is not vendor dishonesty. It is the absence of an informed party on the organization’s side of the table whose incentives are aligned only with the organization’s decisions.
When the leadership gap is not filled deliberately, commercial partners may fill it by default.
The answer is not always a new box on the chart
Current research reflects the increasing strategic role of technology leadership. Deloitte’s 2025 Tech Exec Survey reported that 80 percent of technology executives believed their responsibilities had expanded significantly to meet business objectives. Sixty-five percent of CIO respondents reported directly to the CEO, and most within that group said the relationship positioned them better to shape strategy and results.
McKinsey’s 2026 Global Tech Agenda found a similar association. Nearly two-thirds of top-performing organizations in its survey said technology leaders were deeply involved in enterprise strategy, compared with 52 percent of other organizations. Top performers were also more likely to develop business and technology plans continuously rather than joining them only during an annual planning cycle.
Those findings do not establish that every organization should hire a full-time CIO or have technology report directly to the CEO. The studies primarily represent larger organizations, and the relationships are correlations rather than proof that an org-chart change causes performance.
They do reinforce a more durable point: technology creates more value when technology judgment can influence business direction while choices remain open.
An organization might provide that capability through a permanent executive, a fractional or interim leader, an independent advisor, clearer decision rights, or a formal cadence that brings technology into leadership discussions. The appropriate model depends on the decisions, risk, pace of change, and internal capability involved.
Evaluate the capability, not only the title
The useful question is not whether the IT manager reports to the correct executive.
It is whether the organization has a credible way to connect technology operations with enterprise strategy, investment, risk, data, vendors, people, and change.
Who tests the assumptions behind major proposals? Who can explain where the strategic plan depends on capabilities the organization does not yet have? Who represents technology risk in business terms before it becomes an incident? Who can challenge a vendor recommendation without being responsible for selling or delivering the alternative? Who ensures operational staff are not carrying executive accountability without executive authority?
Ronin has previously examined why an organization can make CIO-level decisions without maintaining a CIO role. The reporting structure is where that broader issue often becomes visible in day-to-day work.
The current structure may still be reasonable. But when technical responsibility expands beyond operations, leadership should decide intentionally how executive technology judgment will enter the organization.
Otherwise, the gap does not remain empty. It is filled by urgency, habit, and whoever is closest to the next decision.