Legacy systems are not the problem, how you work around them is

Older systemsglossary×SystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term→ do come with limitations. They're harder to change, often poorly documented, and rarely designed for how products operate today. But over time, teams buildglossary×BuildA build is the process of compiling and packaging code into a runnable application.Open glossary term→ workarounds. Processesglossary×ProcessA process is a defined sequence of steps used to achieve a specific outcome.Open glossary term→ are adjusted to compensate for gaps. Additional steps are introduced to handle edge cases. Different departments solve the same problem in slightly different ways because there's no single path that works for everyone. Individually, those decisions make sense. Collectively, they create complexity. What starts as a workaround becomes the way things are done.

The systemglossary×SystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term→ also makes a convenient subject because it cannot object. Naming a processglossary×ProcessA process is a defined sequence of steps used to achieve a specific outcome.Open glossary term→ as the problem implicates the team that runs it. Naming the platformglossary×PlatformA platform is a system or environment that enables users, services, or applications to interact, build, or operate.Open glossary term→ implicates nobody in the room, which is part of why the diagnosis lands so easily and goes unchallenged.

By the time transformationglossary×TransformationTransformation is a fundamental change in how a system, organisation, or experience operates, often involving structure, processes, and behaviour.Open glossary term→ is being considered, those workarounds are deeply embedded. They're no longer seen as temporary fixes, but as part of the systemglossary×SystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term→ itself. People rely on them. Processesglossary×ProcessA process is a defined sequence of steps used to achieve a specific outcome.Open glossary term→ are built around them. Entire workflows exist to compensate for limitations that were never properly addressed.

Replacing the systemglossary×SystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term→ doesn't remove that. What often happens is that a new platformglossary×PlatformA platform is a system or environment that enables users, services, or applications to interact, build, or operate.Open glossary term→ is introduced with the expectation that it will simplify everything. But the same processesglossary×ProcessA process is a defined sequence of steps used to achieve a specific outcome.Open glossary term→ are carried over. The same workarounds are rebuilt. The same inconsistencies are preserved, just implemented in a different way. The technology changes. The behaviour doesn't.

Requirements gathering is where it gets locked in. Asked what the new systemglossary×SystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term→ must do, people describe what the current one does, including the workarounds, because that is what the job now consists of. The specification captures the compensations faithfully and carries them across intact.

What shifts this is not replacing the systemglossary×SystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term→ first. It's understanding everything that has formed around it. That means looking at how work actually flows through the organisation: where decisions are made, where duplication exists, where people are compensating for gaps that shouldn't be there. It means identifying the workarounds, not just accepting them as part of the processglossary×ProcessA process is a defined sequence of steps used to achieve a specific outcome.Open glossary term→.

Once those patternsglossary×PatternA pattern is a reusable solution to a design problem that recurs across products and contexts. It captures an approach already shown to work, so a team solves the problem once rather than every time it appears.Open glossary term→ are visible, they can be challenged. Some can be removed entirely. Others can be simplified. In many cases, what looks like a systemglossary×SystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term→ limitation is actually a processglossary×ProcessA process is a defined sequence of steps used to achieve a specific outcome.Open glossary term→ that has evolved unnecessarily over time. Not everything needs to be carried forward.

The workarounds are rarely written down anywhere, which is what makes them hard to find. They live in the spreadsheet somebody maintains privately, the message sent to a colleague to unblock a case, the field being used for something other than its label. Those are the things worth asking about directly.

Instead of asking what the new systemglossary×SystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term→ needs to do, the focus should shift to how the organisation needs to operate. What should the processglossary×ProcessA process is a defined sequence of steps used to achieve a specific outcome.Open glossary term→ look like if it was designed properly? Where can steps be removed? Where can ownership be clarified? Where can consistencyglossary×ConsistencyConsistency is the use of uniform patterns, behaviours, and visual elements across a product to create familiarity and predictability. It helps users learn once and apply that knowledge throughout the experience.Open glossary term→ be introduced? Only then does the system come into play, as an enabler, not a constraint.

When this work is done upfront, legacy systemsglossary×Legacy SystemA legacy system is an outdated system that is still in use, often due to its critical role.Open glossary term→ often become more manageable than expected. In some cases, they can even support improvements without immediate replacement, simply because the way they're being used has changed. Legacy systemsglossary×SystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term→ do have limitations. But they're rarely the reason things aren't working. It's the layers of processglossary×ProcessA process is a defined sequence of steps used to achieve a specific outcome.Open glossary term→, workarounds, and decisions that have built up over time that create the real friction. Until those are addressed, replacing the system won't solve the problem. It will just move it somewhere else.

This also changes what a business case can honestly claim. Savings attributed to a replacement are usually savings from removing processglossary×ProcessA process is a defined sequence of steps used to achieve a specific outcome.Open glossary term→, and process can often be removed without replacing anything. Separating the two makes the case weaker on paper and considerably more likely to be realised.