A merger or acquisition can be completed on paper relatively quickly. Integrating two organizations is a very different challenge.
Once the transaction is complete, leaders often find themselves dealing with questions that were only partly visible during the deal itself.
- Who makes which decisions now?
- Which processes should remain in place?
- Where do responsibilities overlap?
- Which systems should be combined?
- How should leaders communicate changes to employees?
- And perhaps most importantly: How do two organizations actually start operating as one?
This is where post-merger integration becomes less of a transaction question and more of an organizational management challenge.
The GRIFFOX Layered Cake Model™ was not developed specifically as an M&A methodology. However, its layered and interconnected structure can provide a practical framework for managing the organizational side of post-merger integration.
Post-Merger Integration Is More Than Combining Structures
One of the risks after a merger or acquisition is treating integration primarily as a technical exercise.
Organizational charts are combined. Systems are migrated. Policies are aligned. Reporting structures are updated.
All of these activities may be necessary.
But successful post-merger integration usually reaches much further.
Two organizations may have different leadership styles, decision-making processes, customer expectations, internal routines, cultures, systems, performance measures, and ways of communicating.
Even when the future structure looks clear on paper, employees still have to understand it, accept it, and work within it.
That is where integration often becomes difficult.
- Responsibilities can remain unclear.
- Decisions can take longer because nobody is certain where authority sits.
- Teams may continue using their previous processes.
- Employees may receive different messages from different leaders.
- Integration projects may compete with day-to-day operations.
And leaders may underestimate how much organizational coordination is required simply to keep the business functioning while the integration is taking place.
Post-merger integration therefore should not be viewed as one isolated project.
It is usually a collection of interconnected organizational changes.
A Layered Approach to Post-Merger Integration
The GRIFFOX Layered Cake Model approaches organizational change through five interconnected layers:
- Goal
- Recalibration
- Implementation
- Framework
- Foundation & Experience
Each layer serves a different purpose, but none of them operates independently.
In post-merger integration, this becomes especially important because decisions made in one area almost always affect another.
- Changing the organizational structure may affect leadership responsibilities.
- Changing leadership responsibilities may affect decision-making.
- Changing processes may affect technology requirements.
- Changing technology may affect employees and customers.
The purpose of the layered approach is therefore not to make integration look simpler than it is.
It is to make that complexity more manageable.
Goal: What Does Successful Integration Actually Mean?
The first question in post-merger integration should not simply be:
“How do we combine these two organizations?”
The more important question is:
“What should the integrated organization be able to accomplish?”
Different transactions may require very different answers.
For one organization, successful integration might mean creating a single operating model.
For another, it might mean preserving strong local operations while combining certain corporate functions.
Other organizations may focus primarily on achieving synergies, strengthening leadership, improving geographic coverage, integrating capabilities, reducing duplication, or creating a stronger customer experience.
The goal has to become specific enough to guide decisions throughout the integration process.
Without that clarity, individual integration activities can easily move in different directions.
- One team focuses on cost reduction.
- Another focuses on employee retention.
- Another standardizes processes.
- Another protects local autonomy.
All of those objectives may be reasonable, but they need to support a shared picture of what successful integration looks like.
The Goal layer creates that orientation.
Foundation & Experience: Understand What You Are Actually Integrating
Before leaders redesign an organization, they need to understand what already exists.
This sounds obvious, but it can easily be overlooked after an acquisition.
There may be an assumption that the acquiring company’s processes, structures, or systems should automatically become the standard.
Sometimes that may be the right decision.
Sometimes it may not.
Both organizations bring existing experience, capabilities, relationships, processes, risks, strengths, weaknesses, and cultural patterns into the integration.
A strong post-merger integration process therefore starts with understanding the organizational foundation.
This can include areas such as:
- organizational structures;
- leadership responsibilities;
- key processes;
- technologies and systems;
- customer relationships;
- employee capabilities;
- internal communication;
- decision-making practices;
- organizational culture;
- operational risks;
- existing improvement initiatives.
This assessment should not be limited to formal documentation.
How an organization officially works and how it actually works are not always the same.
Leadership interviews, employee input, process observations, performance data, customer feedback, and operational experience can all provide important insights.
The Foundation & Experience layer helps leadership understand the starting point before determining what should change.
Framework: Build the Management Structure for Integration
Once the organization understands where it wants to go and where it is starting from, the next question becomes:
How will the integration actually be managed?
Post-merger integration frequently involves multiple workstreams operating at the same time.
- Finance may be integrating systems.
- Human Resources may be aligning policies.
- Operations may be standardizing processes.
- IT may be consolidating platforms.
- Leadership may be redesigning reporting relationships.
- Communications may be supporting employees and customers.
Without a clear framework, these activities can easily become disconnected.
The Framework layer focuses on the management structures needed to coordinate the work.
Depending on the size and complexity of the integration, this might include:
- integration governance;
- clearly defined leadership responsibilities;
- decision rights;
- integration workstreams;
- escalation mechanisms;
- project and change management structures;
- risk management;
- communication routines;
- performance indicators;
- milestones and review cycles.
This is also where leadership needs to make an important distinction:
Not everything has to become identical.
Integration Does Not Always Mean Standardization
One of the most important questions during post-merger integration is:
What must become consistent, and what should remain different?
Standardization can create efficiency, consistency, and easier governance.
But unnecessary standardization can also destroy capabilities that made the acquired organization valuable in the first place.
- A local customer-service model may work extremely well because it reflects the expectations of a particular market.
- A smaller organization may have faster decision-making practices worth preserving.
- A specialized team may use a process that performs better than the acquiring company’s existing approach.
The purpose of integration should therefore not automatically be to make every location, department, or business unit work exactly the same way.
Leadership needs to determine where consistency protects the organization and where flexibility creates value.
That decision belongs within the integration framework.
Implementation: Turn the Integration Plan Into Everyday Operations
Eventually, every integration plan has to leave the conference room.
This is where post-merger integration becomes real.
- Employees begin reporting to different leaders.
- Processes change.
- Systems are replaced.
- Responsibilities move between departments.
- Policies are updated.
- Teams are reorganized.
- Customers may encounter new points of contact.
This is also where some integration efforts begin to lose momentum.
- A decision may have been made, but that does not mean it has become part of everyday operations.
- A new process may exist, but employees may still use the old one.
- A leadership structure may have been announced, but decision rights may remain unclear.
- Training may have been delivered, but behaviors may not have changed.
The Implementation layer therefore focuses on the transition from design to operational reality.
That requires more than completing integration tasks.
It requires attention to adoption, ownership, communication, leadership behavior, process effectiveness, and the practical experience of employees working within the new organization.
The central question becomes:
Is the integration actually working where the work happens?
Recalibration: Integration Rarely Follows the Original Plan Exactly
Even a carefully planned integration will produce unexpected results.
Some assumptions prove correct.
Others do not.
- A process that looked efficient on paper may create problems once implemented.
- A leadership structure may generate bottlenecks.
- A technology migration may take longer than expected.
- Customers may react differently than anticipated.
- Employees may identify risks leadership did not initially see.
This is why reflection and recalibration are an essential part of the GLCM.
Post-merger integration should include regular opportunities to compare intended outcomes with actual results.
This may involve reviewing:
- operational performance;
- integration milestones;
- employee feedback;
- leadership alignment;
- customer experience;
- process performance;
- workforce stability;
- unresolved responsibilities;
- emerging risks;
- expected synergies.
The purpose is not simply to determine whether tasks have been completed.
The more important question is whether the integration is producing the intended organizational result.
If it is not, leadership needs to adjust.
That may mean changing priorities, modifying processes, clarifying responsibilities, revisiting assumptions, or slowing one integration activity to stabilize another.
Recalibration should not be viewed as a sign that the original plan failed.
It is part of responsible integration management.
The Layers Have to Work Together
The value of the GLCM in post-merger integration is not found in treating the five layers as separate steps.
They continuously influence one another.
- New information discovered during implementation may change the understanding of the organizational foundation.
- A change in strategy may require the integration goal to be revised.
- Employee feedback may reveal that part of the framework is not working.
- Operational performance may require leadership to recalibrate the implementation approach.
This interaction is particularly important during mergers and acquisitions because the organization continues operating while integration is taking place.
- Customers still expect service.
- Employees still have daily responsibilities.
- Leaders still have to make decisions.
The business cannot simply stop until the integration is complete.
A layered approach helps leadership maintain a connection between long-term integration goals and the realities of everyday operations.
When Post-Merger Integration Starts to Stall
Not every organization begins integration with a structured approach.
Sometimes several months have already passed before leaders realize that progress is slowing.
The organizational structure may technically be integrated, but departments continue working separately.
- Employees may still identify primarily with the previous organizations.
- Projects remain unfinished.
- Responsibilities overlap.
- Leadership spends increasing amounts of time resolving exceptions.
The same issue may be handled differently across locations.
Decisions may move slowly because authority is unclear.
At this stage, the solution is not necessarily to create another integration plan.
The more useful starting point may be to assess where the integration has become disconnected.
Is the goal unclear?
Was the organizational foundation insufficiently understood?
Is the governance structure weak?
Has implementation failed to create ownership?
Or has the organization continued executing a plan that needs to be recalibrated?
Looking at the integration through these layers can help leadership identify where additional attention is required.
Post-Merger Integration Is an Organizational Change Challenge
Mergers and acquisitions are often discussed in terms of transactions, valuation, financial performance, and expected synergies.
Those elements are important.
But after the transaction closes, leadership faces another challenge:
Two organizations have to function together.
That requires changes in leadership, structure, systems, processes, responsibilities, communication, and behavior.
The GRIFFOX Layered Cake Model does not replace the financial, legal, or transaction-related disciplines involved in M&A.
Its role is different.
It provides a management architecture for the organizational change that follows.
By connecting the desired outcome with the organizational foundation, management framework, implementation, and continuous recalibration, leaders can approach post-merger integration as more than a collection of projects.
They can manage it as an interconnected organizational transformation.
Because closing the transaction may complete the deal.
But it does not complete the integration.
By Harald Lavric | Founder, GRIFFOX Consulting | Creator, GRIFFOX Layered Cake Model™
About Harald Lavric
Harald Lavric is the founder of GRIFFOX Consulting and creator of the GRIFFOX Layered Cake Model™. His work focuses on the connections among leadership, strategy, organizational change, operational responsibility, and enterprise decision-making. Drawing on more than three decades of experience in the German health-insurance system and work across public- and private-sector environments, he helps leaders make overlapping change more coherent and workable.
About Harald Lavric | Explore the GLCM | Contact GRIFFOX
Alternative Site Links
Insights — https://griffoxconsulting.com/insights/
The GRIFFOX Layered Cake Model — https://griffoxconsulting.com/griffox-layered-cake-model/
GLCM Enterprise Change Architecture — https://griffoxconsulting.com/glcm-enterprise-change-architecture/
Consulting — https://griffoxconsulting.com/leadership-strategy-consulting/
About Harald — https://griffoxconsulting.com/harald-lavric/
Contact — https://griffoxconsulting.com/contact-griffox-consulting/