Creating an Integration Playbook
The following is a sample playbook, an aggregation of many of the tools and much of the advice offered in this book. The purpose of this playbook is to give you an idea of how all of the integration plan elements can be packaged together to help you involve the stakeholders who will become a successful part of your integration project.
If your organization is going to be integrating merged or acquired companies frequently, having a working playbook is a good idea. However, playbooks are fluid and never complete; they should continually be optimized by lessons learned from previous integrations.
I'm amazed when I talk to companies that have frequent integration activities but have no standardized approach. It's an exercise in reinventing the wheel each time there's an integration activity. Integration work is hard enough as it is, so developing a playbook will help your company adopt some standardized and repeatable processes and tools it can leverage for future integration activities.
Keep in mind that it is important to create something that can aggregate organizational competency, like a playbook, but that it should be continually improved and updated after each integration.
A typical playbook's contents might look like the following lists that show some of the most common topics discussed in this book. These are presented in a fairly intuitive order, based on the key planning phases.
Setup, Planning, and Execution ...