Leading Through Uncertainty: What Really Happens During M&A Integration

M&A transactions are built on models.

Before a deal closes, leaders develop financial models, synergy assumptions, integration assumptions and roadmaps. Together, these create a sense of certainty about how the combined organisation will operate and where value will be realised.

However, the reality of integration is rarely as predictable and straightforward as the deal model suggests. Decisions must be made with incomplete information, previously disguised dependencies begin to emerge, key people react in unexpected ways and operational priorities continue to change. Technology, customers and regulatory obligations introduce further complexity. These are not necessarily signs of poor planning; they are features of integrating two (or more) organisations that were not previously designed to operate as one.

The success of an acquisition is therefore not determined solely by the quality of the original deal model or the integration plans; it is dependent on the organisation’s ability to recognise, understand and manage uncertainty after the deal closes and throughout the integration process.

Why uncertainty is unavoidable

Uncertainty in M&A (Mergers and Acquisitions) integration is the gap between what leaders believe will happen and what actually emerges as the organisations are brought together. Uncertainty cannot be eliminated through more detailed planning because, before completion, the integration team does not possess all the information needed to understand how the business operates. Some information may not be available because of confidentiality restrictions. Other issues only become visible once the integration workstreams begin operating across organisational boundaries. Decisions or changes that appear straightforward within an individual function can create unexpected consequences elsewhere. A change to a system, process or role may negatively impact customers, regulatory obligations, reporting requirements or another part of the operating model.

The purpose of integration management is therefore not to remove uncertainty. It is to identify it early, understand how it moves across the organisation and create an integration programme capable of responding when reality differs from the original integration thesis.

Across M&A integrations, uncertainty consistently emerges in six interconnected areas: the integration plan, people, technology, customers, operational reality and leadership and decision-making. Each area creates its own challenges, but changes in one will often have consequences across several others.

Six areas of uncertainty:

The myth of the perfect plan

Integration planning is essential.

But even the most detailed plan is based on theories and assumptions made at a particular point in time. It reflects the information available before close, the priorities understood at that stage and an anticipated view of how the two (or more) organisations will strategically fit together. It cannot fully represent the operational reality that will emerge once integration begins.

Plans are often treated as finite, fixed commitments rather than working hypotheses. This can create false confidence and discourage teams from questioning assumptions when new information becomes available. Hidden dependencies, changing stakeholder expectations and conflicting priorities require the original plan to be updated to reflect the new information. A strong integration plan should provide direction without creating rigidity. Leaders must be clear about the intended outcomes of the acquisition while remaining prepared to change the route used to achieve them. Adaptation is not evidence that the plan has failed; it is a necessary response to greater knowledge and may lead to a better outcome. Integration planning is an iterative process.

People: the biggest unknown

An organisational chart provides names, roles and reporting lines. It does not show how the organisation really operates. Informal relationships, individual influence, trust, institutional knowledge and the people who resolve problems outside formal processes are largely invisible before integration begins.

This creates significant uncertainty. Key employees may leave before retention plans are activated, while others may remain but become disengaged. Uncertainty surrounding roles, reporting lines and future opportunities can reduce productivity and increase resistance. Cultural differences that appeared manageable during due diligence may become more pronounced when teams across the businesses are required to make decisions and work together. Integration decisions can also unintentionally remove the people who hold critical knowledge or maintain important relationships. Leaders must therefore look beyond job titles and organisational structures. Understanding who people rely on, where knowledge sits, and how work is actually completed is essential before roles, processes or reporting lines are changed. The people plan should evolve as these dependencies become visible.

Technology: more than a systems challenge

Technology integration is often presented as a sequence of system migrations, data transfers and application rationalisation. In reality, the technological landscape is rarely fully understood before close. Legacy systems may support critical processes through undocumented workarounds and the connection between systems, data and operational activity may only become visible when changes are attempted.

Incomplete or inconsistent data can delay migrations and undermine decision-making. Cybersecurity vulnerabilities may emerge during integration, particularly when access arrangements change or previously separate networks are connected. Transitional Service Agreements (TSAs) can create further uncertainty where critical services remain dependent on the seller, third-party providers or shared infrastructure for longer than anticipated.

Technology decisions therefore cannot be made in isolation. Retiring, replacing or integrating a system can affect employees, customers, financial reporting and regulatory compliance. Integration leaders need visibility of the technological architecture, the operating model and the business processes that the systems support. Dependencies should be mapped and tested before systems are changed, with contingency and roll-back plans available where the operational impact remains uncertain.

Customer uncertainty

