The Invisible Cracks Deepening Behind “DX Success”
Many executives receive “success reports” on individual DX projects or SaaS implementations, yet somehow feel no tangible improvement in the organization’s overall IT capability. The sales department leverages a CRM, development introduces the latest tools, and accounting streamlines with cloud software. Individually, everything seems to be progressing smoothly. But when it comes time to produce the “company-wide numbers” needed for management decisions, they end up scrambling to gather disparate data from each department and manually piecing it together. This is not merely a lack of tool integration. It is a structural disconnect created by a fundamental “mismatch in time horizons” that management has failed to define.
Through supporting over 38 companies, I have become convinced that this “disconnect in time horizons” is one of the primary factors that significantly erodes the effectiveness of IT investment and dulls management decision-making. When making IT investment decisions, executives focus on “cost” and “functionality,” but they almost never define the “speed” or “update frequency” at which that IT operates and contributes to decision-making. As a result, three different IT systems, each operating on its own timeline, coexist within the organization, evolving independently without intersecting.
The “Three IT Time Horizons” Left Unmanaged
The IT within an organization evolves and operates on entirely different time horizons depending on its role. It is precisely this difference in time horizons that creates the physical wall preventing integration.
Business IT Evolving in “Seconds”: Speed is Life
This is the IT for areas directly involved in growth and customer touchpoints, such as sales, marketing, and development. Examples include real-time lead tracking using Salesforce, instant communication on Slack or Teams, and continuous integration on GitHub. The time horizon here is “seconds” or “minutes.” The speed of judgment and execution creates competitive advantage, and even a slight delay directly leads to missed opportunities. Those responsible in this domain immediately trial new SaaS as it appears and respond sensitively to vendor updates. Their objective function is “how fast, how much.”
Management IT Operating on “Months to Quarters”: The Design of Integration and Reproducibility
This is the IT used by management to assess business health and decide the next move. It centers on systems like ERP (Enterprise Resource Planning), integrated BI (Business Intelligence) tools, and budget-actual management systems. The time horizon here is “months” or “quarters.” Data accuracy, comparability, and reproducibility are the top priorities. Data aggregates when monthly closing occurs, and management plans are reviewed each quarter. This cycle is the lifeline. However, the raw, “second-by-second” data from business IT does not flow directly into here. The essential processes of aggregation, processing, and adjustment—tasks that “take time”—inevitably slow down the speed.
Operational IT Moving in “Years”: Stability is Everything
This is the IT supporting the corporate foundation: core systems, networks, security, asset management, etc. It is often managed by the IT department. The time horizon here is “years,” sometimes even “several years.” The primary evaluation criteria are “stability” and “cost control.” System downtime is unacceptable, and steady operation within budget is required. Major overhauls require lengthy procurement and implementation periods, and events like Windows OS end-of-support often trigger updates. Their objective function is “how stably, how cheaply.”
The “Four Realities” Created by Colliding Time Horizons
What realities emerge when these three time horizons coexist without a common purpose?
1. The Physical Limits of Data Integration
The real-time dashboard the sales department wants “right now” is physically impossible to extract from core systems premised on annual contracts and design. The intervening IT department, concerned about security and load, demands careful consideration. As a result, sales start manual aggregation in Google Sheets without waiting for approval, and another instance of “shadow IT” is born. This is not a matter of will; it is a physical limitation where the “second” and “year” time horizons cannot directly communicate.
2. The Impossibility of Measuring Investment ROI
Even if management introduces the latest collaboration tool for “productivity improvement,” measuring its effect with the “quarterly” numbers of management IT is extremely difficult. Between tool usage logs (in seconds) and final performance (in quarters), there exist numerous intermediate variables and time lags. Unable to calculate ROI, IT investment ends up being discussed either as a “cost” or an “article of faith.”
3. Distortion in Talent Evaluation and Development
Top talent thriving in the “second” world of business IT is valued for speed and innovation. Meanwhile, personnel supporting the “year” world of operational IT are valued for steadiness and risk management skills. Their required aptitudes are polar opposites, making it difficult for them to recognize each other’s value, and their career paths become divided. This solidifies the structure where tech-savvy personnel lack a management perspective, and management cannot understand technology.
4. The Normalization of “Time Lag” in Management Decisions
The most serious issue is the delay that arises in management decision-making itself. Even if market changes (in seconds) are detected, it takes weeks or months to prepare reliable data for discussion at a management meeting (quarterly). Opportunities are lost in the interim, and decisions are always reactive. This is not because decision-making speed is slow; it is because the time horizon of the IT supporting those decisions is vastly misaligned with business reality.
Management Practice: “Designing” the Time Horizons
So, how should management confront this disconnect in time horizons? The key lies in shifting from “delegating” IT to “designing” its time horizons.
First Step: “Visualize” the Three Time Horizons
Try categorizing your company’s major IT systems and SaaS into three groups: “Business IT (seconds-minutes),” “Management IT (months-quarters),” and “Operational IT (years).” Don’t just list tool names; map them from the perspective of “how long does it take for that tool’s data to be used in decision-making?” You will likely notice that in many companies, a “black box” exists between business IT and management IT—manual data handoffs via Excel or email. This is the first realization.
The Core: Calculate the “Update Frequency” of Management IT Backwards from Business Strategy
The most critical management decision is, “How fast should the time horizon of our management IT be?” “Quarterly” is not the default. In industries with intense competition, you may need to review strategy on a “monthly” or even “weekly” basis. In that case, the data aggregation and analysis cycle of management IT must also be redesigned to match, moving to a “weekly” cycle. This is not merely a tool setting; it means redesigning the business processes themselves, including data flow, inter-departmental reporting rules, and manager authority.
Concrete Measure: Intentionally Create a “Conversion Layer” to Connect Time Horizons
While you cannot use “second” data directly for “quarterly” reports, complete separation is also problematic. What’s needed here is an intentionally designed “conversion layer.” Specifically, this means setting up a mechanism using automation tools like Zapier or Power Automate to regularly (e.g., every night) accumulate and prepare raw business IT data in a data warehouse. Or, establishing a middleware layer that connects Salesforce dashboards and management BI tools (Tableau, Power BI, etc.) via API. Management must clearly define the existence of this layer and its update frequency (daily or hourly). This allows the conflict between the IT department’s concerns for stability and the business unit’s demands for speed to be contained within a pre-designed process.
Defining “IT Time” is Defining Management Speed
The disconnect in IT time horizons is not a technical issue; it is a fundamental design problem that dictates the speed and quality of management decision-making. No matter how fast individual SaaS tools become, if the management decision-making process connecting them remains bound to the traditional “quarterly” time horizon, the organization’s overall agility will not improve.
When management next considers an IT investment, they should ask themselves: “Which time horizon’s IT does this tool strengthen?” and “Is it aligned with the speed of decision-making we aim for?” If management IT cannot keep up with the speed of business IT, the investment target might not be the latest CRM, but rather the intermediate layer that “converts” and “accelerates” data. If everything is aligned solely with the stability-focused time horizon of operational IT, the business will suffocate.
IT integration is not about standardizing tools under one vendor. It is about designing the mechanism: how to mesh gears turning at different speeds using decelerators and accelerators, to reliably transmit power to the driving axle that is management. This is one of the most crucial “definitions of IT”—a task only management can perform.
Comments