On paper it was one company. In day-to-day operations, it was still two.
The combined organisations operated in related business fields, but differed in their priorities, customer structures and operational ways of working.
After the merger, employees and functions had moved closer together organisationally. However, the actual operational integration had not been carried through consistently enough in many areas.
People from both organisations worked alongside one another without processes, responsibilities, systems and common standards having been fully redefined.
A merger does not resolve differences simply because people subsequently work under the same company name.
Operational integration planning must begin before the organisations are brought together.
From my perspective today, successful integration begins with planning well before the operational combination. The financial view is only one part of the overall picture.
Equally important – within the applicable legal framework – is a realistic picture of the operating organisation: What capabilities do employees have? Who are the key people? Which functions are actually needed? Where are the overlaps? Which processes work well? Which systems support the business – and which do not?
Understand capabilities, key people, responsibilities and critical knowledge.
Look beyond cost to operational capability, interfaces and required capacity.
Analyse overlaps, different services, contacts and potential.
Understand the strengths and weaknesses of both organisations before common standards are defined.
Especially when two companies come from a similar market environment, there is a risk of underestimating the differences. Similar services do not automatically mean identical processes, capabilities or customer requirements.
After a merger, there needs to be a clear picture of how the new company is meant to operate.
Simply placing two existing organisations together does not create a robust new structure. Responsibilities need to be reconsidered and made visible.
Who owns which task? Which functions are combined? Where do different business logics still make sense? Which management levels are needed? Who decides what?
Temporary duplicate structures can make sense during transition phases if they preserve knowledge and enable an orderly handover. What matters is that there are clear tasks, criteria and a target state.
A common organisation chart is not an administrative detail. It is the visible answer to the question: who is responsible for what in the new company?
Integration has to become visible in day-to-day operations.
A substantial part of my work therefore consisted of completing structures and standards. This included the introduction of a common IT system as well as clear documentation of processes, responsibilities, security requirements and organisational workflows.
An external certification requirement was useful because it forced us to document many points systematically and make them binding: processes, responsibilities, organisation chart, security topics and operational standards.
The certificate itself was not the important part. What mattered was that partly informal or differently practised routines became one common way of working.
With overall operational responsibility, I continued the organisational and operational integration: introducing a common system, establishing clear responsibilities, documenting processes and standards, and gradually standardising the operating organisation.
A new company also needs to look like a new company.
Even after the merger, old logos, names and other elements of the predecessor organisations were still present. It was therefore clear to me that these visible remnants needed to be replaced consistently.
This included a consistent website, revised materials, uniform templates, signage and work equipment. Visible elements like these are also part of integration.
At first glance, this may look like branding. In reality, it is also organisational work. As long as employees are constantly confronted with old names, old logos and former affiliations, the past remains present in everyday operations.
At some point, “we from before” and “they from before” need to become a shared “we” – and that new company has to be visible.
People cannot simply be merged organisationally.
A merger is always emotional for employees as well. Questions arise about status, responsibility, jobs, leadership and the future. Added to this are different habits and the natural tendency to view one’s former organisation positively.
That is precisely why integration must not be reduced to distributing new organisation charts. Leaders and selected key people need to be involved early. Processes and decisions should be explained. Workshops and joint team formats can help make differences visible and turn them into shared standards.
In my view, a leader who is not emotionally associated with either predecessor organisation can be particularly useful in such a situation. Decisions can then be made more from the perspective of the future company and less from the logic of either former camp.
After a merger, the question cannot permanently be: Which of the two companies did it better before? The question must be: What does the combined company need going forward?
Attrition is not an integration strategy.
Anyone who hopes that staffing overlaps will resolve themselves through voluntary resignations loses control of the integration process.
High-performing employees are often particularly quick to decide whether they want to remain in an uncertain organisation. What appears to be a reduction in personnel cost can therefore turn into the loss of customer knowledge, experience and operational capability.
It should therefore be assessed early which capabilities the future company needs, who holds critical knowledge and how responsibilities should be distributed in the target organisation.
People decisions are part of a merger. They should, however, result from deliberate organisational decisions – not from uncontrolled developments.
Customers also need to understand what the merger has created.
Another weak point was external communication. In some cases, customers did not have a sufficiently clear understanding of how the company had changed. Former names remained in circulation and the combined service structure was not explained clearly enough.
A merger should create a tangible benefit for customers: a broader service portfolio, additional capabilities, more resources or better geographic coverage.
These benefits need to be communicated actively. That includes early information, clear points of contact, customer visits, an up-to-date shared market presence and a clearly described service portfolio.
Identify shared customers, overlaps and different relationships early.
For every relevant customer, it must be clear who will lead and make decisions going forward.
The combined service offering needs to be clearly described internally and externally.
Customers and partners need to know what is changing – and what benefit that change brings.
A merger should not be explained to customers as an organisational event, but as a tangible improvement in the service offering.
The small remnants of the past often reveal how far integration has really progressed.
As integration progressed, it became apparent that some formal documents and permits were still held under former company names.
Such details may initially appear minor. However, they show that integration has not been fully completed.
Contracts, permits, licences, insurance documents, safety documentation, templates, policies, company data and other formal documents therefore belong in a structured integration plan.
After a merger, a company should not carry organisational traces of its predecessors for years if they no longer serve any function in the new business model.
In many areas, a merger should be approached like the creation of a new company.
For me, this is the most important conclusion from the experience.
Do not simply decide which of the two legacy solutions wins. First ask what the future company actually needs.
What organisation? Which processes? Which IT system? Which standards? Which identity? Which leadership? Which customer structure? Which services? Which rules?
Of course, not everything has to be reinvented. Good solutions from both predecessor organisations should be retained. But the selection needs to be made from the perspective of the future company – not out of loyalty to the past.
A merger should not preserve two old companies. It should use their strongest capabilities to build a better combined organisation.
Integration only creates value when it actually works in the business.
The economic logic of a deal is not realised in the contract. It is realised in day-to-day operations afterwards.
Two companies need to be deliberately turned into a new one.
A merger is a financial and legal transaction. The real integration work begins, at the latest, when people, processes, systems and customer relationships have to be brought together.
In my experience, it is not enough to combine structures, select systems and define new reporting lines. The future company needs its own organisation, shared standards and a recognisable identity.
People need to be involved early without avoiding necessary decisions. Customers and partners need to be part of the integration plan just as much as IT, processes, governance and organisation.
The later these decisions are made, the longer the company continues to operate with duplicate structures, uncertainty and unnecessary friction.
When the merger has been formally completed, but integration in the business is still not working.
Brueggemann Interim assumes operational leadership responsibility on an interim basis when responsibilities, processes, systems and day-to-day management still do not work together reliably after a merger.