A playbook is only worth having if the previous integration's failures are in it.
Why it matters when the plan changes
Serial acquirers do the same integration repeatedly and usually learn nothing systematic, because the people change and the lessons stay with them. Post-merger integration combines the logistical, social and technical systems of two organisations into one, so the playbook is sequencing dependencies and cross-team commitments, not just tasks. A playbook is how a group builds a capability rather than a sequence of individual efforts, and it is the difference between the fourth acquisition being easier than the first and being the same.
The tension is between a method and a template. A playbook that specifies activities produces compliance with a process; one that specifies which decisions have to be settled and by when produces integration. Research on strategy execution found only nine per cent of managers say they can rely on colleagues in other functions and units all the time, the condition an integration playbook must work against. The first is easier to write and audit, and it is the version most groups end up with.
In practice
A group's playbook specifies a hundred and forty activities across eight workstreams. It does not say who settles a pricing conflict between the acquired business and the platform. That question arises in every integration the group has done, has been answered differently each time, and appears nowhere in the document.
Evidence
Integration combines the logistical, social and technical systems of the merging organisations into one, which is what a playbook has to sequence.
Post-merger integration, Wikipedia (2026)Cross-unit commitments are the least reliable part of execution, which is what an integration creates at scale.
Donald Sull, Rebecca Homkes and Charles Sull, Why Strategy Execution Unravels and What to Do About It, Harvard Business Review (2015)
What it cannot tell you
A playbook cannot tell you whether the decisions it lists will actually be settled by the people it names, or whether cross-business commitments will hold under pressure. It describes method, not the discipline to follow it, and a well-written document can sit alongside the same unresolved conflict every time.
Questions
The decisions that have to be settled, who settles each, and by when, ahead of the activities. Research published in Harvard Business Review found only nine per cent of managers can rely on colleagues in other functions all the time, which is why decision ownership matters more than task lists.
By recording what went wrong last time and what would have prevented it, which requires someone to conduct an honest review after each integration. Groups that skip the review keep a document that reflects the first integration and repeat every subsequent lesson.
The decision list generalises better than the sequence. Which questions have to be settled is stable across integrations of a similar type; how fast and in what order depends on size, overlap and whether systems are being merged. Both parts should be present and separated.
Whoever is accountable for integration outcomes across the group, not a corporate development function that hands over at close. The Wikipedia entry on post-merger integration (2026) describes combining logistical, social and technical systems into one, work that continues well past deal completion and needs a durable owner.
That the same question is answered differently in each integration. If nobody can say who settles a recurring cross-business conflict, the document is recording activity rather than method, however comprehensive its list of activities happens to look on the page.