Integrate or not to integrate
- This topic has 5 replies, 6 voices, and was last updated 1 week, 1 day ago by
.
-
Posts
-
Integration Is a Choice. Value Creation Is the Goal.
Some key takeaways and key points on decision integrate or not to integrate, what other considerations come to your mind?
1st. Integration is not the objective, value creation is. Integration should enable the strategic rationale and synergies of the deal.
2nd. The deal rationale should determine the level of integration. Capability-driven acquisitions may require autonomy, while scale-driven acquisitions may benefit from deeper integration.
3rd. Integration needs to start early. Bringing integration expertise into the deal lifecycle helps challenge assumptions, identify complexity and build a realistic business case.
4th. Expect the unexpected. Cost, complexity and timelines are often underestimated. Once you gain access to the acquired organization, assumptions need to be tested and sometimes changed.
5th. Stay close to people. Transparency, communication and a compelling “why” are critical to maintaining engagement and retaining talent.
6th. Adapt when reality changes. A good integration plan is a guide, not a rigid script. If the data changes, the plan should change too.
7th. Ultimately, successful integration is not a cookie-cutter exercise. It requires strategic clarity, realistic expectations, strong governance and the ability to adapt.Good considerations! One additional thought: integration does not necessarily have to be an all-or-nothing decision. It can make sense to integrate selectively by function, depending on where standardization creates value and where preserving the targets strengths is more important.
I like this phrase: “Integration is not the objective, value creation is”. It is important to include in this process a “look-back analysis” to measure the actual results vs the deal case assumptions to make sure that the integration or non-integration is delivering the expected results.
I agree, particularly that integration should be driven by the deal rationale rather than treated as an end in itself. Equally important is protecting business continuity while pursuing synergies. Clear accountability, realistic timelines and regular reviews of the business case help ensure integration decisions deliver sustainable value without undermining existing operations.
Bjoern, “integration is a choice, value creation is the goal” is a great way to put it, and I agree the deal rationale should drive the level of integration.
What I’d add, from the IMAA C-suite sessions, is that the choice is best made much earlier than most people expect, during target selection and diligence rather than after signing. Martin Howard’s “begin with the end in mind” point was that as soon as you start learning about a target, you should be asking whether you’ll fully combine, run it largely independently, or use a hybrid. That choice changes what you look for in diligence, how senior the transition team needs to be and how much outside help you need.
Two of his examples show diligence answering the “integrate or not” question for you. In one, a records business expected synergies from combining production, but diligence showed both companies were largely manual, so there were no savings to capture by integrating. They chose a looser cooperation instead of an acquisition. In the other, the value of a full combination depended on a software platform that turned out to need a near-rebuild, and the buyer walked away.
On customers, he made a point I hadn’t considered: being part of a larger group can be a selling point in some sectors, but where value sits in a personal relationship (he mentioned a physical therapist or a financial adviser), clients may see the acquirer as a “faceless corporation”. That seems like a strong argument for lighter integration of client-facing teams even when back-office functions are combined, which fits the “integrate selectively by function” idea from the earlier reply.
Hi Bjoern, I am going to have to disagree with you on a few of your points. While I absolutely agree on your thesis that ‘Integration Is a Choice. Value Creation Is the Goal’, I am a believer that integration archetypes are a stagnant consideration, they can be designed as a repeatable delivery framework, and that a shift in an integration archetype, though technically possible, represents a massive issue as it completely shifts the overall value-creating objectives of the integration thesis itself. I believe that an archetype, or a mix-use archetype in the instance where you may have differing workstreams following differing archetypes, should be a set and repeatable delivery structure defined across core integration workstreams. It sets the guardrails and what is generally considered ‘in scope’ vs ‘out of scope’ for the different functional areas. It is therefore inappropriate to change what is ‘in scope’ vs ‘out of scope’ after a project starts, as that affects the deal financials, the work to be completed over the already-set timeframe, and the change management expectations of the end users. Changing an archetype mid-integration should not be an option, because it fundamentally represents a miss from the corp dev team in shaping their deal thesis, and all teams who are tracking toward set value drivers then are aiming for an unrealistic goal.
I think your points 1-5 have merit, but your items 6 and 7 are a clear signal that someone high up made a serios mistake which can and probably will cost the firm a large sum of money. Those are the kinds of errors that cost people their jobs.
- You must be logged in to reply to this topic.