Technology Investment Success Begins with Better Management, Not Product Selection
The true value of enterprise technology investments is measured not by what is purchased, but by the business objective it serves, how it is managed, and the results it produces.
Imagine an organization approving a large-scale technology investment. Presentations have been made to the board, the budget has been approved, the project timeline has been set, and one of the market's leading technologies has been selected.
On paper, everything looks promising.
After months of work, the system goes live. However, over time, the budget is exceeded, unexpected costs arise, and users struggle to adapt to the new system. Business processes do not improve as expected. The efficiency, growth, or risk reduction targets promised at the beginning of the project are never achieved.
The technology is working. The project is complete. But has the investment been a success?
The answer to this question requires much more than simply putting the system into operation.
Because Completing a technology project is not the same as creating value from a technology investment.
In corporate investments, the main problem often stems not from a lack of technology, but from a failure to establish a connection between strategy, business processes, decision-making mechanisms, and implementation. Even the most advanced software or comprehensive infrastructure cannot automatically solve a poorly defined business need.
Technology is a powerful tool. However, it is the management approach that determines for what purpose this tool will be used, what risks are acceptable, and how success will be measured.
So how can organizations transform technology investments from a cost item into sustainable business value?
1. The rationale for investment should be job needs, not technology.
One of the most common misconceptions in the corporate technology world is confusing the need for modernization with the goal of improving business processes.
When considering a new ERP system, cloud infrastructure, cybersecurity platform, or data analytics solution, the first question is usually which product to choose.
However, there are questions that need to be answered before that:
•What business problem are we trying to solve?
•What is the cost of the current situation to the organization?
•Which strategic objective will this investment support?
•Is it possible to achieve the same result at a lower cost or with less complexity?
•Does the organization need to make changes to its current processes?
The SAP-based inventory management transformation of the German retail company Lidl is one example that demonstrates the importance of these questions.
In 2018, Lidl decided to end the eLWIS project, which it had been working on for about seven years. At the time, press reports indicated that around €500 million had been spent on the project; however, this figure was never officially confirmed by the companies involved.
One of the project's major challenges was the incompatibility between Lidl's inventory valuation approach and the way the standard SAP Retail software operated. While Lidl wanted to maintain its existing approach, the need to adapt the software increased costs and complexity. The company concluded that it could not achieve its initially defined strategic goals at acceptable costs.
The lesson to be learned here is not that standard software is always the right choice or that existing business processes must be changed.
The main lesson is this: The alignment between technology selection and business practices should be considered a strategic decision at the outset of the investment.
Sometimes the right decision is to change the business process. Sometimes it's necessary to adapt the software, choose a different solution, or redefine the scope of the investment.
The important thing is that these decisions are made not as a natural consequence of technical preferences, but based on a clear business rationale and a cost-benefit analysis.
2. We should measure success by business results, not by the time the product goes live.
In enterprise technology projects, the go-live date often becomes the most important milestone. Budget compliance, schedule adherence, and completed technical deliverables are presented as indicators of success.
All of these factors are important. However, none of them alone proves that the investment was successful.
The large-scale IT transition experienced by UK-based TSB Bank in 2018 is a striking example of this.
The bank spent years preparing for the transition from its old platform to a new banking system. Numerous tests and transition trials were conducted; assurances were obtained from managers and suppliers.
Despite this, significant service disruptions occurred after the transition. Customers experienced problems accessing their accounts and banking services. The bank faced significant costs due to customer inconveniences and operational disruptions.
TSB's 2018 annual report revealed a cost and revenue impact of £330.2 million associated with service disruptions following the transition. A subsequent independent review indicated that different approaches could have been adopted in planning, supplier oversight, and testing practices.
The important point in this example is not the lack of technical preparation, but the fact that the preparations made failed to guarantee real-world operational outcomes.
Just because a system passes tests doesn't mean it will work flawlessly under all conditions. A supplier's assurance doesn't absolve the organization of its own responsibility. Completing a transition on schedule isn't proof of operational resilience either.
Therefore, success criteria should be defined at the beginning of the project.
For example:
•What level of accessibility should critical services have?
•How should the system behave when trading volume increases?
•How long should it take for services to be restored after an outage?
•What operational efficiency improvements should the new system provide?
•How should user adoption of the new system be measured?
•How can it be verified that security and compliance objectives are met?
The answers to these questions should be on the agenda not only of IT teams, but also of managers responsible for the commercial and operational results of the investment.
Going live is a milestone. True success comes when the system operates reliably and produces the promised business results.
3. If the person who made the decisions is not clear, then accountability also becomes unclear.
One common problem in large technology investments is that, over time, the project falls outside the agenda of business units and comes to be seen solely as the responsibility of the IT department.
Business units communicate their needs. IT designs the technical solution. It develops the supplier system. Project management monitors the schedule.
However, while all these activities are being carried out, the following questions may remain unanswered:
Who will prioritize business requirements? Who will approve scope changes? Who will make the final decision when business prospects conflict with technical constraints? Who will be responsible for ensuring the promised benefits are realized upon project completion?
The digital transformation dispute between Hertz and Accenture, which went to court in 2019, is one example illustrating the cost of such problems.
Hertz partnered with Accenture to redesign its website and mobile applications. Delays, technical issues, and delivery obligations related to the project have led to a legal dispute between the parties. Hertz's lawsuit alleges that it paid Accenture over $32 million for the project.
It would be incorrect to attribute all the causes of this incident to a single managerial deficiency. However, the case demonstrates how critical the relationship between business requirements, technical deliverables, and contractual responsibilities is in large-scale technology projects.
In a project, it's not enough for responsibilities to be written in the contract. It must also be clear how decisions will be made, how changes will be managed, and how disputes will be resolved.
An effective governance model should clearly define at least four areas of responsibility:
•Business sponsor: This role owns the investment's business rationale, strategic priority, and expected commercial outcomes.
•Product or process owner: This role prioritizes requirements and makes business decisions, and ensures the solution meets real needs.
•Technology and architectural leadership: It is responsible for ensuring the suitability of technical design, integrations, safety requirements, and sustainability.
•Project and program management: It manages scope, timeline, budget, dependencies, and risks in an integrated manner.
These roles can be undertaken by different individuals. However, the relationships of authority and responsibility between them should not be left unclear.
The goal of governance is not to hold more meetings or to bog decisions down in bureaucratic processes.
The goal is to ensure that the right decisions are made by the right people in a timely manner, and that the results of these decisions are monitored.
4. Scope management is about managing the right change, not resisting it.
Organizational needs change over time. New regulations, customer expectations, security threats, and market conditions may create new requirements after a project has begun.
Therefore, successful investment management does not mean maintaining the initially defined scope at all costs.
The key is understanding which changes will create value and which will introduce cost, complexity, or risk.
Every new request should be evaluated from at least four perspectives:
1. What is its contribution to job value?
2. What is its impact on total cost and delivery schedule?
3. How does it alter architectural complexity, technical debt, and security risks?
4. Which of the previously agreed-upon goals does this affect?
In projects where this discipline is absent, the scope expands over time, integrations become more complex, and temporary solutions transform into permanent architectural components.
Initially seemingly small decisions can accumulate, increasing system maintenance costs and limiting future transformation options.
At this point, technical debt is not just an engineering issue. If left unmanaged, it transforms into a financial, operational, and strategic risk.
Southwest Airlines' operational crisis in December 2022 highlighted the importance of this relationship.
Following severe winter conditions in the U.S., the company experienced significant difficulties reassigning flight crews, flight schedules, and aircraft. More than 16,700 flights were canceled between December 21 and 31. The company reported a pre-tax financial impact of approximately $800 million for the fourth quarter of 2022.
Attributing these results solely to outdated software would be incomplete. Weather conditions, operational planning, inter-system dependencies, and recovery capacity following the crisis must all be considered together.
However, the incident has an important management message: the resilience of systems supporting critical operations cannot be designed solely for normal operating conditions.
An organization should know in advance how long it can operate under extraordinary circumstances, which processes can be carried out using alternative methods, and how long it will take to recover its operations.
Therefore, in technology investments, technical debt, business continuity, and operational resilience should not be considered as independent issues.
An architectural decision postponed today could become not just a technical problem tomorrow, but a direct risk to business continuity.
5. The true cost of an investment is not limited to the purchase price.
A financial assessment of a technology investment is incomplete if it is limited to licensing and hardware costs.
Implementation, integration, data migration, training, change management, maintenance, support, security, capacity expansion, and future migration costs are also part of the total cost of ownership.
In addition, the conditions under which the benefits of the investment will be realized should also be evaluated.
For example, a new automation platform can reduce operational workload. However, realizing this benefit may depend on redesigning processes, user adoption of the system, and efficient use of the resulting capacity.
Therefore, the economic justification for investment should not be based solely on assumptions about technology.
A sound business justification should include at least three elements:
•Cost visibility: The initial and life cycle costs of the investment should be calculated as completely as possible.
•Benefit visibility: Expected outcomes, such as increased productivity, revenue growth, cost reduction, or risk decrease, should be defined in a measurable way.
•Uncertainty management: It should be shown what assumptions the predictions are based on, what risks are involved, and how the results might change under different scenarios.
Especially in large-scale transformations, one of the most important questions is this:
What will the organization do if the expected benefits don't materialize?
The business rationale established at the start of the investment should not be discarded after project approval. Costs, risks, and expected benefits should be re-evaluated throughout the project.
In some cases, changing the scope, dividing the investment into phases, or postponing a specific component may be the best decision. Sometimes, new information may necessitate halting the investment altogether.
This is not about accepting failure; it's a management approach that conserves resources and prioritizes corporate value.
6. How do we measure the value of an investment?
One of the most significant shortcomings in technology projects is the insufficient and unsystematic evaluation of the real impact of the investment after the project is completed.
The system is commissioned, the project team moves on to another task, and daily operations continue through the new structure.
However, whether the initially promised benefits actually materialize is often not followed up with the same level of diligence.
However, the true performance of an investment is understood not from the project closing report, but from the business results that emerge over time.
Therefore, four elements must be defined in advance for every major technology investment:
•Initial value: What is the current performance level prior to the investment?
•Target value: What tangible improvements should the investment deliver?
•Measurement method: Which data and indicators will be used to evaluate the results?
•Person in charge: Who will monitor whether the expected benefit is realized?
For example, when investing in cybersecurity, it's not enough to simply measure the number of products purchased or the systems covered.
The primary assessment should be based on whether the level of protection for critical assets has increased, whether incident detection and response times have improved, whether the risk of service disruption has decreased, and to what extent the investment contributes to existing security capacity.
Similarly, an infrastructure modernization should not only involve commissioning new servers but also monitor outcomes such as service availability, capacity utilization, operating costs, recovery time, and operational flexibility.
There is an important distinction here: not every benefit may have a direct financial equivalent.
Meeting regulatory obligations, mitigating critical risks, or strengthening service continuity can also contribute to the value of an investment. However, these benefits should also be defined with clear criteria whenever possible.
Unmeasured utility cannot be managed; utility that is not claimed easily remains an assumption.
7. An integrated management model for successful technology investments.
The examples we have discussed so far show that technology investments cannot be reduced to a single project management discipline.
Success depends on the harmonious interplay of strategic priorities, financial discipline, business ownership, architectural decisions, risk management, and benefit measurement.
Therefore, I propose that large-scale technology investments be managed through seven key control mechanisms.
The aim of this model is not to create a new layer of bureaucracy.
The aim is to ensure that large investments are managed holistically, not just in terms of project schedule and budget, but also from their strategic rationale to their operational outcomes.
The board of directors must know why the investment is necessary. The business owner must assume the expected benefit. Technology teams must deliver a reliable and sustainable solution. Finance teams must track cost and benefit assumptions. Risk and security functions must assess how decisions align with the organization's risk appetite.
These responsibilities don't need to be concentrated in one person. However, none of them should be left unattended.
Success doesn't come from all parties doing the same job, but from managing different responsibilities toward a common goal.
Conclusion: It's not about buying technology, it's about managing value.
In enterprise technology investments, the most important question is not which product or platform to choose.
The real question is, what problem will this investment solve for the institution, what goal will it support, and what results will qualify it as a success?
Lidl's ERP transformation demonstrates the importance of alignment between standard software and business processes. TSB's crisis serves as a reminder that even comprehensive preparation and assurances do not automatically guarantee operational success. The dispute between Hertz and Accenture highlights the importance of clear responsibilities and delivery expectations. Southwest's operational crisis illustrates the impact of technology dependencies and resilience on business results.
The common message of these examples is not that technology is unimportant; rather, it is that technology, when not managed correctly, cannot produce the expected value.
Today, organizations need more than just to buy more technology. They need a management approach that links investments to strategic goals, clarifies decision-making, anticipates risks, and measures the realized benefits.
This approach transforms technology investments from being solely the responsibility of the IT department into an integral part of the corporate strategy.
Because the true success of technology investments is not revealed on the day the project is completed, but through the sustainable change it creates in the organization's working methods and business results.
Technology is a powerful accelerator. However, without a strategy that sets the direction, a management approach that takes ownership of the decisions, and a discipline that measures the results, speed alone does not guarantee success.
First published: LinkedIn, 2026-11-01 22:41. Original article: https://www.linkedin.com/pulse/teknoloji-yat%C4%B1r%C4%B1mlar%C4%B1nda-ba%C5%9Far%C4%B1-se%C3%A7imiyle-de%C4%9Fil-y%C3%B6netim-melih-%C3%B6zhan-nnbbf
Comments