Every business has them: The system that was only meant to be temporary, the software that was purchased to solve one very specific problem, the workaround that saved the day when a project was running behind schedule and the technology that was supposed to be replaced three years ago.
At the time, these decisions made sense but technology has a habit of outliving the circumstances that brought it into the business in the first place. What begins as a sensible short-term decision can quietly become a permanent part of the organisation, long after its original purpose has disappeared.
Businesses spend considerable time thinking about their next technology investment, but far fewer take a step back to examine the decisions that have brought them to where they are today.
The Temporary Solution That Became Permanent
Few things are as difficult to remove from a business as a temporary solution that works well enough.
Perhaps a department introduced a spreadsheet to manage information while waiting for a new system to be implemented. The implementation was delayed, so the spreadsheet stayed. Employees became comfortable using it, additional information was added, and eventually it became an important part of the department’s daily operations.
Years later, the business may have several systems that should perform the same function, but employees still rely on the spreadsheet because it is familiar and convenient.
The problem is no longer simply the spreadsheet itself. It is the collection of decisions that have accumulated around it. People have developed processes, responsibilities and expectations based on a solution that was never designed to become permanent.
The same thing happens with ICT infrastructure. An organisation may introduce an interim server, a secondary application or a manual process to compensate for a system limitation. As time passes, more dependencies develop around that original workaround, making it increasingly difficult to remove.
Eventually, the business is no longer dealing with a temporary fix. It is managing an entire set of processes built around a decision nobody remembers making.
When Yesterday’s Technology Becomes Tomorrow’s Constraint
Technology decisions are made for a particular business at a particular moment in time but businesses and their needs continuously change. Yet the technology supporting these activities don’t evolve at the same pace.
Replacing these systems can be expensive and disruptive, so the natural response is often to work around their limitations. Businesses may respond by introducing another application, an additional integration, or employees develop a manual process to bridge the gap.
While each of these decisions may seem to be reasonable in isolation, the difficulty comes in when businesses have to manage the combined result of all of these additions.
The Cost of a Decision Doesn’t Always Appear on the Original Invoice
One of the reasons outdated technology decisions are so difficult to identify is that their true cost rarely sits in one place.
The original purchase may have been a set fee. However, the business might now be paying for specialist maintenance, workarounds and integrations that would not have been necessary if a different approach had been taken.
There are also costs that never appear directly on a supplier invoice. Such as; employees spend time moving information between systems, IT teams maintain ageing infrastructure instead of working on more valuable projects, managers waiting for reports that should be readily available or new initiatives taking longer because existing systems can’t easily accommodate them.
Individually, these expenses wouldn’t necessarily attract much attention but together, they can have a meaningful impact on productivity, budgets and the organisation’s ability to make progress.
This doesn’t mean that every older system should be replaced or that every historical decision was a mistake. The real question is whether the business still understands the reasons for keeping it, the cost of maintaining it and the implications of continuing to depend on it.
The Most Expensive Decision Might Be the One You Keep Avoiding
When a business delays reviewing an ageing system, it may lose access to vendor support, struggle to find people with the necessary expertise or become increasingly dependent on a small number of individuals who know how to maintain it. Integrations can become harder to support and the eventual migration may become more complicated because the organisation has allowed dependencies to accumulate.
The challenge is knowing when to maintain, when to improve, when to replace and when to retire.
That requires more than looking at the age of a system or responding when something breaks. It requires understanding the role the technology plays in the business today, its ongoing costs, the risks associated with keeping it and the consequences of changing it. It also requires someone to revisit decisions that may have been perfectly sensible when they were originally made.
It’s Time to Stop Letting the Past Make Your Technology Decisions
At Telesa, we recognise that an ICT environment is not simply a collection of products and services purchased over time. It’s the result of years of business decisions, changing requirements, supplier relationships and operational compromises.
As an independent ICT management partner, we help businesses maintain a clearer understanding of their environments, assess whether existing arrangements continue to meet their needs and identify opportunities to improve how their technology is managed.
That includes looking beyond what is currently working to consider why it exists, what it costs, what it depends on and whether it remains appropriate for the business going forward.
The objective is not to replace technology for the sake of having something newer. It is to ensure that today’s decisions are informed by the reality of the business, rather than dictated by yesterday’s assumptions.
