Post-merger
Post-merger integration:
two teams, one plan.
A post-merger integration retreat is a working day, sometimes two, where the combined leadership team of two merged organizations settles the decisions the rest of the integration depends on: one operating model, who leads what, which systems survive, what stays separate on purpose, and one scoreboard. It is not the integration office's kickoff, which organizes the work. When the two companies compete, hold it after the deal closes, because until then competition law limits what the two sides may share and decide together.
TL;DR
- When
- In the first weeks after the deal closes. Before close, prepare only what your lawyers approve.
- Length
- One full day. Two days when the businesses overlap heavily.
- Who attends
- The leaders of the combined company from both sides, with a facilitator from neither.
- What you leave with
- The operating model, named leaders, surviving systems and what stays separate, each with an owner and a date.
Build your integration agenda.
Start today, or put the prep dates in your calendar.
When is it?
Which month?
Who's working on it?
What a post-merger integration retreat is
Every merger runs on two tracks. The first is mechanical: payroll, bank accounts, legal entities, email, access badges. Integration offices and day-one checklists handle it well. The second is the set of choices only the leadership team can make: how the combined company will run, who leads what, and which of two ways of working wins. The retreat is where the second track gets settled, so the first track has something to carry out.
Three meetings that get confused
| Day-one readiness | Integration kickoff | Leadership retreat | |
|---|---|---|---|
| Purpose | Nothing breaks on the first day: pay, access, contracts, customer contacts | Launch the integration program: teams, governance, timeline | Make the leadership decisions the program depends on |
| Who | Integration office and functional leads | Integration office, workstream leads, sponsors | The leaders of the combined company |
| When | Planned before close, run on closing day | Often before close, under rules set by counsel | After close |
| Output | A readiness checklist | A work plan and a meeting rhythm | Decisions with owners and dates: the start of the 100-day plan |
The decisions only the leadership team can make
- The operating model. Yours, theirs, or a new one, area by area.
- Who leads what. One name per area, and who decides what.
- Which systems and processes survive. One survivor per overlap, with an owned migration.
- What stays separate on purpose, with a reason and a date to review it.
- One scoreboard. The few numbers both sides will be judged on.
- What the combined plan can afford, and what stops to pay for it.
Leave these open and the integration office still runs, but it runs on guesses. Each workstream picks its own answer, and the two companies quietly keep building separate futures.
When two nonprofits merge
The same day works. The pressure points differ. Nonprofit mergers often turn on mission, programs and funders more than on cost savings, and both boards usually have a say in the structure. Competition law can still apply to nonprofits, so check with your lawyer before the two teams share sensitive information.
Why integrations miss, and when not to hold a retreat
Most acquisitions fall short of what was promised. How short depends on how you count. Clayton Christensen and colleagues, writing in HBR in 2011, said study after study puts the failure rate between 70% and 90%1. Mitchell Marks and Philip Mirvis, drawing on more than 70 combinations, put it at three in four in 20012. The studies define failure differently, but they point the same way.
The gap is widest where the leadership team has the most control. In McKinsey's 2004 study of merger results, most deals delivered at least half of the cost savings planned, but almost 70% fell short of the revenue gains expected3. Cost savings come from a plan. Revenue gains come from two teams selling, serving and deciding together.
Culture is the reason leaders give most often. In a Bain survey of executives who had managed mergers, published in 2013, culture clash was the No. 1 reason a deal failed to deliver the promised value4. In Bain's 2023 survey of M&A practitioners, nearly half named cultural fit or difficulty integrating management teams as a primary reason past deals failed. About three in four integrations still ran into culture problems that needed serious intervention, even though most had looked at culture early5.
"Culture" can sound vague. Research makes it concrete. In a 2003 laboratory study, Roberto Weber and Colin Camerer let small groups develop their own way of working on a task, then merged two groups. Performance fell. People overestimated how well the merged group would do, and they blamed members of the other group rather than the clash in habits6. That is the pattern a leadership retreat exists to catch: two teams using the same words for different things, each sure the other is the problem.
Do not hold a retreat when:
- The deal has not closed and the two companies compete. See what you can do before close.
- You plan to leave the acquired business alone. If the value is in what the target already does, a day to agree one operating model sends the wrong signal. A shorter meeting on reporting and shared services fits better. See how much to integrate.
- The big decisions are already made and announced. The day becomes theater, and the acquired team knows it. Hold a meeting that explains the decisions and takes hard questions instead.
- People in the room do not know if they have a job. Settle the top structure first, and tell each person where they stand before the day. GE Capital's integration lessons, written up in HBR in 1998, advised deciding and announcing structure, key roles and layoffs as soon as possible after the deal is signed, within days if possible8.
Before close and after close: what you can do when
Not legal advice. The rules depend on where the companies do business, the size of the deal, and whether the two compete. Talk to your competition or antitrust lawyer before the two leadership teams share plans, prices, customers or costs.
Until a deal closes, the two companies are separate businesses and must act like it. In the US, larger deals must be reported to the Federal Trade Commission and the Justice Department, and the parties may not close until a waiting period has passed or been ended early9. Taking control of the target early, or acting as one company before then, is called gun jumping. In 2025, three oil companies agreed to pay a $5.6 million penalty, the largest ever for gun jumping in the US, after the buyer stopped the target's planned drilling and coordinated its customer contracts and prices during the waiting period10.
Sharing information is a risk of its own. The FTC's 2018 guidance names current and future prices, strategic plans and costs as competitively sensitive, and says merging competitors should exchange them only through safeguards such as clean teams11. It also warns that sharing of this kind can be evidence of an illegal agreement under the Sherman Act, and that the companies must keep competing in case the deal does not happen11.
The European Union works on the same principle. Deals above its size limits must be notified and may not be put into effect until the European Commission clears them. In 2018 the Commission fined Altice 124.5 million euros, in part for holding veto rights over the target's ordinary business, telling it how to run a marketing campaign, and receiving detailed commercially sensitive information before clearance. Fines can reach 10% of the companies' combined turnover12. Many other countries run their own merger reviews with similar limits.
What a clean team is
A clean team is a small group allowed to see the other side's sensitive information for a narrow purpose, such as integration planning, under rules set by counsel. The FTC's guidance says it should not include anyone responsible for pricing, competitive planning or strategy11. That usually rules out most of a leadership team, which is why the full retreat waits until after close.
| Before signing | Signing to close | After close | |
|---|---|---|---|
| The two leadership teams meet | To negotiate and check the deal, with counsel | For planning your lawyers approve | Freely, as one company |
| Prices, customers, costs, plans | Only through safeguards counsel approves | Only through clean teams or outside advisers | Shared openly |
| The combined operating model | Not yet | Options planned, nothing put into effect | Decided at the retreat |
| Telling employees who leads what | Not yet | Messages drafted, timing checked with counsel | Soon after the retreat |
What you can prepare before close
- Set the date, the venue and the facilitator, so the retreat can run in the first weeks after close.
- List the decisions the retreat must settle, starting from the reasons the board approved the deal.
- Ask counsel which questions each leadership team may answer before close, and who may see the results. Questions about how people work are different from questions about prices, customers or plans.
- Have the clean team or outside advisers prepare the facts the retreat will need, released to the full team at close.
- Draft the first messages to both workforces.
If the two companies do not compete, or the deal is too small to need a filing, the limits may be lighter. Your lawyer decides that, not the integration plan.
Decide how much to integrate first
Before the room debates which system survives, it needs to agree how far to integrate at all. Philippe Haspeslagh and David Jemison's classic 1991 framework asks two questions: how much do the two businesses need each other to create the value in the deal, and how much does the acquired business need its independence to keep that value alive7?
| Approach | When it fits | What the retreat decides |
|---|---|---|
| Absorb | The businesses depend on each other, and the target does not need its own way of working | One operating model, one set of systems, one leader per area |
| Preserve | The value is in what the target does now, and integration would damage it | The few things that are shared, such as money, reporting and risk, and everything that stays separate |
| Connect (symbiosis) | The businesses depend on each other, and the target still needs its independence | What joins now, what stays separate, and when each separate item is reviewed |
| Hold | Little connects the two beyond ownership | Reporting and controls only. A combined retreat may not be needed |
Most deals mix approaches by area: absorb finance, preserve product, connect sales. The "What stays separate" block in the sample agenda is where that mix gets written down, each item with a reason and a review date. Without it, "separate for now" quietly becomes "separate forever", or gets merged by accident.
Christensen and colleagues made a related point in 2011. If you bought a company for its resources, such as its customers, products or people, fold them in. If you bought it for the way it does business, keep that model intact, often by running it separately. Their warning case is Daimler, which folded in Chrysler's resources and lost the fast design process and lean costs that had made Chrysler worth buying1.
Who attends
Both leadership teams, in balance. If one side fills two thirds of the seats, the other side's view becomes a minority report. Invite the leaders who will run the combined company, from both sides.
Each business unit lead with a profit and loss. Each team has to hear its part from the people who decided it.
The finance lead and the heads of operations and systems. The combined plan has to add up, and the systems choices need the people who will run the migration.
The people lead. Culture is the reason leaders most often give for a failed deal45, and someone has to hold the key-people list and the communication plan.
When some roles are changing
If a leader's role is going away, tell them before the day, in private, and decide together whether they attend. James Walsh's 1988 study of acquired companies found turnover in their top teams well above normal levels, with the most senior and visible executives leaving soonest13. A 2014 review found that keeping the acquired leaders helps some deals and replacing them helps others, depending on the deal14. What helps no deal is leaving people to guess.
A facilitator from neither company
In most leadership retreats a facilitator is optional. Here it usually is not. If the buyer's chief executive runs the day, the acquired team hears the buyer's agenda. A facilitator from neither company can put the hard question to both sides and hold the time. Ask candidates how they collect views before the day and how they handle a room where one side holds the power.
Before the day: hear both teams separately
Each company arrives with facts the other does not have: why a big customer stays, which system is held together by one person, what the last reorganization broke. In a classic 1985 experiment, groups given all the information picked the best option 83% of the time. When the same facts were split among members, only 18% of groups found it, and discussion reinforced the first impression rather than correcting it15. In a merger the split runs along company lines, which makes it worse.
Weber and Camerer's merged groups blamed each other for problems the clash itself caused6. Collecting each person's view privately, before anyone talks, puts the differences on the table as data rather than as accusations. Then show the results side by side: where both teams agree, where they split, and the question most people named.
Questions to ask both leadership teams before the integration offsite
Throughline asks the leader four questions about the decision, then asks the team to answer anonymously on their own devices, in about two minutes. These are the questions it uses.
For you, the leader
- What is the one operating model: yours, theirs, or a new one?
- What stays separate on purpose, and for how long?
- Where do the two sides disagree in ways that will cost money?
- Who leads what, and how many teams hear their part?
For both teams, anonymously
Each rated 1 to 5. Nobody sees who said what, including you.
- I am clear on the decision this retreat needs to make.
- I know who leads what in the combined company.
- I can say what I really think with this team.
- I am confident we will follow through.
Then one open question: what is the most important decision this retreat has to make?
Who to invite
- Both CEOs or the two integration leadsone model needs both
- CFOthe combined plan
- Heads of operations and systemswhat survives
- People leadthe culture clash costs money
- Each business unit lead with a P&Leach team must hear its part
- Ask both teams the same questions. Ask only one side and the assumption one team made that the other never agreed to stays hidden.
- Send them after close, or with counsel's approval. Before close, check with your lawyer which questions the two teams may answer and who may see the results. See before and after close.
- Keep answers anonymous, including from both chief executives, so people can write what they would not say across the table.
- Send the questions about two weeks before the day, and share the results a week before. Build the agenda around where the two teams split.
Planning timeline
| When | What happens |
|---|---|
| Signing to close | Decisions for the day listed from the deal rationale. Date, venue and facilitator set. Questions and their timing agreed with counsel. |
| Close | First messages to both workforces. Top roles announced, if decided. |
| Close plus 1 week | Questions sent to both leadership teams. |
| Close plus 2 weeks | Answers in. Agenda built around where the two teams split. |
| Close plus 3 weeks | Pre-read sent: the deal rationale, the decisions, the results of the questions. |
| Close plus 3 to 5 weeks | The retreat. Each decision recorded as it is made. |
| Within 2 days after | The same message to both workforces on what was decided. |
| Days 30, 60 and 90 | Decisions, synergies and key people checked. |
A sample merger integration kickoff agenda
A full day for the combined leadership team, laid out by the same rules Throughline’s planner uses, before either side has answered anything. It settles the decisions, the decision rights, which systems survive and what stays separate. Full day, 09:00 to 15:25, breaks and lunch included.
- 09:00
Welcome 10 min
- 09:10
Warm-up 10 min
- 09:20
Opening brief 20 min
Method: Read the brief, then talk
Done when: Everyone has reacted to the brief and named what they want to leave with.
- 09:40
The decision 30 min
Method: Make the decision and pick the priorities
Done when: The call is made and the priorities are ranked.
- 10:10
Cuts and trade-offs 30 min
Method: To fund this, what stops
Done when: No new commitment is unfunded and no funding source is vague.
- 10:40
How we work together 25 min
Method: Agree how we'll work
Done when: A short list of behaviours is agreed and the keepers are starred.
- 11:05
Break 15 min
- 11:20
Decision rights 20 min
Method: Whose call is it
Done when: Every listed decision has a claimant or a dated contest.
- 11:40
Lunch 45 min
- 12:25
Affordability check 20 min
Method: Can we afford what we just agreed
Done when: Total commitment fits capacity, or the room has explicitly accepted the overrun.
- 12:45
Warm-up 5 min
- 12:50
One scoreboard 25 min
Method: Are we watching the same scoreboard
Done when: One scoreboard is agreed and the competing measures are listed beside it.
- 13:15
Systems and processes 20 min
Method: Which systems survive
Done when: Every overlap has one survivor and an owned migration.
- 13:35
Break 15 min
- 13:50
What stays separate 20 min
Method: Kept separate, on purpose
Done when: Everything separate has a why and a review date.
- 14:10
Order of work 20 min
Method: What has to happen before what
Done when: The order stands and nobody’s item secretly starts first.
- 14:30
Each team's part 30 min
Method: What each team owns
Done when: Each area knows what it owns.
- 15:00
Close and commitments 20 min
Method: What, so what, now what
Done when: The third round produced something with an owner.
- 15:20
Who made today work 5 min
Make one for your own situation Planning two days? The free planner builds both from your team’s answers.
Half a day or two days
Half a day. Keep the opening brief, the decision, decision rights, one scoreboard, what stays separate and the close. That runs about two and a half hours with one break, and works when most of the acquired business will stay separate.
Two days. End the first day after the affordability check and hold a dinner for both teams that evening. Open the second morning with a short recap of what day one settled, then take one scoreboard, systems and processes, what stays separate, the order of work and each team's part. Use two days when the businesses overlap heavily and many systems have to be chosen.
Two additions for any length
- Mixed tables. Seat people so every table has both companies at it, from the first exercise.
- The buyer's leaders speak last on contested questions, so the acquired team's view is heard before the direction is set.
Running the day
Ground rules. Agree three at the start: describe how things are done, not which company does them; what is said in the room stays in the room; the buyer's leaders give their view last on contested questions.
Name habits, not values. "Customer first" means nothing when both companies claim it. Ask each side to describe a specific habit: how a price exception gets approved, how fast a complaint reaches a leader, who can hire without asking. Differences in habits are what trip up a combined team, and habits can be decided.
Write before you talk. On each big question, give everyone two minutes to write their view before anyone speaks. Then go round the table, alternating between the two companies.
Choosing between two systems. Agree the test before looking at the options: the cost to switch, the risk to customers, and which one the combined company can grow on. Then score both. A system chosen by a test survives the next hard month. One chosen by rank gets reopened.
Decision rights. For each decision in the "whose call is it" block, name one person. Where two leaders both claim it, write it down as a contest with a date to settle it, rather than leaving it vague.
What the leaders can say
We bought this company for what you do well, and I do not yet know all of it. Before today, both teams told us where they agree and where they do not. Today we settle the few things the rest of the integration depends on. On anything contested, I will give my view last.
Walk us through how it works day to day. Who approves it, how long it takes, what happens when it goes wrong. Then I want to hear how the other team handles the same thing.
We agreed the test before we looked at the options: switching cost, customer risk, and whether it can carry us for five years. On that test, we keep one ordering system, ours. Andy owns the migration. It reopens only if the migration is less than half done by March.
Here is what we decided, who owns each piece, and what stays separate for now. Both companies hear the same message from us within two days. If you disagree with how I have put any of it, say so now.
Keeping key people and telling both workforces
The leadership team is not the only audience. Everyone in both companies is waiting to hear what the retreat decided, and silence fills with rumor.
The evidence favors saying more, sooner. In a 1991 field experiment, David Schweiger and Angelo DeNisi followed two plants of a company that had just announced a merger. One plant got a realistic merger preview, a program of honest communication about what would change. The other got limited information. The preview reduced the harmful effects of the merger, the benefit lasted, and on some measures people returned to where they had been before the announcement16.
GE Capital's lessons, published in HBR in 1998, point the same way: start integration planning during due diligence, before the deal is signed; make integration one person's full-time job; settle structure and roles within days where possible; and integrate cultures as well as operations8.
- Same message, same day, both companies. A leak from one side becomes the story.
- Tell the truth, including "we do not know yet". In GE Capital's 1998 account, ten chief executives of companies it had bought all said, looking back, that the changes had not moved fast enough. One warned against calling it business as usual, or a merger of equals, when it is neither8.
- Say what is decided, what is not, and when it will be. People can live with "the sales structure is set by March". They struggle with silence.
- Managers first. Brief managers shortly before the all-company message, so they can answer their teams' questions.
- Key people in person. Before the retreat, list the people in both companies whose loss would hurt the deal most. Each one gets a conversation with their new leader within a week after it.
Yesterday the leaders of both companies spent the day together. Here is what we decided: how the combined company will run, who leads each area, and what stays as it is for now. Here is what is not decided yet, and the date for each. Your manager will walk you through what it means for your team this week.
What the combined team leaves with
The operating model, who leads what by name, which systems survive and what stays separate, each with an owner and a date: the start of the 100-day plan.
- Every decision is recorded with an owner, a date and what would reopen it.
- The plan drafts itself from what the room decided, and each team gets its own part of it.
- Owners check in from an email in one click. A missed check-in counts as off track, and their manager is told.
- Follow-up all year on how the plan is holding up. Or take the plan with you as a PDF or Markdown.
From decisions to the 100-day plan
The 100-day plan is the work that turns the retreat's decisions into a running company. GE Capital's 1998 account describes planning sessions held right after close, where the leaders of both companies draft a 100-day plan together, starting with the acquired team describing what works well in its company and should be built on8. Each decision becomes one or more pieces of work with an owner and a date. Record each outcome in one of three columns:
| Decided | Kept separate, on purpose | Not yet decided |
|---|---|---|
| What changes, who owns it and by when | What stays as it is, why, and when it will be reviewed | What still needs work, who brings it back, and by when |
Tracking synergies
The deal model promised savings and growth. Give each synergy an owner, turn it into a monthly number, and review it with the other decisions. Report cost and revenue separately. Revenue gains are where estimates miss most often3, so they need the closest watching and the most honest forecast.
Did it work?
A good integration retreat feels like progress. That is not the test. Check these five things:
- The decisions held. Count how many of the day's decisions were reopened within 90 days. A few is healthy. Many means the room agreed on words, not decisions.
- Key people stayed. Check the key-people list at 90 and 180 days, for both companies.
- Synergies are on track. Compare each synergy line to plan every month, with cost and revenue reported separately.
- The two teams are closer. Ask both leadership teams the same anonymous questions again at 90 days, such as whether they know who leads what in the combined company. The gap between the two companies' answers should shrink.
- Work happened in order. Check that migrations and other work followed the agreed order, and that nobody's item quietly started first.
Post-merger integration retreat checklist
Between signing and close
- Lawyers asked what the two teams may share, and when
- Decisions for the retreat listed from the deal rationale
- Date, venue and a facilitator from neither company booked for the first weeks after close
- Key-people list started, for both companies
- First messages to both workforces drafted
First two weeks after close
- Top roles settled, and anyone whose role is changing told in private
- Same questions sent to both leadership teams, with answers anonymous
- Answers in, and the agenda built around where the two teams split
The week before
- Pre-read sent: the deal rationale, the decisions, the results
- Tables mixed across both companies
- Someone named to record decisions as they are made
On the day
- Habits named, not values
- Write before talking on every big question
- Each outcome recorded: decided, kept separate, or not yet decided
- An owner and a date on every decision
After
- The same message to both workforces within two days
- Key people spoken to within a week
- Synergies tracked monthly, cost and revenue separately
- Decisions, key people and both teams' answers checked at 30, 60 and 90 days
What integration leads want to know first.
What should be on a merger integration kickoff agenda?
The decision the integration turns on, how the combined team will work, who decides what, what the combined plan can afford, one scoreboard, which systems survive, what stays separate, the order of work, and each team's part. The sample above covers them in a day.
How do you combine two leadership teams after an acquisition?
Once the deal has closed, decide the operating model and who leads what early, by name, in the same room. Hear both sides anonymously first, so the disagreements that will cost money are on the table before the day rather than after.
Should both leadership teams answer, or just ours?
Both. Ask only one side and the most dangerous thing stays hidden: the assumption one team made that the other never agreed to.
When in the integration should we run it?
In the first weeks after the deal closes. Before close the two companies are still separate, and if they compete, competition law limits what they may share and decide together. Use the time before close to plan with your lawyers, then run the day as soon as the deal is done.
Is anything visible to the other side?
Nobody sees who said what. Answers are anonymous to everyone, including both leaders, so people can write what they would not say across the table.
How does the day connect to the 100-day plan?
Every decision leaves with an owner and a date, and the plan drafts itself from them. Each team gets its own part, with check-ins and follow-up that runs all year.
What is gun jumping in a merger?
Gun jumping is acting as one company before a deal is allowed to close: taking control of the target early, or coordinating prices, customers or plans with it. US and EU authorities have fined it heavily. This is not legal advice; ask your competition lawyer what applies to your deal.
What is a clean team in M&A?
A small group allowed to see the other side's sensitive information for a narrow purpose, such as integration planning, under rules set by counsel. US FTC guidance says it should not include anyone responsible for pricing, competitive planning or strategy, which usually rules out most leaders.
Why do post-merger integrations fail?
Most often because the deal overestimated revenue gains and the two cultures clashed. Studies by McKinsey and Bain point to both. Cost savings usually arrive; growth that needs two teams working as one often does not.
What should happen in the first 100 days after an acquisition?
The leadership decisions first: operating model, who leads what, which systems survive and what stays separate. Then the work that carries them out, each piece with an owner and a date, with key people kept and both workforces told the same thing on the same day.
Does team building help after a merger?
Time together helps people meet, but a social event does not settle who leads what. What builds one team is deciding the hard questions together, with both sides heard, and then keeping the decisions.
Sources
- Clayton M. Christensen, Richard Alton, Curtis Rising and Andrew Waldeck, "The Big Idea: The New M&A Playbook," Harvard Business Review, March 2011. hbr.org
- Mitchell Lee Marks and Philip H. Mirvis, "Making Mergers and Acquisitions Work: Strategic and Psychological Preparation," Academy of Management Executive 15(2), 2001. doi.org
- Scott A. Christofferson, Robert S. McNish and Diane L. Sias, "Where mergers go wrong," McKinsey on Finance, 2004. mckinsey.com
- Dale Stafford and Laura Miles, "Integrating cultures after a merger," Bain & Company, December 2013. bain.com
- Bain & Company, "How to Avoid the Fault Lines Sending Tremors through Cultural Integration in M&A," M&A Report 2023, January 2023. bain.com
- Roberto A. Weber and Colin F. Camerer, "Cultural Conflict and Merger Failure: An Experimental Approach," Management Science 49(4), 2003. doi.org
- Philippe C. Haspeslagh and David B. Jemison, Managing Acquisitions: Creating Value Through Corporate Renewal, Free Press, 1991.
- Ronald N. Ashkenas, Lawrence J. DeMonaco and Suzanne C. Francis, "Making the Deal Real: How GE Capital Integrates Acquisitions," Harvard Business Review, January to February 1998. hbr.org
- US Federal Trade Commission, "Premerger Notification Program." ftc.gov
- US Federal Trade Commission, "Oil Companies to Pay Record FTC Gun-Jumping Fine for Antitrust Law Violation," press release, January 7, 2025. ftc.gov
- Holly Vedova, Keitha Clopper and Clarke Edwards, "Avoiding antitrust pitfalls during pre-merger negotiations and due diligence," US Federal Trade Commission, Competition Matters, March 2018. ftc.gov
- European Commission, "Mergers: Commission fines Altice €125 million for breaching EU rules and controlling PT Portugal before obtaining merger approval," press release IP/18/3522, April 24, 2018. ec.europa.eu
- James P. Walsh, "Top management turnover following mergers and acquisitions," Strategic Management Journal 9(2), 1988. doi.org
- Jeffrey A. Krug, Peter Wright and Mark J. Kroll, "Top Management Turnover Following Mergers and Acquisitions: Solid Research to Date but Still Much to Be Learned," Academy of Management Perspectives 28(2), 2014. doi.org
- Garold Stasser and William Titus, "Pooling of Unshared Information in Group Decision Making," Journal of Personality and Social Psychology 48(6), 1985. doi.org
- David M. Schweiger and Angelo S. DeNisi, "Communication with Employees Following a Merger: A Longitudinal Field Experiment," Academy of Management Journal 34(1), 1991. doi.org
Written by Tom Olajide, Founder. Survey figures are quoted with the year they were collected. Last reviewed September 24, 2026.
Two plans still running side by side?
When is it?
Which month?
Who's working on it?