The Structure Where Only Cost Reduction is Valued

Introduction

In many companies, the evaluation of the Information Systems department (IT) tends to be summarized in a single phrase: “How much did you reduce costs in the end?” Stable system operation is taken for granted, and any achievements discussed beyond that are skewed toward cost reduction—cutting license fees, compressing vendor costs, and suppressing personnel expenses. This article organizes why IT has come to be evaluated solely on “cost reduction,” not as a matter of capability or attitude, but as a structural problem of management decisions and authority design.

An Organization Without Investment Decision-Making Power Can Only Be Discussed in Terms of Cost

First, there is a fundamental premise to understand. An organization that lacks investment decision-making authority cannot discuss its results in terms of investment returns (ROI). Many IT departments do not hold final approval authority for IT investments, cannot participate in comparative judgments against business investments, and are not in a position to set investment objectives. In this state, the results IT can discuss are limited to the scope of expenditure management: “It operated as planned,” “We avoided incidents,” or “We completed it for less than estimated.”

Management Has Not Defined IT as an “Investment Target”

The root cause of this structure lies in the fact that management has not clearly defined IT as a “business investment,” “growth investment,” or “competitiveness investment.” For a long time, IT has been treated as a “necessary cost that does not directly generate profit.” Under this definition, the question management poses to IT focuses on a single point: “Why does this cost so much?” As long as there is no question of purpose—”What do we want to gain from this investment?”—evaluation inevitably converges on “How much (cost) were you able to reduce?”

It’s Not That ROI Can’t Be Calculated; It’s That the Design to Calculate It Was Never Created

It is often said that “IT’s ROI (Return on Investment) is difficult to measure,” but the reality is different. The problem is that investment objectives are not defined, what to optimize is not decided, and the axis for measuring results is not designed from the outset. In this state, it’s natural that ROI cannot be produced. It is not a case of “we don’t evaluate because we can’t measure,” but rather the result of “designing on the premise that we wouldn’t evaluate.” Consequently, the only comparable and common language left was the metric of “cost.”

Cost-Based Evaluation Locks Actions into a “Defensive” Posture

Evaluation metrics determine people’s actions. As long as cost reduction is the primary evaluation criterion, the rational actions of the IT department become the following:

• Avoid new investments
• Postpone medium- to long-term improvements
• Focus on price negotiations
• Become cautious about in-house development and system modernization

This is not passivity; it is merely optimally selecting the actions most valued within the given evaluation design. Within this structure, demanding “Drive DX (Digital Transformation)” or “Take on offensive IT” creates a clear contradiction with the evaluation design itself.

As Long as Cost-Reduction Evaluation Continues, the Role Will Not Change

The important point is that cost management itself is not the problem. The issue is that there is no evaluation as an investment, no metrics for value creation are designed, and as a result, cost reduction becomes the sole performance indicator. If management had defined IT as a “device to increase business reproducibility,” a “platform to extend decision-making,” or a “preemptive investment to reduce future costs,” there would have been multiple axes for evaluation.

Conclusion

The “structure where only cost reduction is valued” is not a problem of the IT department’s attitude or capability. It is the consequence of management decisions that did not grant investment decision-making authority and, fundamentally, did not treat IT as an “investment.” If you want to change this evaluation, what is needed is not minor budget adjustments, empty slogans about DX, or requests for effort from the front lines. It is for management itself to take ownership of a fundamental redefinition: to regard IT not merely as a “cost,” but as “an investment in what.” Unless this single point changes, IT will rationally remain the “cost reduction role.”