- The Management Challenge Beyond Criticizing IT Departments
- Standardization is a Means to Support the Business
- Unmeasurable Outcomes are Replaced by Means
- Easily Explained Standardization Becomes the Outcome
- Rational Actions Stiffen the Organization
- The Role of IT that Management Fails to Define
- Concrete Actions for Executives and CTOs
The Management Challenge Beyond Criticizing IT Departments
IT departments are often criticized for being “inflexible.” However, this is not a matter of individual capability. It is an inevitable outcome created by the organization’s evaluation design. The disconnect between management and IT begins here.
Standardization is a Means to Support the Business
The original purpose of standardization is clear: to reduce operational costs and lower the risk of failures. Eliminating dependency on specific individuals and improving resilience to change are also goals. All of these are means to stabilize business outcomes.
Unmeasurable Outcomes are Replaced by Means
An organization cannot evaluate outcomes it cannot measure. Historically, the evaluation criteria for IT have been overwhelmingly restrictive. The focus has been on avoiding failures and not increasing costs. The degree of contribution to the business has not been part of the evaluation framework.
Easily Explained Standardization Becomes the Outcome
Metrics that are easy to explain to management are chosen. Standardization is clear-cut—it’s easy to quantify whether rules are “being followed.” Evaluating the value IT brings to the business is difficult. As a result, standardization itself comes to be seen as the achievement.
Rational Actions Stiffen the Organization
If the only evaluation criterion is standardization, actions converge. It becomes rational to refuse exceptions and reject local optimizations. New technologies are also excluded as non-standard. This is a faithful response to the given evaluation criteria.
The Role of IT that Management Fails to Define
The problem is not standardization itself. It’s that the purpose of standardization is not defined. Management has failed to define IT as a growth engine. Consequently, the design of what should be standardized goes wrong.
Concrete Actions for Executives and CTOs
First, management must articulate the purpose of IT investment. The CTO should propose evaluation metrics for business contribution. The IT department must agree with management on the scope of standardization. This will repair the disconnect between IT and management.


Comments