Your integration plan is probably fine. That is the problem. A plan can be accurate on every line and still fail, because the people who have to act on it were never moved to act.
Post-merger integration change management is the work of getting real people to do real things differently, while they are worried about their jobs. Most integration failures I have seen were adoption failures. The system was installed. The people kept using the old one. The synergy was in the model and never in the P&L.
ADKAR in one minute
ADKAR is a change model from Prosci. It says a person changes through five steps, in order, and that the change stalls at the first step that is missing.
- Awareness of why the change is happening.
- Desire to take part in it.
- Knowledge of how to change.
- Ability to do it in practice, at speed, under pressure.
- Reinforcement so the new way sticks and does not drift back.
The useful part is the diagnosis. When a group is not adopting, find the earliest step they have not cleared and fix that one. Training people who do not yet want the change wastes the budget.
Four groups, not one
Do not write one message for "the organization." You have four groups, each starting at a different step:
- Employees of the acquired business, who fear for their jobs, pay, and status.
- Customers, who fear a change in service, price, or the person they call.
- Vendors and partners, who fear a change in volume, terms, or who they deal with.
- Your own team, which is often the group acquirers forget. They absorb extra work, hear conflicting stories, and can quietly resent the new people.
The ADKAR change plan grid
Fill in one card per group. If a row has no owner, nobody is doing it. Replace my starter actions with ones that fit your business.
Group owner: the acquired business's general manager, with the integration lead behind them.
| Step | What good looks like | Starting action | Owner |
|---|---|---|---|
| Awareness | Every person can say what is changing, what is not, and why. | All-hands on day one, then a written follow-up the same week. State what you do not know yet. | Integration lead |
| Desire | Key people see a future for themselves here. | Stay conversations with the critical few. Retention agreements for the roles that hold customers. | General manager and HR |
| Knowledge | People know how the new process, pay plan, or system works. | One page per change, in plain language, with a named person to ask. | Function leads |
| Ability | People can do it at normal speed without heroics. | Practice alongside a coworker. Pick a cutover date outside the busy season. Put floor support in place for two weeks. | Function leads |
| Reinforcement | The old way is gone and the new way is recognized. | Measure adoption weekly. Recognize the people who changed first. Retire the old tools. | General manager |
Group owner: the sales leader, with the top-account relationship holders doing the talking.
| Step | What good looks like | Starting action | Owner |
|---|---|---|---|
| Awareness | Customers hear it from their usual contact before they hear it elsewhere. | Top accounts called personally, then everyone else by letter or email, after employees know. | Sales leader |
| Desire | Customers see the combination as a reason to stay, not to shop around. | Say what stays the same first: contact, service levels, terms. Then say what gets better. | Account owners |
| Knowledge | They know how to order, who to call, and where to send invoices. | A short guide for any change to ordering, billing, or support. | Operations lead |
| Ability | The new ordering and billing path works the first time. | Test it with two friendly accounts before it reaches the rest. | Operations lead |
| Reinforcement | Churn and complaints stay flat or fall. | Watch the opening customer cohort separately from new sales. Follow up at 30 and 90 days. | Sales leader |
Group owner: the purchasing or operations lead.
| Step | What good looks like | Starting action | Owner |
|---|---|---|---|
| Awareness | Key vendors know who the new owner is and who to call. | A short call to the vendors who matter, after customers. | Purchasing lead |
| Desire | They want the combined volume and keep their terms in good faith. | Explain the volume story honestly. Do not threaten on the first call. | Purchasing lead |
| Knowledge | They know the new order, receiving, and payment process. | Send the process change in writing with a contact for exceptions. | Operations lead |
| Ability | Orders, deliveries, and payments run without exceptions. | Pay on time through the transition. Late payment is the fastest way to lose a good vendor. | Finance lead |
| Reinforcement | Terms and service hold, or improve with proof. | Review the vendor scorecard at 60 days. Do not consolidate to your agreement until you know why theirs was better. | Purchasing lead |
Group owner: you, the person leading the deal. Nobody else can own this one.
| Step | What good looks like | Starting action | Owner |
|---|---|---|---|
| Awareness | They know why this deal was done and what it changes for them. | Brief your own managers before the announcement, not after. | You |
| Desire | They treat the new people as colleagues, not a threat. | Name the benefit for them. Be straight about the extra work. | You |
| Knowledge | They understand what the acquired business does well. | Have your people spend real time with theirs before changing anything. | Function leads |
| Ability | They have the capacity to do integration work and their day job. | Take something off their plate for every integration task you add. | You |
| Reinforcement | Credit goes to the people who made it work. | Tie a share of bonuses to integration milestones people control. | You and HR |
The valley of despair
Here is what the model does not say out loud. After the announcement, performance and morale usually dip before they climb. Productivity falls while people learn new tools. Good people update their resumes. A customer or two tests whether you are still the same company. This dip is normal. I call it the valley of despair, and every integration I have run has had one.
The difference between a good integration and a broken one is rarely the dip. It is what the leader does inside it. Leaders who expect the valley hold their nerve. They keep the plan, keep communicating, and fix the specific step that is stuck. Leaders who do not expect it read the dip as proof the deal was wrong and reverse course. The people stop believing the next announcement. That is how you crush what you bought.
How to be ready for it
- Tell your board, lender, or partners before closing that a dip is coming and what you will watch.
- Set early warning signs in advance: exits among the critical few, top-account order volume, collections, on-time delivery.
- Decide now what counts as a real problem and what counts as the valley. A rule written on a calm day beats a decision made on a bad one.
Get the 100 day integration tracker (XLS)
An editable spreadsheet with an owner and status on every item. Use it to run the ADKAR grid above across your first 100 days.
Where is each group on the curve? A weekly check
Once a week, the integration lead and group owners answer one question for each group: what is the earliest ADKAR step we have not cleared? A group is only past a step if you can show evidence, not because you sent a message.
- Awareness: Ask five people why this deal happened and what changes for them. If the answers differ, you are still at Awareness.
- Desire: Are the critical few staying, taking calls, and bringing problems to you early? Silence is not agreement. If your best people have gone quiet, you are at Desire.
- Knowledge: Can a typical person describe the new process without looking it up? If not, you are at Knowledge, no matter how many sessions you ran.
- Ability: Is the new way done correctly, at normal speed, without a workaround? If people still lean on a workaround, you are at Ability.
- Reinforcement: Six weeks later, is anyone still using the old way? If yes, the change is not finished, however good it looked at launch.
Mark each group in the tracker as stuck at one step. Then put one action and one name against that step, and nothing else for that group until it clears.
Sequence change against management capacity
Every change uses the same limited resource: the attention of a handful of managers who also run the business. A plan with pay changes, a new system, new reporting lines, and a rebrand in one quarter is a plan nobody can carry out.
- List every change you intend to make in the first year, and count the managers each one touches. If three people own half the list, that is your bottleneck.
- Protect before you improve. Put anything that touches pay, reporting lines, or a top customer's experience later, after the key people are secure.
- One big change per group at a time. Do not run two high-effort changes through the same team in the same window.
- Avoid the busy season. Do not cut over a system when the field crews are slammed.
The 100 day sequence is in the first 100 days integration plan. The people side is covered in employee retention after acquisition. If you want the operating-model decision behind all of this, preserve and strengthen, selectively integrate, or substantially consolidate, that is in the post-merger integration playbook. The full task list is the post-merger integration checklist. If you want your managers trained to run this method themselves, see post-merger integration training.
Run it with your team
The 100 day integration tracker gives each group an owner, a status, and a place to mark where they are stuck.
Decisions on this topic
The specific calls operators face inside this part of the integration. Each has its own page, with the tension laid out and a way to decide.
- How fast to change after acquisition. Move too fast and you break the business you bought, too slow and the value leaks.
- When their hustle culture meets your salaried one. Normalizing hours and pay can cut real take-home and erase an identity people were proud of.
Questions
What is change management in post-merger integration?
It is the work of getting employees, customers, vendors, and your own team to actually adopt the changes an integration requires. Systems and org charts can be installed. Behavior has to be earned. Most integration shortfalls trace back to people not changing what they do.
What is the ADKAR model?
ADKAR is Prosci's change model. It describes five steps a person moves through: Awareness, Desire, Knowledge, Ability, and Reinforcement. A change stalls at the earliest step that is missing, so the fix is to find that step and address it, not to push harder on everything.
What is the valley of despair after an acquisition?
It is the dip in performance and morale that usually follows an announcement, before results climb. Expect it, measure it against a baseline, and hold your course. The damage comes when leaders reverse direction in response to a normal dip.
How much change is too much in the first 100 days?
It depends on management capacity, not on the length of your to-do list. If the same few managers own most of the changes, you are over capacity. Protect key people and customers first, then sequence improvements so no group carries two big changes at once.