Skip to searchSkip to main content

Operations

Transactions Have Closing Dates. 
Operations Don't.

Two gears working together

What COOs need to protect while ownership, 
leadership, and the operating model are changing


Mergers and acquisitions are often discussed through the transaction: strategy, valuation, diligence, financing, negotiation, signing, closing, and synergy targets.

All of those things matter.

But from inside the operating business, the transaction is only part of the story. Customers still expect service. Employees still need decisions. Technology still has to work. Cash still matters.

The business does not stop operating because ownership is changing.

I learned that from the operating side of an acquisition.

Earlier in my career, I worked inside a small company that moved through executive and ownership disruption, financial distress, bankruptcy, acquisition, stabilization, rebuilding, and expansion.

I was not involved in valuation, financing, legal work, transaction negotiations, or deal structure. My responsibility was on the operating side: keeping the business functioning, adapting operating capabilities, making day-to-day decisions during leadership disruption, transferring knowledge as new leadership came in, and helping prepare the organization for its next stage of growth.

That experience changed how I think about M&A.

The transaction changes who owns the business. Integration changes how the business operates.


Operating Risk Can Begin Before the Transaction

Not every acquisition begins with a healthy organization preparing for new ownership. Strategic disagreement, leadership instability, capital constraints, and unclear priorities can affect execution long before a transaction begins. By the time ownership changes, the organization may already be operating under considerable strain.

This is where the strength of the existing operating system becomes important.

Standard work, clear ownership, reliable information, trained people, and documented knowledge may look like ordinary operating discipline during stable periods.

Under pressure, they become continuity mechanisms.

For a COO, the lesson is that operational resilience cannot begin with an integration plan. It must already exist within the organization's operating practices.

When leadership changes, those capabilities provide a foundation for maintaining execution while new responsibilities and priorities are established.


Decision Rights Cannot Disappear

Leadership turnover creates more than an organizational chart problem.

It creates a decision problem.

During one period of severe organizational disruption in my career, the formal leadership structure became extremely thin. Employees still needed answers, customers still had problems, and technical and operating work still had to move.

I became a central point for many operating decisions, coordinating priorities, resources, workflows, customer issues, people issues, and cross-functional needs while reporting upward to board-level leadership.

That was not a formal COO appointment, and I was not managing the acquisition transaction. But it taught me something directly relevant to the COO role:

Responsibility without decision rights creates paralysis, while decision rights without operating knowledge create risk.

When leadership changes, authority and operating knowledge do not necessarily transfer together. Incoming leaders may have decision-making authority without fully understanding the dependencies behind those decisions. Meanwhile, employees who understand those dependencies may lack the authority to act.

That gap creates risk.

A COO must establish clear interim decision rights, escalation paths, and knowledge-transfer responsibilities while the future leadership structure is being developed. The goal is not to preserve the old structure indefinitely. It is to prevent uncertainty about authority from interrupting execution.

The future organization chart matters. So does knowing who can make a decision today.


Stabilization Does Not Mean Standing Still

There is a natural temptation during distress or acquisition to freeze change until the transaction is complete.

Sometimes that is appropriate.

Sometimes waiting creates more risk.

A failing process, unstable technology, or unresolved quality problem does not become less important because ownership is changing. The challenge is determining which changes protect the business and which introduce unnecessary disruption.

The better question is not, “Should we change anything?”

It is: What must remain stable, what must change now, and what should wait?

That is a COO judgment call.

McKinsey reported that 72% of ultimately successful mergers maintained organic growth during the first year, compared with 33% of unsuccessful deals.¹

The research reinforces an important operating principle: integration cannot come at the expense of the business's ability to perform.

For a COO, stabilization means maintaining enough control, visibility, and operating discipline to make deliberate decisions while the organization changes. Stabilization is controlled change.


Understand the Capability Before You Change It

Acquirers face a difficult balance. Preserve too much and the organization may carry forward weaknesses the transaction was intended to address. Change too much too quickly and the acquirer may destroy useful capability before understanding it.

The answer is not blind preservation. It is diagnosis.

A process that appears inefficient may contain valuable institutional knowledge. A technology platform may have limitations while supporting critical customer workflows. An experienced employee may understand dependencies that are not documented anywhere.

Removing those elements without understanding their purpose can create problems that were not visible during planning. Before making significant changes, leadership needs to understand how the work actually gets done. That means examining processes, performance data, technology dependencies, decision paths, and the people who hold critical operating knowledge.

I believe four questions provide a practical framework for those decisions:

Protect:What must keep working because disruption would damage customers, cash, safety, compliance, or deal value?

Integrate: What becomes stronger when processes, systems, governance, or resources are connected?

Transform: What must fundamentally change because the current model cannot support the strategy, economics, customer needs, or future scale?

Retire: What are we preserving only because it already exists, even though its cost, risk, or complexity no longer justifies it?

These are different operating decisions, each with its own timing and risk. A process may need to change without destroying the capability behind it. Institutional knowledge may need to transfer without preserving dependence on the individual who holds it. The COO's responsibility is to understand those distinctions and sequence the changes accordingly.


Protect Today's Business While Building Tomorrow's

The real test of integration is not simply whether the organization survives the transition. It is whether the organization becomes capable of operating successfully under what comes next.

The COO sits at an unusual intersection during that transition.

The board and investors are looking at value. The CEO is looking at strategy and organizational direction. Finance is looking at economics, cash, controls, and performance. Functional leaders have integration requirements. Employees want clarity. Customers want continuity. The COO has to connect those perspectives through the operating system.

That requires understanding which capabilities create value, which decisions cannot wait, and how changes in one part of the organization affect the others.

It also requires recognizing that integration is not complete simply because reporting structures, systems, or processes have been combined.

The organization must be capable of delivering consistent performance under its new operating model.

The transaction can create the opportunity for value. Operations still has to convert that opportunity into performance.

The deal can close in a day. Building the organization that can deliver the deal's value takes longer.

Transactions have closing dates. Operations don't.


Source

¹ McKinsey & Company. In conversation: Four keys to merger integration success. October 12, 2022. Interview with Brian Dinneen, Christine Johnson, Alex Liu, and Becky Kaetzler, conducted by Sean Brown.


Kevin VanSlooten

Kevin VanSlooten is an Executive Business & Operations Leader and Lean Six Sigma Black Belt with nearly 30 years of experience spanning business ownership, manufacturing, technical operations, and technology-enabled services. His background includes scaling organizations, building operational capabilities, and leading cross-functional improvement initiatives. He focuses on operational excellence, organizational effectiveness, leadership development, and building sustainable operating systems that support business growth. Kevin is a COO Forum Associate member.


COO Forum Peer Membership