Executives do not struggle with IT because they do not understand technology.
They struggle because they have delegated decisions they should never have delegated in the first place.
The frustration is familiar. Technology costs keep rising. Capabilities expand. Programs consume time and attention. And yet, the business impact remains unclear or disappointing. Systems go live, but the expected value does not materialize.
At some point, the narrative settles into a convenient explanation. IT is too complex. IT does not understand the business. IT needs to perform better.
That narrative is comfortable.
And wrong.
Large-scale technology initiatives rarely fail because of technical shortcomings. They fail because the decisions that define their value are treated as technical decisions, when they are in fact business decisions.
Once those decisions are handed over to IT, the outcome is largely predetermined.
The first of these decisions is spending.
Most organizations approach IT budgets as a benchmarking exercise. What do others spend? What is “reasonable”? The assumption is that if the number is right, the rest will follow.
But spending is not a number. It is a reflection of intent.
What role should technology play in your business? Is it a support function that streamlines operations? Is it a differentiator that shapes customer experience? Is it the backbone of a global delivery model? Each of these choices implies a fundamentally different level of investment and a different tolerance for risk.
If executives do not define that role, IT will fill the gap with implicit assumptions.
The second decision is prioritization.
Most organizations do not suffer from a lack of ideas. They suffer from a lack of choice.
It is not uncommon to see dozens, sometimes hundreds, of initiatives running in parallel. All approved. All funded. All considered important. When everything is a priority, nothing is. IT becomes the function that absorbs this contradiction and attempts to deliver against it.
The result is predictable. Delays, diluted focus, and teams that are stretched across too many initiatives to deliver any of them well.
Prioritization is not a technical exercise. It is a business decision about where the organization is willing to win and where it is willing to accept compromise.
The third decision is standardization.
Centralization and standardization promise efficiency, scale, and control. They also reduce flexibility and create friction with local needs. The balance between the two is one of the most consequential choices an organization makes.
Left to IT, this balance tends to drift to extremes. Either everything is standardized in the name of efficiency, constraining the business, or exceptions are granted continuously, eroding the very benefits standardization was meant to create.
This is not a technical trade-off. It is a strategic one.
The same pattern repeats in operations.
Service levels, for example, are often defined as technical targets. Uptime, response time, recovery objectives. But behind each of these metrics sits a business question. How much disruption can the business tolerate? What is the cost of downtime versus the cost of preventing it?
Left alone, IT will rationally optimize for stability. High availability, minimal risk, maximum control. In many cases, that leads to over-engineered solutions. Ferrari-level service where a Ford would do. The cost is real, but it is rarely challenged because the underlying trade-off has not been made explicit.
Security follows the same logic.
Absolute security is an attractive goal from a technical perspective. From a business perspective, it introduces cost, complexity, and often friction for users and customers. Every additional control has an impact on usability and speed. The right level of security is not the maximum possible. It is the level that aligns with the organization’s risk appetite and business model.
That decision cannot be delegated.
And then there is accountability.
When technology programs fail to deliver value, the instinct is to look at IT. Something must have gone wrong in delivery. But in most cases, the deeper issue lies elsewhere.
Systems do not create value on their own. They enable new ways of working. If business processes are not redesigned, if behaviors do not change, if adoption is weak, the system remains an expensive layer on top of old practices.
Expecting IT or external partners to drive that change while the business continues as usual is one of the most persistent and costly assumptions in large organizations.
Value realization requires ownership.
It requires business executives who are willing to act as true sponsors. Not in name, but in practice. Assigning resources. Making trade-offs. Defining success. Staying engaged beyond the approval of the business case.
Without that ownership, the organization creates a structural gap.
IT is accountable for delivery, but not empowered to make business decisions. The business expects outcomes, but is not accountable for the conditions required to achieve them.
That gap is where most value is lost.
In simple terms: the question is not whether IT understands the business well enough.
The question is whether the business is willing to take responsibility for the decisions that determine the value of its technology investments.