The Decision-Making Void in Japanese Corporate IT

Introduction

In many Japanese companies, a chronic and normalized condition persists: despite the constant presence of IT-related meetings, investments, and projects, it remains difficult to clearly explain “who ultimately makes the decisions.” This article frames the unique void in IT decision-making within Japanese firms—how it emerges and its consequences—not as an issue of people or capability, but as a problem of “decision-making structure.”

The Illusion of Decision-Making

At first glance, IT decisions appear to be made in many forums. Approval requests circulate, reports are made to the board, and daily judgments are made on the ground. However, upon closer inspection, a lack of a final decision-maker is not uncommon. IT projects often proceed without a clear entity that can definitively answer questions such as: “Why are we investing in this IT?” “What constitutes success?” and “If it fails, what criteria define withdrawal?”

The Disconnect Between “Operational Judgment” and “Management Judgment”

In Japanese companies, IT-related judgments tend to be fragmented as follows: frontline staff choose practical solutions to keep operations running, administrative departments prioritize rules and control, and management provides broad approval without delving into details. While each acts rationally, no one determines the overall optimal solution. Consequently, this leads to a layering of localized optimizations, a series of ex-post-facto approvals, and decisions whose rationale is not preserved.

The “Subjectless Decision” Created by Approval Processes and Committees

In Japanese firms, approval requests and committees are often placed at the center of IT decision-making. In principle, these should be mechanisms to support decision-making. In reality, however, priorities often shift to “no one objecting,” “not deviating significantly from precedent,” and “being able to disperse responsibility,” diluting the act of decision-making itself. The result is the creation of a “subjectless decision”—a decision that is made, but with the “who” behind it remaining ambiguous.

Why IT is Treated as an Exception

For many management decisions—such as business withdrawal, investment choices, or organizational restructuring—the ultimate responsible party is clear. IT, however, has historically been treated as an exceptional area with ambiguous accountability, often justified by its “high specialization,” “technical difficulty,” and “uncertain future.” As a result, IT has been placed outside the formal decision-making structure, becoming a domain that “progresses even without clear decisions.”

Typical Symptoms Created by the Void

Within the void of IT decision-making, the following phenomena repeatedly occur:

• Decisions are delayed, forcing reliance on makeshift frontline solutions.
• The rationale for investments is only discussed after the fact.
• Neither successes nor failures can be replicated.
• Systems and structures are rebuilt every time a problem arises.

These are not due to the competence of individual projects but are the inevitable outcomes of a structure lacking a clear decision-making authority.

Why Has the Void Not Been Filled?

The void in IT decision-making did not arise because “someone was negligent.” It formed through the accumulation of factors: management not treating IT as a primary subject, not engaging deeply due to its perceived specialization, and the blurry line between delegation and neglect. This created a no-man’s-land where no one could effectively step in.

The Necessary Perspective Moving Forward

Filling this void does not require new positions or committees. What is needed first is to redefine IT as a “management subject requiring decisions” and to clarify which judgments management will own. In the next article, we will delve into why IT has disappeared from management meeting agendas and examine how this void became institutionalized.