I have spent a decade leading post-merger integrations across different contexts: in-house, within consulting structures, and as an independent lead. That experience has given me a clear view of what PMI requires, and how different those requirements are from what gets a deal to close.
M&A and integration look at the same deal from different positions. The deal team does its job well: evaluating, pricing, and reaching a decision under significant time pressure. Once the deal closes, a different set of questions takes over. The focus shifts from assessing an organization to working inside it, with its culture, its pace, and the gap between what was modeled and what the ground looks like on day one.
Culture sets the pace of an integration
In my experience, the variable that most consistently determines how an integration goes is the culture of the acquired company. It’s also the one most underweighted during due diligence and least likely to be built into timelines. Peter Drucker put it well:
“Culture eats strategy for breakfast.”
A capable team with a well-designed plan can still lose momentum when the change required outpaces what the organization can absorb at that moment.
Working with culture takes time on the ground. The information that matters tends to surface in informal conversations, in one-to-one meetings, in the kind of exchange that would never happen in a formal governance setting. Part of the job is reading when an organization is losing momentum before it appears in any status report.
Why integration teams should be involved before closing
One of the best improvements I’ve seen in how integrations are set up is involving the PMI lead during due diligence, even in a listening capacity. This gives the integration team early insight into how the organization is structured, where duplicate roles will create friction, and which individuals carry informal authority that won’t be visible on any chart.
Listening in on vendor calls and expert sessions provides context that can hardly be reconstructed from documents alone. The earlier the integration team is involved, the better prepared they are to deliver a credible day-one plan.
What working independently changes
Working as an independent integration lead changes the dynamic in ways that are specific to this kind of work.
There is no internal hierarchy to navigate, no follow-on engagement to position for, and personal accountability on every mandate. That creates the conditions to surface problems early, challenge assumptions that have stopped holding, and push for decisions at the moment when delay is creating more risk than the decision itself would. It removes a layer of caution that exists in most organizational structures.
One person staying through the full arc of an integration also builds trust that compounds over time. My approach has always been straightforward: I say what I do, and I do what I say. That consistency is what holds transparency in place across the whole program.
In the whitepaper, I go deeper into each of these areas:
- What the first two weeks of an integration look like in practice
- How to read the signals that tell you a program is drifting
- How to build the conditions where problems surface early
- What a more useful measure of integration success looks like
Get your copy of the whitepaper
These insights draw on a decade of field experience and are written to be useful to anyone working at the intersection of M&A and integration, whether in corporate development, PE, or as an independent professional.
