Acquisition complexity is rarely the result of one bad integration decision. More often, it builds through a series of decisions that were entirely rational at the time: a process variation retained because changing it wasn't commercially worthwhile, a manual workaround introduced because two systems didn't quite join up, or an additional control added to manage a particular risk.
Individually, none of these decisions create a significant problem. The challenge is what happens as they accumulate. Over years of acquisition-led growth, financial services organisations can find themselves carrying layers of processes, systems, controls, workarounds and dependencies that make the operation progressively harder to manage and harder to change.
I think operational debt is a useful way of describing what happens.
The concept of operational debt isn't new, but it's far less established than technical debt. To me, it describes the accumulated impact of operational decisions that made sense at the time, but collectively make an organisation more difficult to change.
Repeated acquisition can be a particularly significant source of that debt. A lot of attention naturally goes into the major integration decisions: technology, products, brand, distribution and go-to-market. At an operational level, things can look integrated, but the reality underneath can be quite different.
Having worked with organisations going through this, what I tend to see are different processes remaining, workflows not quite joining up, and data coming from different places and following different standards. Ownership isn't always clear, so teams develop their own workarounds and informal ways of routing work between them to keep things moving.
When looked at individually, these issues can appear too small to justify fixing, particularly where the solution requires significant technology investment, so they remain in place for the people on the ground to continue working around.
Another acquisition then brings another operating model into that environment, along with another set of decisions on what to integrate, what to retain and where compromises need to be made. Those decisions may, again, be completely rational. It’s their cumulative impact over successive acquisitions that creates the problem.
Our guide to how acquisitions create complexity in financial services explores in more detail how this complexity can accumulate across organisations that have grown through repeated acquisition.
One of the reasons operational debt can remain hidden for so long is that people become extremely good at working around it. Experienced employees know which system contains the right information, teams understand which exceptions apply to which legacy business, and manual interventions bridge gaps between processes that were never designed to work together.
Over time, those compensating mechanisms can become part of the operation itself:
The operation continues to function, but that doesn't mean the complexity has disappeared. Instead, people are absorbing it, and the organisation is effectively carrying an ongoing cost for decisions made over many years.
Like financial debt, operational debt can therefore be thought of as carrying an interest payment. The cost may be felt through rising operating costs, inconsistent customer experiences, increased operational risk or transformation programmes that become progressively more difficult to deliver. These can look like separate problems, but increasingly I think they can be different symptoms of the same underlying issue.
When organisations start trying to simplify, this matters more than ever. Making the mechanisms that compensate for complexity more efficient can improve performance, but it isn't the same as removing the complexity itself.
Operational debt doesn’t necessarily sit neatly within one team, system or process. A workaround in one part of the organisation may exist because of a system constraint somewhere else. An additional process step might be compensating for a problem further upstream or downstream, while unclear ownership may have its roots in organisational structures inherited from an acquisition years earlier.
What appears to be a local inefficiency can therefore have its cause somewhere entirely different in the wider journey. If each symptom is addressed independently, organisations can invest considerable time and money improving individual parts of the operation without materially simplifying the end-to-end experience.
This is particularly important when building the case for addressing acquisition complexity. As I previously mentioned, a single workaround or manual process may not justify the investment required to remove it, especially where technology change is involved. That said, the case can look very different when you understand the additional controls, delays, failure demand and downstream work connected to the same underlying cause.
For me, understanding the ‘why’ behind operational debt means joining those points together. Looking beyond where the complexity appears and understanding what’s driving it across the wider journey gives you a much stronger basis from which to decide what actually needs to change.
Once different processes and ways of working have been identified, standardisation can appear to be the obvious next step. There is value in consistency, but there is also a risk that organisations take a process containing years of accumulated complexity and simply make that process the standard.
If several variations of the same process exist across acquired businesses, the first question isn't just which one should win, but why those variations exist in the first place, which parts remain necessary and which reflect decisions or organisational structures that are no longer relevant.
The same applies to controls, handoffs and ownership. Some will exist for important regulatory, product or customer reasons, while others may simply have survived because removing them was never a sufficient priority on its own. The aim isn't to eliminate complexity from financial services operations altogether; much of that complexity exists for good reason. Instead, we want to distinguish necessary complexity from complexity that has simply accumulated over time.
This is particularly relevant in financial services, where legacy complexity cannot simply be stripped away without considering regulatory requirements and the impact on customer outcomes.
Not all operational friction should be removed. In financial services, some friction is intentional: additional steps may be needed to protect vulnerable customers, prevent fraud or reduce the risk of harm.
The challenge is distinguishing between friction that serves a purpose and friction that exists simply because years of acquired systems and processes have never been untangled.
It’s why I think simplification needs to come before standardisation or scale. Removing unnecessary steps, variations and dependencies creates a cleaner foundation. Only then does it make sense to decide what should be consistent across the wider organisation.
The same principle applies when automation and AI investment enters the conversation. Automation can make a manual workaround more efficient and AI may help teams navigate information distributed across different parts of the organisation. All of those interventions can create genuine value.
The risk is that technology becomes another way of compensating for operational debt rather than addressing its causes. If a process operates six different ways because of years of acquisition-led growth, it may be possible to build technology capable of accommodating all six. Doing so solves an immediate implementation problem, but it can also encode those variations into the future operating model.
In that situation, the organisation has become more efficient at carrying its complexity without necessarily becoming any simpler.
For me, this is why the sequence matters. Before asking how technology can improve an existing operation, I think there is value in understanding which parts of that operation should still exist in their current form. Simplifying unnecessary variation first can create much stronger foundations for whatever comes next.
Addressing operational debt doesn't mean redesigning an entire organisation or launching another multi-year transformation programme. In fact, trying to tackle every source of complexity at once risks creating another layer of change for the operation to absorb.
A more practical starting point is to understand how an important end-to-end journey actually works and where complexity is having the greatest cumulative impact. That means looking beyond documented processes to understand where teams are compensating for disconnected systems, where manual interventions are hiding problems elsewhere, where variations no longer have a clear purpose and where additional controls are managing complexity rather than reducing the need for it.
From there, organisations can start identifying the causes that are worth removing rather than simply treating the symptoms that appear around them. The aim isn't to create a theoretically perfect operating model. It's to make the organisation progressively easier to operate and, importantly, easier to change.
After years working in financial services transformation, I think that's an important distinction. Successful transformation depends as much on understanding the organisation you've inherited as it does on designing the organisation you want to create.
It's a principle that sits at the heart of our work at Reinvigoration - helping organisations understand how work really happens today, simplify the complexity that has accumulated over time and create stronger foundations for what comes next.
For firms that have grown through repeated acquisition, some of the biggest barriers to the next transformation programme may have been created long before that programme begins.
Our whitepaper, The Hidden Operational Complexity of Acquisition, explores how financial services organisations can identify inherited operational friction, understand its root causes and create simpler foundations for future transformation, technology and AI.
Download The Hidden Operational Complexity of Acquisition to explore the approach in more detail.
If you'd like to continue the conversation around operational debt, acquisition complexity and financial services transformation, you can also connect with Dafydd on LinkedIn.