Treating IT as a Decision-Making Apparatus: A New Perspective

Introduction

In Chapter II, we organized the key questions: what IT was supposed to optimize, why growth speed, reproducibility, and stability became misaligned, why IT investments failed to show ROI, and the false dichotomy of “Is IT a management resource or an expense?” When these are tied together with a single axis, we arrive at one conclusion. It is the perspective of treating IT as an “apparatus for making decisions.” This article organizes the perspective of viewing IT not merely as a tool or a resource, but as an “apparatus” that formalizes and reproduces management judgment.

What is a Decision-Making Apparatus?

A decision-making apparatus is a mechanism that formalizes the process of “who makes a decision, based on what information, from which options, and by what criteria” into a structure. Fundamentally, companies operate based on human judgment. IT is the apparatus to make that judgment “faster,” “more consistent,” and “repeatable.”

The Moment IT is Treated as Just a Tool

When IT is treated merely as a tool, the focus shifts to points like “what it can do,” “which is more convenient,” or “which product is superior.” From this perspective, the most critical questions—”who decides?” and “by what criteria is judgment made?”—are left behind. As a result, IT is diminished from being a substitute for decision-making to a tool for streamlining post-judgment tasks.

IT Should Have Been Positioned “Before” the Judgment

Originally, where IT should have been positioned was not after execution, but “before” the judgment. It is precisely at the stage of deciding “what information to look at,” “what to compare it against,” and “where to stop” that IT demonstrates its true value. In other words, IT is an apparatus for designing the preconditions of management judgment.

Why Wasn’t IT Treated as a Decision-Making Apparatus?

The reason IT wasn’t treated as a decision-making apparatus lies in the assumptions of Japanese-style management. Because judgment was performed on a personal basis, managed through on-site adjustments, and wasn’t a problem while successful, the necessity to formalize judgment into a structure never became apparent. Consequently, IT was not designed as an apparatus to formalize judgment.

The Value Created by Treating IT as a Decision-Making Apparatus

When IT is treated as a decision-making apparatus, the evaluation criteria change significantly.

• Not processing speed, but decision speed
• Not usability, but decision consistency
• Not the number of features, but decision reproducibility

From this perspective, the value of IT investment comes to be evaluated based on “how quickly can decisions be made” and “how consistently can the same decision be repeated.”

Why ROI Becomes Explainable

When IT is viewed as a decision-making apparatus, the previously inexplicable ROI (Return on Investment) becomes visible in a different form. Decisions become faster, judgment errors decrease, and decision criteria become aligned. Even if these don’t directly link to sales, they reliably reduce wasted investment, rework, and organizational friction. The issue wasn’t a lack of ROI, but a misunderstanding of what the return should be measured against.

What is Needed to Treat IT as a Decision-Making Apparatus

What is needed to implement this perspective is not new tools (like SaaS). What is needed is for management to define the following points:

• Which judgments will be entrusted to IT?
• Which judgments will people continue to hold?
• Who has the authority to change a judgment?

As a Summary of Chapter II

What became clear throughout Chapter II is not the failure of IT itself. It is that management did not adopt IT as a “decision-making apparatus.” By standing on this perspective, the misalignment of objectives, the absence of ROI, and the confusion in investment decisions can all be explained as a single problem. In the next chapter, we will examine from the business layer how this IT-as-decision-apparatus becomes distorted in the field of business execution and why business IT tends to run out of control.