M&A Integration: Why the First 90 Days Are an Operations Problem, Not an HR Problem

Every M&A integration plan I've ever seen leads with culture and communications. Town halls. Leadership introductions. Values alignment workshops. These are important — but they are the wrong first priority. The first 90 days of integration are an operations problem.

What actually breaks in the first 90 days

In every integration I've run or advised on, the failure modes in the first quarter are always operational: duplicate vendor contracts no one is managing, reporting timelines that don't sync with board expectations, IT systems that can't talk to each other, site-level leaders who don't know what they're accountable to the new parent for. Culture failure is usually downstream of these operational failures — people disengage not because of culture clash, but because they don't know what's expected, systems don't work, and nothing gets decided.

The 100-day operational foundation

The first 30 days should establish operational baseline: current-state mapping across all sites, standardized reporting definitions, governance cadence, and a clear accountability structure. Not the final operating model — just enough clarity that the business can run and report while the integration unfolds. Days 31–60 focus on the highest-risk integration points: IT systems, vendor consolidation, and financial reporting harmonization. Days 61–90 build the forward plan: the first version of the value-creation roadmap, aligned to the sponsor's thesis.

Culture follows systems

Culture work should begin in month four — not month one. By then, people have seen that the new ownership is operationally competent. Decisions are being made. Systems work. Accountability is clear. The culture conversation is much easier when the organization isn't operating in chaos. Starting with culture when operations are unstable just creates cynicism — people hear the values message while experiencing operational dysfunction, and they conclude the values aren't real.