What Kind of IT Should Management Design?

Introduction

This media platform has previously analyzed why IT departments became trapped in a defensive posture, why IT failed to become a strategic weapon for management, and why reform efforts have consistently failed, framing these as issues of management judgment and organizational structure. This article represents the turning point. It is not about “the role IT departments should play” or “theories of IT department reform.” It is an attempt to clearly articulate the design responsibility that management itself should have shouldered.

The IT Management Must Design is Not a “Tool”

We must start with a negation. The IT that management must design is not about selecting individual tools—which system to implement, which SaaS to choose, whether to build in-house or outsource. These are merely the means that appear as a result of the design. What management should have fundamentally designed is the answer to the essential question: “What do we want to replicate using IT?”

What Management Should Have Designed is the “Decision-Making Structure”

The essential value of IT is not mere operational efficiency. Its value lies in speeding up decisions, aligning decisions, and making decisions reproducible. In other words, the IT that management must design is a mechanism that structurally codifies “how this company makes decisions.” Which information is reviewed, who makes the judgment, what is standardized into rules, and where is discretion retained? Introducing IT without deciding these points will only result in more tools, decisions becoming dependent on individuals, and a loss of overall visibility.

The Responsibility to Simultaneously Design “Business, Organization, and IT”

This is why overseas companies and high-growth firms appear exceptional. They design their business model, organizational structure, and IT architecture simultaneously, not in isolation. In contrast, many Japanese companies have long been siloed: business belongs to business units, organization to HR, and IT to the IT department. In reality, however, business, organization, and IT are an inseparable trinity that cannot be designed separately. The IT that management must design is the holistic blueprint that includes which tasks to leave to people, where to embed structure, and where to stop judgment.

The “Decision to Discard” That Management Should Have Owned

The primary reason IT has become complex and overall optimization has been lost is that no one took ownership of the “decision to discard.”

• Should we keep or discard the legacy system?
• Should we stop or allow departmental optimization?
• Should we pursue short-term results or avoid future technical debt?

These are all decisions that only management can make. The moment these are delegated to the IT department, responsibility and authority become misaligned, and overall optimization fails. The IT that management should have designed was the very structure capable of deciding “what not to do.”

IT is a “Reproduction Device for Management Philosophy”

Ultimately, we arrive at this question: “What kind of decisions does this company consider good?” Is speed the top priority, reproducibility most valued, or stability paramount? These are matters of management philosophy, which should be articulated and shared. IT is merely the device for translating that philosophy into processes, converting it into rules, and embedding it into data structures. Therefore, the IT that management must design is the structure that reproduces its management philosophy.

Conclusion

As long as we attempt to answer the question, “What kind of IT should management design?” solely with the latest technology, DX initiatives, or organizational theory, the discussion will never align. The answer lies in a more fundamental question: “What kind of decision-making company do we want to be?” Management must answer this question and design its content as a structure. Only then do the role of the IT department, the meaning of IT investment, and the criteria for tool selection naturally become clear. To design IT is, in essence, to design management itself.