The work after the acquisition.
A transaction can make sense financially and still create a difficult operating reality. Once an acquisition closes, employees need practical answers. Who approves a purchase? Will payroll run as expected? Which policies apply? Who can resolve an issue when the old process no longer works?
My work across more than 40 acquisitions reinforced how much depends on those details. The business case creates an expectation of value. Integration is where people have to make that expectation work.
I approach that responsibility with a clear priority: understand what must be ready, assign ownership and give employees a dependable path through the change.
Start the work before closing.
Due diligence should help shape the integration plan. Collecting documents has limited value if no one turns the findings into decisions.
If a benefit arrangement requires action, a vehicle agreement has transfer conditions or a payroll process depends on one person's knowledge, the integration team needs to understand the issue before it becomes an operational surprise. Each open item needs an owner, a next step and a clear explanation of what depends on its resolution.
I also want the team to distinguish confirmed facts from assumptions. “The vendor should be able to handle it” is a question to resolve. A plan becomes more useful when it records what has been verified, what is still open and who has the authority to decide.
Make the first day dependable.
Employees may have understandable concerns about the future. We add to that uncertainty when basic processes are confusing or unreliable.
Payroll, benefit coverage, access to essential systems, safety responsibilities and reporting relationships deserve focused preparation. Their transition dates may differ, so the team needs to understand how they fit together. An announcement that everything is complete means very little to someone who cannot access the tools needed to work.
I favor a practical readiness review. What must function when the business opens? Who has checked it? What happens if it fails? Who can employees contact for an answer? The level of detail should reflect the operation and the consequences of getting it wrong.
Learn before replacing what works.
Acquired organizations bring knowledge, relationships and operating practices worth understanding. I do not assume the acquiring company's approach is better simply because it is the established standard.
Some changes need to happen quickly to support consistent controls or dependable operations. Others deserve a closer look. A local team may have a better customer handoff, a stronger scheduling practice or useful expertise that would be easy to lose during a hurried conversion.
I want leaders to be clear about why a change is needed and open to evidence about how to implement it. Listening to the acquired team improves decisions and helps identify the people who will be essential to making the transition work.
Communicate what people can act on.
Employees need more than enthusiasm about the combined organization. They need to know what is changing, when it affects them and where to go with questions.
I would rather say that a decision is still being evaluated, identify who owns it and commit to the next update than offer reassurance we cannot support. Managers need that same information so employees receive consistent answers.
Communication also needs a way back to the integration team. Repeated questions, workarounds and unresolved concerns can show where the plan has missed something. They should inform the next decision.
Carry the work through to ownership.
The first 90 days provide useful milestones, but a date alone does not establish that integration is complete. Open items need to stay visible until they are resolved or deliberately accepted by the appropriate leader.
Permanent owners should understand the processes, recurring obligations and unresolved risks they are receiving. Otherwise, the integration team remains an unofficial help desk long after it should have handed over responsibility.
I judge progress by whether people can do their jobs, leaders understand their authority and the combined organization can operate without constant escalation. That is the point at which a transaction begins to become a functioning organization.