Who Should Put the Brakes on Business-Enabling IT?

Introduction

Business-enabling IT (the implementation of IT systems and SaaS to accelerate business growth) is introduced to enhance frontline productivity and seize market opportunities. However, as seen in Chapter III, it can create labor shortages, accumulate technical debt, lead to tool sprawl and knowledge silos, and ultimately cause a disconnect between operations and management. This article reframes the question of “who should have stopped this business-enabling IT, and where?” not as a matter of individual or departmental blame, but as a problem of decision-making structure.

The Frontline Cannot Stop It

The frontline is always the first to initiate business-enabling IT. In situations where immediate results are needed, customer service cannot be paused, and falling behind competitors is not an option, making judgments like “let’s pause for a moment” or “let’s reconsider the design” is impossible. For the frontline, the decision to stop is akin to abandoning the business.

The IT Department Lacks the Authority to Stop It

The IT department is aware of technical risks, operational limits, and future liabilities. However, in many cases, it lacks the authority to halt business initiatives, cannot make final investment decisions, and does not bear ultimate responsibility. Therefore, its role is often limited to raising warnings, making improvement suggestions, and establishing guidelines. The IT department’s inability to stop projects is not a lack of capability but a problem of role design.

BizOps Cannot Stop It Either

BizOps (Business Operations) functions as a bridge between business and IT, accelerating decision-making and absorbing chaos. However, BizOps does not make decisions on behalf of others nor holds the final decision-making authority, so it cannot make the call to stop. If BizOps were to stop things, business operations would stall, the organization would fall into chaos, and BizOps would ironically be held accountable.

Vendors Are Not in a Position to Stop It

External vendors are in the position to build what is requested and fulfill responsibilities within the contract scope. They are not entities that take on business strategy, organizational design, or long-term management judgment. Expecting a vendor to make the decision to stop is itself a misplacement of responsibility.

Only “Management” Can Stop It

The conclusion drawn from the analysis so far is singular. Only management can stop business-enabling IT. This is because decisions to slow growth, sacrifice short-term results, or spend time on design are all trade-offs made against the overall risk to the business. Only management can assume responsibility for this trade-off.

“Stopping” Does Not Mean Quitting

Here, “stopping” does not mean canceling IT implementation or suppressing frontline activity. It refers to the act of applying a design brake: “switching phases,” “updating the objective function,” or “separating roles.”

Why the Decision to Stop Was Not Made

The reason management in many companies failed to make the decision to stop is clear. The business was growing, numbers were positive, and problems were not yet visible, leading to repeated judgments like “it’s not bad enough to stop yet” or “we’ll think about it in the next phase.” However, the timing to stop inherently only arrives while problems are still small.

What Was Needed as a Management Decision

What management should have done from the outset was to decide on the following three points in advance:

• How long is the experimental phase?
• At what point do we switch to a foundational system?
• Who declares that switch?

The decision to stop has the characteristic of being too late if made after problems arise; it can only be made while things are still successful.

Conclusion of Chapter III

Business-enabling IT did not fail because it wasn’t stopped. The problem was that no one assumed the responsibility for making the decision to stop. In the next chapter, based on this structural premise, we will address why the Information Systems department became confined to “defensive IT” and shift our perspective from the business layer to the operational layer.