Integration playbooks look impressively thorough in the deal process. 

Detailed workstreams, clear milestones, named owners for every task. What they consistently underweight is the difference between a task being theoretically assigned and a task actually happening on an ordinary Tuesday, when the person nominally responsible for it is also dealing with three other urgent things that have nothing to do with the integration plan. 

The pattern that plays out most often: the integration playbook assigns a specific workstream, say systems consolidation, to a specific senior person, and that person genuinely intends to drive it forward. 

But that same person is also running a piece of the core business day to day, and integration work, however important strategically, rarely feels as urgent on any given Tuesday as whatever operational fire is currently burning. 

Six weeks in, the integration workstream owner hasn’t actually made much progress, not because the plan was wrong, but because nobody built in the actual time and headspace required to execute it alongside an already full role. 

The playbooks that actually work tend to share one specific feature that’s easy to skip when building the plan under deal timeline pressure: dedicated integration capacity that isn’t also running a piece of the existing business. 

Whether that’s a dedicated integration lead, a temporary consultant, or explicitly carved-out time for an existing senior person with their other responsibilities genuinely reduced rather than just nominally deprioritised, integration work that competes for the same hours as running the business tends to lose that competition, quietly, week after week, until the plan is meaningfully behind and nobody can point to exactly when that happened.