A Deal That Looks Finished on Paper
The contracts are signed. The org chart is drawn. Two teams that used to compete, or never worked together at all, now report into one structure. On paper, the merger is done.
In the room, it isn’t close to done.
I have sat in enough of these rooms to know the gap between the paperwork and the people. Systems can be combined in a quarter. Habits, instincts, and the quiet rules a team lives by take much longer, and nobody puts that timeline in the deal memo.
The Problem Nobody Named in the Announcement
Every integration I have been part of ran into the same problem: two teams that were each doing good work, on their own terms, now had to agree on whose terms would win.
That sounds like a process question. It isn’t. It’s an identity question. A creative team that built its reputation on speed does not easily sit next to one that built its reputation on caution and polish. Neither is wrong. But put them in one room without naming the difference out loud, and you get quiet resistance that looks like slowness, or turf protection that looks like ego.
Leaders tend to treat this as a communication gap. Send a memo, hold a town hall, explain the new structure clearly enough and people will fall in line. I have tried that, and it buys you a week of calm before the old patterns come back.
What Is Being Lost
When two teams merge, each side is quietly grieving something, usually the authority to do things their own way. People rarely say this directly. They say the new process is slower, or that the other team doesn’t understand the client, or that decisions used to happen faster.
Underneath all of that is a simpler sentence: we used to know how to do this, and now we don’t.
That is the real problem a leader has to solve. Not the org chart. The sense of competence people had before the merger, and have lost since.
How I Approach the First Ninety Days
I have learned to stop treating the first few months after a merger as an execution problem and start treating it as a trust problem. That changes where I spend my time.
I spend less time explaining the new structure and more time asking each team what they are proud of from before. Not to be sentimental, but because that pride points to what they will protect without being asked, and what they will fight you on if you touch it carelessly.
I also look for the small decisions, who signs off on creative, who talks to the client first, who owns the budget line, because those are where the real culture clash shows up, long before it reaches a strategy document. Get those decisions wrong, or leave them ambiguous, and you will spend the next year refereeing disputes that look procedural but are really about who gets to feel competent.
And I try to be honest that some capability will be lost in the short term. Two fast teams rarely combine into one faster team immediately. Naming that trade-off, rather than promising seamless integration from day one, buys more patience than any reassurance does.
The Standard I Hold the Work To
A merger succeeds when people on both sides can point to something they do better now than they could alone, not when the org chart stops generating questions. That takes longer than most timelines allow for, and it rarely moves at the pace the announcement suggested.
The teams that get there are usually the ones whose leaders stopped asking “how do we get them aligned” and started asking what each side was afraid of losing. That question is slower to ask and harder to sit with. It is also the one that actually gets two good teams to become one.



