Most acquirers treat integration as a march towards total harmonisation. The same systems, same processes, same everything. As M&A shifts from volume to value, that assumption deserves a second look.

If the whole organisation works in one standard way, who gets to try something new? Who innovates? And who decides when the standard approach doesn’t fit the local market?

In practice, that means everyone on the same system, the same salary bands and the same client pitch. The word “integrated” has come to mean “identical”.

When you’re producing physical objects… spanners, cars, microchips… there are obvious benefits from standardisation. Quality improves. Costs fall. Speed increases. The same logic applies to software development: one platform, fewer lines of code, less duplication. These are real gains, and they come from everyone doing the same thing in the same way.

But people are not spanners. Not everyone in your organisation has the same skills, the same client base, the same competitive landscape, or the same market dynamics. A single way of doing things may be, at best, the least worst option for everyone.

A single way of doing things may be, at best, the least worst option for everyone.

The accountability problem

Now add three concepts that every organisation values: accountability, ownership, and innovation.

A managing director in a regional business, told what to do by global functions in the group, loses accountability. When they can’t adapt to their local market, or try new things, they lose ownership. Who has to give approval if they want to try something new (a different pricing approach, a different way of packaging their services)? How long does that take?

Innovation doesn’t happen naturally in a fully standardised organisation. It happens by exception, fighting its way through committees and change-control processes that exist precisely to protect the standard. The people closest to the client, closest to the market, end up spending their energy seeking approval rather than creating value.

And here’s the problem on the other side: if nothing is defined and nothing is standard, you’re not integrated at all. You are just a collection of businesses under the same letterhead. So the real question is where to standardise, and why.

Make every initiative earn its place

Most integration plans start from the assumption that the goal is full harmonisation, and then carve out exceptions where they’re forced to. We’d suggest flipping that entirely:

Start from no harmonisation, and ask each integration initiative to articulate how it creates value.

That single shift changes the conversation. It forces every group function to articulate the value it creates. It gives local teams a legitimate basis to push back.

The obvious objection is that some areas should not need a value case. Surely IT should be allowed to fully harmonise without having to justify it? Cybersecurity, email and financial reporting feel self-evident.

Perhaps. But even here, the discipline of making the case is useful. It makes the action intentional. It forces people to understand their role in the broader organisation. And it helps with prioritisation.

Measure what matters

A good test of whether harmonisation is delivering value is whether you can name a measure that improves as a result. That measure should be an outcome, such as revenue, margin or client retention, rather than a count of how many people follow the process.

If everyone can agree an improvement in a specific measure improves the performance of the overall organisation, you are on the right track. If the only thing you’re measuring is whether people are doing what they’re told, you’re not integrating. You’re controlling.

Integration is connection

For some people, integration means everyone following the same process flow diagrams to the letter, globally, dealing with every eventuality in a prescribed way. That’s not what creates value.

A well-integrated business is not one where everyone does everything the same way. It’s one where everyone understands the value they’re creating, has the tools and the freedom to create it, and is genuinely connected to the broader organisation.

In our interim and consulting work, the integrations that last are the ones where every standard has a reason behind it.

Eton Bridge Consulting is a team of senior experienced practitioners who guide, and where needed, stay to deliver the results. If you are integrating a recent acquisition, or deciding where to standardise and where to give local teams room to lead, we would welcome the conversation.