IT Project Failures Are Caused by a Lack of Design
“Our IT implementation isn’t working.” “We invested, but our operations haven’t improved.” I hear these complaints all the time. What’s the real cause? Is it the wrong tools, a flawed implementation process, or a lack of skills among the staff?
From my experience supporting over 38 clients, I can say this: Most IT failures stem from management not “designing” the IT itself.
Many executives think of IT as something to “leave to the experts.” But IT is a management resource—a decision-making tool for the business. Handing it over entirely to specialists is nothing less than an abdication of management responsibility.
In this article, I’ll explain concretely what it means for management to “design” IT.
What is “IT Design”?
IT design is not just about deciding on a system architecture. It’s about management defining how to leverage IT to achieve the business strategy.
Specifically, management needs to clarify the following three elements:
Defining the Purpose
Is the goal of implementing IT to increase sales, reduce costs, or improve operational efficiency? If management doesn’t clearly define this, different departments will interpret it differently, leading to fragmented objectives.
For example, the sales department might introduce a CRM to “increase sales,” while the administrative department tries to use the same system to “reduce costs.” This conflict creates system chaos.
Setting Investment Criteria
Management needs to establish the criteria for IT investment decisions. Is it ROI, TCO, or customer satisfaction?
Without clear criteria, implementation proceeds based on gut feelings like “let’s just try it.” As a result, the investment never delivers the expected returns.
Designing for Reproducibility
IT is a tool to transform “individual success” into organizational strength. In other words, management’s role is to use IT to create a system that delivers the same results, even without a specific person in charge.
For instance, if you embed a veteran salesperson’s know-how into a CRM, even a new hire can achieve a certain level of performance. If you neglect this “design for reproducibility,” IT becomes nothing more than a recording tool.
Three Tragedies Caused by Poor Design
What problems arise when management doesn’t design IT? Here are three typical patterns.
Fragmented Objectives
If management doesn’t define the purpose of IT, each department will start using the system for their own convenience.
For example, at one manufacturing client, the sales department introduced Salesforce for “customer management.” Meanwhile, the manufacturing department introduced a different system for “production management.” As a result, customer data and production data were never linked, and the lead time from order to production didn’t improve.
This happened because management failed to define the objective of “linking customer and production data.”
Preserving Dependency on Individuals
Even if you introduce IT, if management doesn’t design the business processes, you won’t eliminate dependency on specific individuals.
At one service industry client, they introduced the task management tool “Asana.” However, because each team member started using it in their own way, project progress was not visualized, and the dependency on individuals actually worsened.
This was the result of management not designing the rules for “how to manage tasks.”
Incompatible System Silos
Systems introduced without a clear purpose or criteria often become impossible to integrate later.
At one retail client, the accounting system, inventory management system, and sales management system were each introduced by different vendors, and data could not be linked at all. As a result, matching inventory levels with sales data required manual Excel work every month.
Again, this was because management didn’t design for “system integration.”
Three Steps for Management to “Design IT”
So, what exactly should executives do? Follow these three steps.
Step 1: Back-Calculate IT Requirements from Your Business Strategy
First, clarify your company’s business strategy. Set goals like “double sales in three years” or “increase new customers by 50%,” and then back-calculate the IT requirements needed to achieve them.
For example, if your goal is to “increase new customers by 50%,” implementing a CRM is essential. You also need to consider integration with marketing automation (MA) tools.
Step 2: Set Investment Criteria
Management should set the criteria for IT investment decisions. For example, decide on specific metrics like “recoup the investment within two years” or “improve customer satisfaction scores by 10%.”
With these criteria, you can judge whether a tool’s features are “truly necessary” during selection. This reduces the risk of spending money on unnecessary features.
Step 3: Design for Reproducibility
After implementing IT, design how to standardize operations. Specifically, document business workflows and create manuals for using the system.
For example, if you introduce a CRM, set rules like “update deal status weekly” and “record all customer interactions in the system.” This ensures that even if the person in charge changes, the same quality of work can be maintained.
Conclusion: IT Design is Management’s Job
IT project failures are not the fault of the tools or vendors. They happen because management didn’t design the IT.
As a business leader, you should view IT not as something to “leave to the experts,” but as a “management resource you must design yourself.” How will you leverage IT to achieve your business strategy? Facing this question is the first step toward successful digital transformation.
If you feel your company’s IT design has challenges, start by checking the alignment between your business strategy and IT requirements. From there, you’ll see the truly necessary IT investments.
Comments