During integration, leadership attention naturally turns inwards. Teams focus on organisational design, systems, processes and governance. However, customers continue to expect consistent communication, service and relationship management throughout the change.

Uncertainty can emerge when customers receive conflicting or incomplete messages about the acquisition. Changes to products, services, account managers, or delivery processes may create confusion or concern, even when the intention is to improve the customer experience. Service disruption may also occur when employees are distracted by integration activity (such as technological changes to customer-facing systems) or unclear about new responsibilities.

Customer relationships can be particularly vulnerable where they depend on specific individuals. If those employees leave or their roles change, valuable knowledge of the customer and trust may be lost. Sales teams may also become focused on internal decisions at the expense of maintaining the external relationships that bring in revenue.

Customer impact should therefore be assessed as part of every significant integration decision. Leaders need to understand what will change, which customers may be affected and how relationships and service continuity will be protected while the organisation transitions.

Operational reality

The integration plan describes how the combined organisation is expected to operate. Operational reality reveals whether that design is achievable. Once integration begins, teams frequently discover that governance arrangements, processes, controls and responsibilities are less consistent or clearly defined than anticipated.

A Target Operating Model (TOM) can provide a valuable view of the intended future organisation, but it does not automatically explain how either business operates today.

Processes may be undocumented, responsibilities may overlap and key controls may depend on individuals rather than on formal governance. Data may also be held across different systems, interpreted differently by each organisation, or in some cases still with the seller. Regulatory and compliance obligations introduce additional layers of complexity. Different entities, products and jurisdictions may be subject to different requirements, while seemingly straightforward integration decisions can create unintended regulatory consequences.

Integration leaders must therefore establish the current operational reality of both organisations before deciding how they should fit together. This means looking beyond documented processes and understanding how work is actually performed, where decisions are made and which dependencies must be maintained during transition. The Target Operating Model should then evolve as this knowledge becomes available.

Leadership and decision-making under uncertainty

Leadership during integration requires decisions to be made before the full picture is available.

Delaying every decision until uncertainty has been removed is unrealistic, but moving too quickly without understanding the consequences can create further disruption across the programme.

Many executives will lead only a small number of integrations during their careers. They may be experienced business leaders without having extensive integration experience. At the same time, they remain responsible for running the existing business and managing competing operational priorities. Integration therefore competes for limited leadership attention at precisely the point when clear direction and timely decisions are most important.

The absence of an agreed Target Operating Model can increase this uncertainty. Without a clear view of the intended future organisation, workstreams may make decisions independently and create conflicting outcomes. Governance can also become ineffective where there are too many meetings, unclear decision rights or issues that repeatedly move between forums without resolution.

Effective leadership does not require certainty. It requires leaders to establish a clear strategic direction, define who has authority to make decisions and remain open about the assumptions and risks informing decisions.

What successful integration programmes do differently

Successful integration programmes do not attempt to eliminate uncertainty. They create the visibility, governance and flexibility needed to manage it. In practice, five actions are particularly important:

• Define the strategy. Leaders should communicate both the strategic rationale for the acquisition and the integration strategy. The programme needs to understand not only what the rationale for the deal was, but how the organisations will be brought together to achieve that outcome.

• Maintain programme-wide visibility. Integration leaders need oversight across all workstreams so that emerging issues and changes are not managed in isolation.

• Map dependencies. Dependencies and interdependencies should be identified across the entire integration programme, not only within individual workstreams. A decision made by one function may alter the plans, risks or timelines of several other workstreams.

• Make risks transparent. Risks should be documented, visible and actively mitigated. Uncertainty becomes more dangerous when teams feel unable to raise concerns or when risks remain hidden within individual workstreams.

• Build adaptability into the programme. Contingencies should be considered from the beginning. Integration plans must provide direction while allowing the programme to respond when assumptions change or new information emerges.

Conclusion: managing rather than eliminating uncertainty

Uncertainty is not evidence that an integration has been poorly planned. It is an inevitable consequence of bringing together organisations with different people, systems, processes, customers and ways of operating. The limitations of the original plan only become visible as the integration progresses and greater knowledge becomes available.

Successful integration therefore requires more than delivering against a fixed roadmap. It requires programme-wide visibility, transparent risk management, clear leadership and an understanding of the dependencies connecting each area of the organisation. Plans must be sufficiently stable to provide direction but adaptable to respond to operational reality.

The success of an acquisition is not determined solely by the quality of the deal model. It is also determined by the organisation’s ability to navigate uncertainty after the deal closes whilst remaining focused on the strategic outcome the acquisition was intended to achieve.

In summary, uncertainty cannot be eliminated. It can only be identified, understood and managed.