Why Technology Projects Fall Short of Their Promise
2026.06.16
min
Written by:
Myriam Levert, Céline Huot, Caroline Ménard
2026.06.16
min
Written by:
Myriam Levert, Céline Huot, Caroline MénardOrganizations are investing in technology at an unprecedented pace. Yet one observation resurfaces with striking consistency: the returns are not materializing. The root cause is rarely the quality of implementation. More often, it is the absence of the organizational clarity that should have preceded it.
The enterprise software landscape has never been more mature. ERP platforms, FP&A solutions, CRM systems, advanced analytics and AI: these tools are well-established, rigorously tested and broadly available. The problem is not the technology. The problem is the sequence of decisions that leads organizations to adopt it.
Despite significant investments and proven solutions, expected gains remain elusive. Adoption is partial. Teams work around systems rather than through them. When accountability comes due, organizations point to change management failures or user resistance. These factors exist, but they rarely explain the full extent of the gaps.
Strategic intent is not a vision statement. It is not a mandate to “modernize systems” or “accelerate the digital agenda.” True organizational intent requires a deliberate, explicit position on what needs to change: which business problem is being solved, which decisions need to improve, which behaviors must evolve, and which trade-offs leadership is willing to make to get there.
Without that clarity, technology becomes a bet. Leaders hope the tool will impose structure, harmonize practices, or drive alignment across the organization. In practice, it can only reflect the dynamics that already exist. Alignment is widely recognized as fundamental to performance, yet it remains elusive in most organizations, in large part because leaders underestimate how difficult it is to translate strategic intent into concrete, coherent choices.¹
In many organizations, technology transformation begins with a market scan: comparing features, evaluating vendors, building a business case. The difficulty is that this approach becomes deeply problematic when it precedes a rigorous examination of processes, roles and organizational priorities.
Selecting a tool before defining the problem it must solve is a fundamental inversion of logic. The organization commits to a solution without having established the conditions for its success. The organizations that consistently deliver value from technology transformation think first about their operating model, then about processes, and only then about tools. Not the reverse.
Technology implementation is never organizationally neutral. Every major deployment forces decisions: How much standardization is the organization prepared to accept? How centralized should decision rights be? What level of data transparency is genuinely expected? How will exceptions be governed?
These are questions of governance, culture and, at times, of power. When leadership does not take an explicit position on them, the tool meets implicit resistance. Users develop workarounds. Exceptions multiply. Parallel processes persist. What looks like a technology failure is, in reality, the visible symptom of a deeper organizational misalignment.
Consider a manufacturing organization that implemented an automated invoice payment solution: technically sound, operationally straightforward and well-scoped. The conditions for success appeared to be in place. But leadership deferred the review of upstream procurement processes and postponed conversations about evolving team roles, even as automation was materially reshaping the workload. The result: fewer than 30% of invoices were processed automatically, and the team, left without clarity on its future, gradually disengaged.
A second case makes the pattern equally clear. A professional services organization launched more than a dozen AI initiatives in rapid succession, without first mapping its inefficiencies or validating data quality. Eighteen months later, those solutions coexisted with wildly variable adoption rates and no measurable performance gains. The organization was forced to return to fundamentals: clarifying priorities, rationalizing investments and redesigning processes end-to-end, from data creation to operational use, before any value could be extracted.
No tool can bridge the gap between teams with divergent priorities, resolve unaddressed strategic tensions, or absorb the friction between day-to-day operations and transformation. That is leadership’s work. When it is left undone, technology becomes the focal point of organizational difficulty, not its cause.
Organizations that consistently extract value from technology investments share a common discipline: they begin with intent. They define business objectives, prioritize use cases, map target processes and clarify accountabilities before any technology decision is made. The solution follows as a means of enabling a model that has already been designed.
This sequencing logic is well-supported in the literature. Research consistently highlights the importance of establishing a clear “true north,” an organizing principle that aligns initiatives and guides decisions throughout the transformation journey.² The tool is not the starting point. It is a consequence of strategic clarity.
Execution ultimately depends on leaders’ willingness to own the decisions that implementation demands. That means taking positions on uncomfortable trade-offs, limiting the exceptions that erode system coherence and maintaining consistent messaging across the executive team. It means modeling the behaviors the organization expects, and accepting that some operational flexibility must be sacrificed in the interest of collective discipline.
These are not small asks. But they are what determine whether a transformation is credible. Without them, tools remain underutilized, and the returns remain theoretical.
Research from the Conference Board of Canada reinforces this point: productivity gains depend on the deliberate integration of innovation, organizational design and capability development. Technology accumulation, however sophisticated, does not translate automatically into performance. These are not autonomous solutions. They are accelerators of an operating model that leadership must first define and commit to.
Successful technology implementation is not fundamentally about deploying a capable tool. It is about the organizational decisions that must precede it: on priorities, operating models, governance trade-offs and expected behaviors. Without that foundation, technology investments do not unlock their potential. They tend, instead, to amplify the misalignments already present.
This article is adapted from the original French version published by Revue Gestion.
Read the original article here
¹ Trevor, J., “What Leaders Get Wrong About Strategic Alignment,” Harvard Business Review, January 14, 2026.
² Viswa, C. A. et al., “Scaling Gen AI in the Life Sciences Industry,” McKinsey & Company, January 10, 2025.