The True Responsible Party for IT Department Issues

Introduction

Discussions surrounding the Information Systems (IS) department often conclude with criticisms directed at the front lines, such as “lack of skills,” “weak business understanding,” “being too defensive,” or “absence of a transformation mindset.” Yet, the problems persist. This article analyzes this recurring pattern and clarifies the true responsible party for IS issues—not by criticizing individuals or departments, but from the perspective of management decisions and organizational design.

Why Do IS Issues Always Become “Problems with the Front Line”?

When IS-related problems are raised, the conversation tends to converge on solutions like “talent development,” “mindset change,” or “skill enhancement.” This is not because the IS department is uniquely problematic. Unless the locus of responsibility is placed on “structure” or “decision-making processes,” problems will inevitably be attributed to the visible “individuals” or “front line.” Discussing problems without questioning the structure leaves only the daily-operating front line as an explainable target.

The IS Department Is Not the “Party That Chose Not to Decide”

In many cases, the IS department has operated without the authority to define the purpose of IT investments or to make investment decisions and set priorities. Under these conditions, the only possible role is “operations”—running what has been decided upon stably and without incident. In other words, the IS department is not a party that abdicated its judgment; it is a party that was never given the role and authority to “decide” by management in the first place.

Who Should Have Been “Deciding” About IT All Along?

We need to reframe the question. “What is the purpose of using IT?” “What should we optimize, where should we invest, and what should we discard?” “How do we decide priorities between departments?” These are all quintessential management decisions. No matter how specialized IT is, the party responsible for determining its purpose and strategic priority cannot be anyone other than management.

What the Phrase “We Left It to Them” Conceals

Management sometimes explains, “We left it to the experts” or “We entrusted it to the IS department.” However, this statement lacks a crucial premise. “Leaving it to someone” without providing a clear purpose, decision-making criteria, and authority as a set is not true delegation; it is an abdication of decision-making. True delegation means defining the purpose, clarifying the criteria for judgment, and transferring both authority and responsibility as a package.

Why Didn’t Responsibility Return to Management?

So why, even as problems accumulated, did the locus of responsibility not revert to management? The reason is clear. Under perceptions that “IT is specialized and difficult,” “doesn’t directly generate sales,” and “failures are rarely immediately fatal,” IT continued to be treated as an area management didn’t need to confront directly. As a result, a cycle emerged where the IS department, vendors, and the front line bore the brunt of responsibility whenever problems arose, while the management structure itself remained preserved.

As Long as We Misidentify the Responsible Party, Problems Will Be Recreated

As long as attempts to solve IS problems rely on measures like “organizational restructuring,” “talent reinforcement,” or “tool modernization,” the outcome will not change. These are all merely applying symptomatic treatments to places that are not the true source of responsibility. Unless the locus of responsibility is correctly placed on “management,” problems will recur in different forms, and the cycle of the same debates and frontline burnout will not stop.

Conclusion

The true responsible party for IS issues is not the IS department, the front line, or vendors. It is “management itself,” which has failed to make IT the subject of management decisions and has kept its distance from the responsibility for those judgments. This conclusion is not for the purpose of condemnation, but to show that reclaiming responsibility here is the starting point for true Digital Transformation (DX) and IT strategy. If we are serious about solving these problems, there is no path other than management taking ownership of the responsibility for IT-related decisions. All other reforms will remain mere symptomatic treatments.