How Should an IT Organization Be Designed?

Flawed IT Organization Design is Holding Back Management

IT investments fail to deliver results.

Conflict between IT and business units is constant.

The root cause lies in flawed IT organization design.

Abandon the mindset of designing from functions or department names.

Design from the “structure of decision-making” that supports management’s choices.

This is the only solution.

Functional Decomposition Destroys IT Organizations

Infrastructure, applications, security.

Dividing an organization by function creates silos.

Coordination costs between departments balloon.

Departmental convenience takes priority over overall optimization.

The essence of an IT organization is not functional management.

It is to execute the “decisions” necessary for management.

The Starting Point for Design is the “Type of Decision”

The first question should be about the types of decisions the company makes.

Strategic decisions that determine business direction.

Operational decisions that stabilize daily business.

Architectural decisions that shape the future IT structure.

These require completely different speeds and levels of stability.

Do not burden the same organization with heterogeneous types of decisions.

The Only Axis for Dividing IT Organizations: The “Objective Function”

Dividing by technical domain is a mistake.

Divide by “what the organization optimizes for.”

This is design by objective function.

IT organizations can be classified into three objectives.

The Organization that Optimizes for Stability

Manages core systems and infrastructure.

Its objective is “to keep systems running.”

Its evaluation metrics are clear: availability, robustness, etc.

The traditional IT department falls into this category.

The Organization that Optimizes for Growth Velocity

Manages business IT and product development.

Its objective is “to experiment fast and learn fast.”

Agile development and rapid response are essential.

IT teams embedded within business units correspond to this.

The Organization that Optimizes for Reproducibility

This is the organization most lacking in Japanese companies.

It designs business structures and overall architecture.

It translates management decisions into sustainable mechanisms.

This is the role of the organization that optimizes for reproducibility.

The Missing “Reproducibility” Organization in Japanese Companies

Organizations for stability and growth velocity have existed.

But organizations responsible for reproducibility are almost non-existent.

As a result, IT investments become ad-hoc.

No one considers optimization of the entire system.

The IT department retreats into a defensive posture.

Business IT runs amok without governance—a vicious cycle.

The “Decision” Boundary Management Must Draw

There is only one thing management must decide in IT organization design.

Which decisions to centralize and which to delegate to the front lines.

Drawing this boundary line is a core management role.

Changing org charts or department names is a secondary concern.

The structure of decision-making must be designed first.

Why “Strengthening the IT Department” Worsens the Problem

Superficial calls to “strengthen the IT department” are dangerous.

It grants authority to an organization without a defined objective function.

This only amplifies confusion on the ground.

The critical factor is not the amount of authority.

It is clearly defining the objective function assigned to each organization.

This is the first step in design.

The Next Step: Reflect Management’s Decision Structure in the Organization

The answer to IT organization design is simple.

Reflect management’s diverse decision-making structure in the organization.

Do not mix decisions for growth, stability, and reproducibility.

An IT organization is a structure for executing management decisions.

Names like “IT Dept.” or “DX Dept.” are not the essence.

The responsibility for deciding “who bears which decision” lies with management.

Begin your design from the types of decisions your company makes.