Every organisation eventually reaches a point where change becomes disproportionately expensive. Projects that once took weeks now take months, modernisation programmes absorb significant investment while delivering disappointingly little, and product launches or acquisitions become harder than anyone expected. Eventually the organisation arrives at a familiar conclusion: it has accumulated too much technical debt.
It is an understandable diagnosis. It is also a comforting one.
If the problem sits inside technology, then technology can solve it. Better architecture, better engineering and better tooling promise a route back to simplicity. The discussion naturally turns towards platforms, frameworks and modernisation programmes.
Reality is usually less accommodating.
Software has an unusually long memory. Long after executives have moved on, strategies have changed and organisational structures have been redrawn, systems continue to preserve the consequences of decisions that once seemed entirely reasonable. Every postponed decision, every temporary workaround and every exception that quietly became permanent leaves its mark.
That is why I have become increasingly sceptical when organisations describe their biggest challenge as technical debt. In many cases, the software is simply where the problem becomes visible. The underlying issue lies elsewhere.
Most organisations do not have a technical debt problem. They have a decision-making problem that happens to be visible in software.
Large organisations rarely become difficult to change because engineers collectively forgot how to build systems. More often, they become difficult to change because the organisation gradually loses the ability to make clear, consistent decisions and then reinforces that behaviour through its governance structures and incentives.
A strategic priority changes before the previous one has been completed. A platform replacement begins before anyone is prepared to retire the platform it replaces. Accountability becomes shared across so many committees that no individual genuinely owns the outcome. Each compromise appears reasonable when viewed in isolation, but over time those compromises accumulate into a level of complexity that no engineering programme can realistically eliminate.
The architecture is simply keeping score.
That helps explain why organisations with similar budgets, similar technologies and access to similar talent often achieve dramatically different outcomes. The distinguishing factor is seldom the technology itself. It is the quality and consistency of the decisions that shaped it.
None of this diminishes the importance of engineering discipline. Poor engineering can certainly create unnecessary complexity, just as poor financial management creates unnecessary cost. Strong engineering organisations work relentlessly to improve quality, simplify systems and reduce unnecessary complexity. However, there is a limit to what engineering alone can achieve. No architecture can compensate for constantly changing priorities, and no platform can eliminate organisational indecision. Technology amplifies organisational behaviour far more effectively than it corrects it.
That distinction matters because technology is no longer simply an operational concern. It increasingly determines how quickly an organisation can launch products, integrate acquisitions, respond to regulation, reduce operating costs or enter new markets. Complexity is no longer measured solely in engineering effort. It becomes a constraint on commercial execution.
This is why so many modernisation programmes struggle to achieve the outcomes promised at their inception. Organisations replace platforms while leaving untouched the behaviours that created those platforms in the first place. They expect new technology to compensate for old patterns of decision-making, when in reality the technology merely inherits them.
The organisations that sustain change over time are rarely those with the newest platforms or the most fashionable architectures. They are usually the ones that make fewer, clearer decisions and possess the discipline to live with those decisions long enough for the benefits to compound.
Every organisation believes its systems reflect its technology.
More often, they reflect its judgement.