Dark Light

The deal closes, the press release goes out, and the clock starts running on a number of synergies someone promised a board. What happens next rarely looks like the plan. In the weeks after an announcement, the people who serve customers stop knowing who approves what, which policies still apply, and whether their jobs survive the quarter. That gap between the strategic logic of a merger and the operational reality of a Tuesday morning is where value quietly leaks out, and most integration plans barely acknowledge it exists. David Partain, a marketing executive who has worked inside large financial institutions and built companies from scratch, argues that the first casualty of a merger is rarely strategy. It is the ability of ordinary employees to make decisions, and leaders who do not address that within days are already behind.

Clarity Before Certainty

Partain locates the first breakdown precisely. “Momentum often breaks down first in the space between the announcement and the everyday work,” he says. “Leadership is talking about the opportunity, while employees are asking, ‘Who makes decisions now? What happens to my role? What do I tell my clients?'” When those questions go unanswered, the behavior that follows is predictable and expensive. People protect territory or wait for permission. Neither moves the business forward, and both are invisible on a synergy tracker until revenue starts to slip.

The remedy is not a reassuring deck. Partain’s recommendation is a short shared operating brief issued to both organizations immediately: why the companies are combining, what must keep being delivered for customers, who owns the critical decisions, and when the next update lands. Where the permanent structure is not settled, he would name interim accountability rather than wait. “A client issue cannot wait for the final organization chart.” He is also clear that leaders from both sides belong in that conversation from the start, because integration that feels like one company dictating to another poisons the operational work that comes later. “People do not need every answer on day one, but they do need enough direction to act, and enough honesty to trust the next update.”

What To Standardize And What To Leave Alone

The default instinct in most integrations is to migrate the acquired business onto the acquirer’s systems, processes, and habits, on the theory that consistency equals efficiency. Partain rejects the framing. Drawing on experience in both institutional and entrepreneurial environments, he starts from a sharper question: “What must be consistent, and what is valuable precisely because it works differently?” Financial controls, compliance standards, and accountability for shared outcomes belong in the first category. Product development, customer relationships, and team workflows frequently do not.

The distinction matters because acquirers routinely destroy what they paid for. Imposing identical methods on a smaller, faster business strips out the initiative that made it attractive in the first place, and the loss shows up two years later as a stalled product pipeline nobody can trace back to the integration. Partain wants people “accountable for shared outcomes, not forced into identical methods simply because one organization is larger.” The same logic applies to culture, which he says fails most often when leaders mistake symbols for substance. He watched it happen firsthand at a firm being acquired, where a tradition of paid workdays volunteering at local nonprofits looked set to disappear. Employees read the change as evidence the combined company did not care about vulnerable people in the community. It did. The other organization simply recognized service differently, through an annual lunch honoring employees who volunteered on their own time. The resolution kept both: the recognition lunch stayed, and teams chose organizations to support with new ways to volunteer during working hours. The underlying value was shared all along. Only the expression differed.

The Integration Problem Nobody Is Planning For

Culture gets treated as a communications workstream, which is why it fails. Partain would make it operational instead, by running teams from both organizations through the moments where working habits collide: approving a campaign, escalating a client complaint, challenging a senior leader, rewarding performance. Walking through those scenarios makes abstract differences concrete. From there, he would agree on a few observable behaviors, assign leaders responsibility for practicing them, and review progress alongside operational results. The warning he attaches is the one most integration plans ignore. “If we say we value collaboration but reward managers only for their own department’s results, the incentives will win.”

The harder problem is arriving now. Executives are planning to merge today’s systems and headcount at the same moment AI is rewriting how the work itself gets done, and Partain thinks few are ready for the collision. “The challenge is not simply choosing which AI tools survive. It is deciding which decisions can be automated: Is the data applicable to both organizations? Where does human judgment remain essential? Who is accountable when the two interact?” Two companies with AI systems trained on their own internal data do not merge cleanly, because the data itself may not transfer. His practical counsel is to map critical workflows before committing to headcount reductions or technology savings, identify the expertise each business genuinely depends on, and test redesigned workflows with the people who understand the consequences for customers. The failure mode he would guard against is the one that looks like success on paper: hitting the promised cost savings while quietly losing the knowledge required to serve clients and grow. “The next integration plan should explain not just how two companies become one, but how that company will learn to work differently.”

Follow David Partain on LinkedIn for more insights on post-merger integration, organizational alignment, and leadership during periods of change.

Related Posts