Three months after closing, the integration steering committee reviews the finance workstream. The status is yellow trending red. The reason, on inspection, is never the integration work itself — it's everything that got attached to it.
Somebody decided that since the acquired entity's chart of accounts had to be mapped anyway, this was the moment to redesign the group's account structure. Since reporting had to be connected, why not implement the new consolidation tool? Since processes were being documented, surely now is the time to standardise them group-wide.
Each addition sounded efficient. Together, they put a strategic transformation programme on the critical path of a compliance deadline.
Two kinds of work that look alike
Integration is urgent and compliance-driven. The acquired entity must be controlled from Day 1: payments authorised, payroll running, cash visible. It must report into group consolidation by a date the CFO has already promised the audit committee. It must meet statutory obligations that don't pause for the deal. Integration work has external deadlines, binary outcomes, and a clear definition of done.
Transformation is strategic and mandate-driven. Harmonising systems, redesigning processes, capturing synergies, building the operating model the combined group deserves. This work is valuable — often it's the thesis of the deal — but its deadlines are chosen, its scope is negotiable, and its definition of done is a leadership decision, not a filing date.
Integration deadlines are set by regulators, auditors and the group calendar — you can't move them. Transformation timelines are set by leadership — you can. Put both on one list, and it's always the fixed deadlines that end up slipping.
The grey zone is where value leaks. Transformation items dressed as integration items inflate the critical path, exhaust the team that has to deliver the non-negotiables, and — the quiet cost — burn the acquired company's goodwill on changes that weren't actually urgent.
The two-list method
The discipline we apply on every transaction is almost embarrassingly simple, which is why it works under deal pressure.
The Two-List Method
List A — Integration. Admission requires a YES to: "Does a regulator, auditor, bank or group reporting deadline force this by a fixed date?" Each item gets a deadline, an owner on each side, and a definition of done. List A is allowed to be boring. It is not allowed to be late.
List B — Transformation. Everything else, however sensible. Each item gets a business case and waits for a mandate: sponsor, budget, timeline decided on its own merits — usually after Day 100, when the organisation can think straight again.
The rule: moving an item from B to A requires naming the external deadline that forces it. "It would be efficient to do it now" is not a deadline. In our experience, fewer than one in five proposed migrations survives that question.
What this looked like in practice
On a large healthcare acquisition we supported, the acquired group's twelve entities had two quarters to report into group consolidation. The initial integration plan contained 140 items. Applying the two-list test moved nearly half of them to List B — including a full ERP consolidation that, on its own merits, was later approved as a two-year programme with proper funding.
The integration list that remained was deliverable: reporting mapped to the group chart of accounts via a translation layer (not a redesign), governance and signatories integrated, statutory calendar secured. Every deadline was met. And the transformation programme started months later with something it would never have had as a stowaway: its own mandate, its own budget, and a team that wasn't already exhausted.
Three questions for your next deal
- Can you name the external deadline for every item on your integration plan? If not, you're looking at List B items in disguise.
- Does your integration plan survive the departure of goodwill? Acquired teams cooperate generously for about a hundred days. Spend that goodwill on the non-negotiables.
- Who is guarding the boundary? Someone in the IMO must own the two-list discipline — because every function will lobby to reclassify its pet project as "integration-critical".
Integration has a deadline. Transformation has a grey zone. Keep them on separate lists, and both get delivered. Merge them, and the deadline funds the grey zone until something breaks.