Why IT Doesn’t Make It to the Executive Boardroom

Introduction

In many companies, topics like sales, HR, investment, and organizational restructuring are mainstays on the executive meeting agenda. On the other hand, while IT is often labeled as “important,” it is rarely discussed in a substantive way during these strategic sessions. This article organizes the reasons for this, not from the perspective of meeting management or presentation skills, but from the structure of executive decision-making itself.

The Executive Meeting is a “Place for Decision-Making”

The essential role of an executive meeting is not information sharing, but rather to serve as a forum for making irreversible decisions such as “what to invest in,” “what to stop,” and “which risks to take.” Standing on this premise, it becomes clear that the reason IT doesn’t make it to the executive meeting is not simply because it is “overlooked.”

IT Was Not Organized as “Decision-Making Material”

Topics that make it to the executive meeting share common traits. They have a clear purpose, organized options, and articulated criteria for judgment. In contrast, IT has often been presented with unclear objectives, ambiguous success criteria, and opaque accountability even after a decision is made. As a result, IT is pushed to the periphery of executive meetings as a topic unsuitable for decisive judgment.

The Misconception of “Being Too Specialized”

The explanation that “IT is too specialized to discuss” is often used as a reason why it doesn’t appear in executive meetings. However, the high level of specialization itself is not the actual problem. The problem is that IT is not translated into the language of business decision-making. “What does this change for the business?” “What risk is the company taking?” “What is lost if we don’t proceed?” When only technical elements are presented without these questions being organized, the topic fails to qualify as a proper agenda item.

What Cannot Be Spoken in Numbers Does Not Become an Agenda

Executive meetings ultimately require some form of numerical judgment: investment amounts, expected returns, magnitude of risk, etc. However, with IT, the groundwork for speaking in numbers was often not prepared due to effects being inseparable, impact scope being too broad, or results appearing with a time lag. Consequently, IT became a topic that is “time-consuming to discuss yet yields no conclusion,” leading to its avoidance in executive meetings.

IT Treated Only as a Matter for Approval

In many companies, IT does “appear” in executive meetings. However, in most cases, it is limited to post-facto, formal treatments such as approving already-decided policies, reporting on budget utilization, or explaining issues after a problem occurs. This means IT is positioned not as a subject for decision-making, but as a subject for reporting results.

The Questions Management Failed to Take Ownership Of

Fundamentally, the questions management should have taken ownership of are as follows:

• Which business objective does this IT initiative support?
• Why is it necessary to do this now?
• If we don’t proceed, what constraints will remain?

However, these questions were left to the frontline or specialists and were not addressed in executive meetings. As a result, IT became a domain that progresses without having a “place for decision-making.”

The Resulting Consequences

When the state of IT being absent from executive meetings continues, the following phenomena occur:

• Large-scale IT investments become problematic after the fact.
• Departmental optimization is prioritized over company-wide optimization.
• The same failures are repeated.

These are not failures of IT, but rather the result of excluding IT from the arena of executive decision-making.

What is Needed Next

What is needed to bring IT back to the executive meeting is not a new presentation format. The first necessity is to reposition IT as a “management subject requiring judgment”—in other words, to discuss IT not as technology, but as a matter of decision-making. The next article will address how the myth that “IT should be left to the specialists” has justified this structure.