Most modernization projects are not rejected because they are inadequate, but because they are presented in a form the organization never treats as a priority.
The real challenge starts there: not when the risk is identified, but when you need to secure the buy-in required for the investment. Whether it is the CIO, a director, a manager, or another influential decision-maker, the obstacle is often the same. Modernization projects are rarely dismissed for lack of relevance. They struggle to gain traction because they arrive before the organization with an immediate cost, benefits that are less tangible in the short term, and a priority that is easier to push back than others. In this context, the way the initiative is presented does not create the issue, but it often has a decisive influence on the resulting decision.
A new product evokes growth potential. An acquisition opens access to a market. An expansion signals new revenue. Modernization, for its part, is mainly about preventing a disruption, reducing a vulnerability, or unlocking a capability the organization still struggles to recognize as concrete value. For an executive committee, the trade-off is not solely about budget; it is also narrative, strategic, and political.
The fundamental misunderstanding
The misunderstanding does not stem from an inability of decision-makers to understand technology. It stems from the fact that modernization is still too often presented to them in a language that is difficult to prioritize: technical vocabulary, technical indicators, a logic of correction rather than value creation. Yet the people who arbitrate these choices are not limited to senior technology leadership. They may be vice presidents, directors, managers responsible for a business unit, a budget, a transformation, or a critical service. Not all of them analyze the issue with the same frame of reference, but all of them influence the organization's real ability to act.
The most advanced organizations have already understood one thing: modernization can no longer be defended on technological grounds alone. It must be framed as a business decision, because its consequences directly affect growth, risk, operational continuity, and execution capacity. Yet too many digital initiatives still fail to deliver the expected business outcomes. The gap is not explained by execution alone. It often begins at the moment when you try to secure buy-in, justify the investment, and position the issue within the company's strategy.
A modernization project positioned as a "server replacement" or a "migration to the cloud" does not mobilize anyone beyond IT leadership. The same project, positioned as "a 40% reduction in time to market for new digital products" or "elimination of outage risk on the transactional systems that generate 80% of revenue," completely changes the conversation.
What modernization actually enables
Modernization projects that earn real executive support share a common trait: they are not defended for their technical elegance, but for their concrete effect on the business. Reduction of operational risk. Faster time to market. Simplification of tools. Greater capacity to integrate AI, absorb an acquisition, or sustain growth that the current environment is already holding back. Once the discussion shifts toward these outcomes, modernization stops being perceived as a cost center. It becomes what it should have always been: a strategic choice.
Modernization is not just an investment in technology. It is an investment in the organization's real capacity to operate, innovate, and grow. For it to be prioritized as such, it must be framed as such from the start.
Strategic translation: a shared responsibility
The highest-performing organizations now expect their decision-makers, their transformation leaders, and their technology leaders to connect technology choices to business outcomes, to participate in strategic trade-offs, and to bring technology, talent, and execution into alignment.
This evolution demands a competency that is not purely technical: the ability to translate. Translating an obsolescence risk into a revenue loss risk. Translating technical debt into an inability to launch a new product within market timelines. Translating a lack of interoperability into integration costs during the next acquisition. In this exercise, the architect does not merely validate a solution. The architect helps decision-makers see what the project truly involves: critical dependencies, scalability limitations, integration fragilities, security risks, or costs deferred rather than eliminated. When the architect understands both the technological constraints and the business objectives, that person becomes a valuable point of support for informing trade-offs and connecting technical choices to expected outcomes.
Repositioning modernization within business strategy
To be arbitrated at the business level, modernization must be presented with the standards, objectives, and governance of a business project.
Tie modernization to an explicit strategic objective
Not "migrate 200 applications to the cloud," but "secure operational continuity for the systems that support 80% of revenue," "reduce the technology integration timeline by 12 months for the next acquisition," or "finally create the conditions to deploy an AI agent capable of automating the triage of client requests, because data will no longer be scattered across five systems that do not communicate with each other."
Govern the project at the business level, not solely at the IT level
Steering committees must include representatives from the business lines, leaders capable of arbitrating priorities, and, where relevant, architecture profiles capable of informing structural decisions, making technical risk more readable, and supporting alignment with business objectives. Success indicators must measure the impact on operations, not just the number of applications migrated.
Present modernization as a credible, progressive, and measurable trajectory
A program spanning three to five years, with clearly defined phases, visible results at each stage, and rigorous governance. A plan that leadership can defend because it speaks the language of business.
The real obstacle is not the budget
The budget is not the only obstacle, and it is not always the first. What often blocks progress is the combination of an investment that is difficult to defend, a risk still perceived as abstract, and positioning that is insufficiently strategic. As long as modernization remains presented as an IT topic, it will remain vulnerable in trade-offs.
A technical project that requires millions without promising revenue will always be deferred or rejected. A business project that demonstrates how modernization reduces operational risk, accelerates time to market, improves regulatory compliance, and prepares the organization to leverage artificial intelligence has an entirely different chance of being approved.
Modernization is not held back because it lacks value. It is held back because that value still too often arrives in a form the business does not arbitrate. The day it is carried as a business decision, with its risks, its costs of inaction, and its concrete gains, it will finally stop being the expense that gets deferred and become the decision that gets made.
Sources and references
- Gartner (2024). Gartner Survey Reveals Only 48% of Digital Initiatives Are Successful. Digital initiatives are more successful when they are co-led by the CIO and other business leaders.
- McKinsey / Technology Magazine (2020). How CIOs Become Strategic Business Leaders. CIO performance depends on the ability to make technology an explicit driver of business value.
- IBM Institute for Business Value (2025). IBM Study: CEOs Double Down on AI While Navigating Enterprise Hurdles. Integrated data architecture, innovation ROI, and coherence in technology choices are becoming explicit business issues at the CEO level.
- IBM Institute for Business Value (2026). IBM Study: CEOs are Reshaping C-suite Roles for the AI Era. Leadership roles are converging further around technology, talent, and execution, reinforcing the strategic role of the CIO.
- Alithya (2026). Architecture d'entreprise : accélérateur de transformation dans l'assurance (available in French only). Enterprise architecture is presented as an alignment mechanism between strategic objectives, business capabilities, processes, applications, and data, in order to accelerate organizational transformation.