Skip to main content
← Back to Insights

The Part of Integration Nobody Budgets For

The org chart changed on paper months before anyone told the people living it.

3 min read

Every integration plan has a workstream for systems, a workstream for finance, a workstream for legal. Change management usually gets a line item, sometimes a slide, rarely a budget that matches what it actually takes to move people through a transition they did not choose.

The gap that does not show up on the dashboard

That gap is where integrations quietly fail, even the ones that hit every operational milestone on schedule. Systems can be migrated on a deadline. People cannot be. Someone who has spent five years knowing exactly how to get something done at their company now works somewhere with different tools, different approval chains, and a different definition of normal, and nobody sat down and explained why, or what happens to them specifically. They find out their reporting line changed from a company-wide email. They find out their role is being restructured secondhand, from a colleague, days before it is official.

None of this shows up in an integration dashboard. The systems cutover is green. The finance consolidation is on track. And underneath both, the people who were supposed to make the deal thesis real are disengaging, and disengagement does not announce itself, it just shows up later as slower execution, quiet resignations, and a workforce that complies without believing.

What treating it like a real workstream looks like

The companies that get this right treat change management as a workstream with the same rigor as systems or finance, not a communications afterthought. That means:

Naming what is changing, specifically, before it happens. Not "there will be some changes to reporting structures," but who reports to whom, starting when, and why. Vague communication reads as evasive even when it is not.

Giving people a real channel for questions, not just a town hall. A single all-hands announcement is not change management, it is an announcement. People need somewhere to ask what a change means for them specifically, and someone accountable for actually answering.

Treating manager readiness as part of the plan. Frontline managers absorb the most questions and have the least information, unless someone deliberately equips them first. An unprepared manager fielding questions they cannot answer does more damage to trust than no communication at all.

Deal value gets modeled in spreadsheets. It gets protected or destroyed by whether the people expected to deliver it feel like anyone accounted for what the change actually cost them. That is not a soft consideration bolted onto the real integration work. It is the integration work, for the parts of the business that cannot be migrated on a server cutover schedule.

Key Takeaway

Change management is not a messaging exercise. It is the workstream that protects the people who make the deal thesis real. If it is under-resourced, the integration can look green on every operational milestone and still fail where it counts.

If you are heading into an integration and want the human side resourced as seriously as the systems side, I can help you build that plan.