In a merger or acquisition, a team manager’s rollout plan comes down to knowing the legal framework, answering people’s questions before the rumour mill does, holding off on integration until the deal closes, and then merging processes one at a time. The board owns the transaction; the team manager owns what it means on Monday morning.
Quick Overview
What you will learn:
- Which employee information duties apply when a business changes hands
- Why integration is planned, not executed, before closing
- The roles in an integration project and where a team manager fits
- Three artefacts worth keeping: a stakeholder map, a communication plan and a question log
Who this article is for:
- Team and department managers on either side of a deal
- Integration office members and HR business partners supporting the transaction
- Project leads who will merge processes and tools after closing
Reading time: 7 minutes
What the Deal Means for the People You Manage
Your team will not ask about valuation. They will ask who their manager is going to be, whether their contract changes and whether their project survives. A manager who cannot answer, and cannot say when an answer will come, leaves corridor talk to fill the gap.
European law answers part of it. Council Directive 2001/23/EC on eur-lex.europa.eu covers transfers of undertakings: under Article 3 the rights and obligations arising from existing employment contracts pass to the transferee, and under Article 4 the transfer is not in itself a ground for dismissal, although dismissals for economic, technical or organisational reasons remain possible. Article 7 obliges both the transferor and the transferee to inform employee representatives of the date, the reasons, the legal, economic and social implications and any measures envisaged for staff.
A second instrument sets the wider expectation. Directive 2002/14/EC on eur-lex.europa.eu establishes a general framework for informing and consulting employees and, in Article 4, covers decisions likely to lead to substantial changes in work organisation or contractual relations. Each Member State applies it either to undertakings with at least 50 employees or to establishments with at least 20. Not every deal changes the legal employer, and national law adds its own deadlines, so the legal team decides what applies. The manager’s job is to know the answer before the first team conversation.
Plan, Don’t Integrate, Before Closing
Good managers most often go wrong through enthusiasm. Once it is clear the teams will merge, it feels efficient to agree on shared tools, swap customer lists or split the workload early. In larger deals competition law forbids it. Article 7 of Regulation (EC) No 139/2004 on eur-lex.europa.eu states that a concentration with a Community dimension shall not be implemented before notification or until it has been declared compatible with the common market.
So the period before closing is for preparation: map the processes that will have to merge, list risks, collect open questions. Execution starts after closing. What information may be shared with the other company’s team in the meantime is for the legal team to decide, not for the manager.
A Rollout Plan Built on Kotter’s Warnings
Writing in hbr.org, John P. Kotter listed the errors that derail transformations, from failing to establish a sense of urgency and a strong guiding coalition, through undercommunicating the vision, to declaring victory too soon and not anchoring change in the culture. His article is about companies, but the same traps appear inside a single team after an acquisition. A team-level plan that respects them looks like this:
| Phase | What the team manager does | Kotter’s warning it addresses |
|---|---|---|
| Before announcement | Learns from the integration office which decisions are made, pending or open | Lacking a vision |
| Announcement week | Tells the team what is known, what is not and when answers will follow | Undercommunicating the vision |
| Day one after closing | Makes sure everyone knows their reporting line, systems and HR contact | Not removing obstacles |
| First months | Merges processes one at a time, customer-facing ones first, and makes each step visible | Not planning short-term wins |
Kotter’s point about communication matters most here: a vision is not communicated by one meeting or one email, so the announcement conversation is the start of a series, not the whole of it.
Who Does What in the Integration
An integration project runs on named roles, and a team manager should know the people behind them:
- Change sponsor: a board member accountable for the outcome who settles priority conflicts.
- Integration management office: coordinates the timeline, cross-area dependencies and the decision log.
- Team manager: turns decisions into tasks, gathers questions and signs of resistance, escalates risks.
- HR and legal: handle information duties, changes to terms of employment and dialogue with employee representatives.
Three artefacts keep the manager’s part under control. A stakeholder map shows who in the team and among customers will feel the change most. A communication plan sets who hears what, when and through which channel. A question log gives every question from the team an owner and a due date.
Read Also
- Communicating organisational change to your team — shaping the message
- The change sponsor role in a transformation project — what the board owes the project
- Resistance to change — working with the team’s concerns
Build Your Skills
Explore the Change management for managers and leaders and Kotter’s 8-step model of change courses. The first focuses on communication and handling resistance, the second on leading a transformation stage by stage. Contact us to shape the scope around your organisation’s situation.
Frequently Asked Questions (FAQ)
What does change management involve in a merger or acquisition?
It translates a decision about a transaction into changes in people’s work: reporting lines, processes, tools and terms of employment. The board sets the direction and the integration office runs the timeline, while the team manager makes sure people know what changes, when, and whom to ask.
What are the stages of change management after an acquisition?
At team level: preparation before closing, a candid conversation after the announcement, an orderly first day after closing and a gradual merger of processes. Kotter’s article in hbr.org adds the conditions for success: urgency, a guiding coalition, a vision, sustained communication and anchoring the change in the culture.
Does the ADKAR model work in a merger?
Yes, as a complement to the organisational plan. ADKAR looks at change through the eyes of an individual employee, which helps a manager see where a particular person is stuck. Our article on the ADKAR model for organisational change management covers it in more depth.
What are real-world examples of change management after an acquisition?
Common cases include moving a sales team onto a shared CRM, aligning remote-work rules across both companies or bringing the customer service teams of both companies under one manager. Each calls for the same toolkit: a stakeholder map, a communication plan and a question log with due dates.