The High Cost of "Let's Circle Back"
You’ve seen the playbook before. The deal closes. The 100-Day Plan looks pristine in PowerPoint. Then, week four hits. The Steering Committee meets, and instead of decisions, you get updates. The IT integration lead is waiting on the CFO for budget approval, the CFO is waiting on the CISO for a risk assessment, and the CISO is waiting on a vendor who doesn't know who their point of contact is anymore.
This isn't an execution problem; it's a governance failure. In Private Equity, time isn't just money—it's IRR. McKinsey analysis suggests that up to 50% of anticipated deal value is lost due to slow or ineffective integration. The culprit is rarely technical incompetence. It is almost always decision latency—the time lag between identifying a problem and making the call to fix it.
Most portfolio companies try to solve this with more meetings. They create "integration councils" and "working groups" that function as massive, consensus-driven bottlenecks. They confuse being informed with having veto power. To protect your multiple, you need to strip the governance model down to its studs. You don't need a "collaborative culture" during the first 100 days; you need a dictatorship of competence.
The Private Equity IT Integration RACI Template
Standard RACI matrices (Responsible, Accountable, Consulted, Informed) fail in M&A because they are too democratic. In a turnaround or high-velocity integration, the "Consulted" column is where momentum goes to die. If you have more than two people in the 'C' column for a critical decision, you have already missed your timeline.
Here is the simplified governance model we deploy to unblock technical integrations in buy-and-build scenarios.
The Roles
- Steering Committee (SteerCo): The Operating Partner (You) and the PortCo CEO. They define the What and the When. They do not debate the How.
- Integration Management Office (IMO): The Program Lead. They hold the pen on the plan. Their job is to identify collisions between workstreams.
- Workstream Lead (WSL): The functional head (e.g., VP of Engineering, CIO). They own the execution.
The Matrix
| Decision / Activity | SteerCo (PE/CEO) | IMO Lead | IT Workstream Lead | CFO / Finance |
|---|---|---|---|---|
| Synergy Target Definition | A (Accountable) | C | C | R (Responsible) |
| Integration Budget Approval | A | R | C | R |
| ERP/CRM Selection | I (Informed) | C | A | C |
| Staffing / Headcount Reductions | A | R | C | C |
| Go-Live Decision (Go/No-Go) | I | A | R | I |
| Security Risk Acceptance | I | C | A | I |
Notice the deliberate lack of 'C's. The SteerCo is Informed on the ERP selection, not Consulted. Why? Because if you, the Operating Partner, are debating SAP vs. NetSuite, you are too deep in the weeds. If the CIO can't pick the right ERP, swap the CIO. Don't do their job for them.
The "Consulted" Trap: Where Synergies Die
The single biggest mistake I see in post-merger integrations is treating the 'C' (Consulted) as a 'V' (Veto). In a polite corporate culture, 'Consulted' implies that the person must agree before you can proceed. In a PE-backed integration, 'Consulted' means: "I will ask for your input because you have specific domain knowledge. I am under no obligation to use it, and if you don't respond by close of business Tuesday, I am moving on."
To enforce this, we implement the "Disgaree and Commit" rule. The IMO Lead has the authority to break ties. If the Sales VP wants Salesforce and the Service VP wants Zendesk, and they can't agree within 48 hours, the IMO decides. The decision is final. The cost of a suboptimal software choice is often lower than the cost of a three-month delay.
Defining the 'Accountable' One
There can never be two 'A's. Never. "Co-leads" are a lie we tell ourselves to avoid hurting feelings. If the row for "Data Migration" has both the Legacy CTO and the Acquiring CIO as Accountable, the migration will fail. One neck to choke. Usually, the acquiring CIO is the 'A', and the legacy CTO is a heavily leveraged 'R' or 'C'. If the legacy CTO blocks progress, refer to the Founder Extraction playbook.
Speed is the primary synergy. Your RACI matrix isn't just a document; it's a permission slip for your leaders to move fast without looking over their shoulders.
