handshake for divestment

Why CIOs need Enterprise Architecture to cope with Divestments

In a previous blog we discussed the architectural challenges that arise with mergers and acquisitions (M&A). Problems develop when the dealmakers have built their case on potential synergies without appreciating the work needed by the IT staff charged with reshaping and supporting the combined company’s business operating model. Sadly, we know of cases where the Chief Information Officer (CIO) has been excluded from early M&A discussions because of the paramount need for secrecy. But then when things go wrong, the blame is often unfairly pinned on the CIO.

How to Succeed

We argued that to improve the chances of success with an M&A venture, the CIO needs to be involved at an early stage: first, to establish what business value the synergies will deliver, and how this will be realised; second, to highlight the operational risks, by presenting views of the current enterprise architectures of each side of the planned merged company, as well as those of the future planned combined state. Even at a relatively high level, these contrasting views will reveal problems and opportunities that should inform the due diligence process.

We believe that similar considerations should apply to divestments (or divestitures, in American speak). At first sight, it might seem that divesting part of a business is a more straightforward challenge for the CIO than an M&A initiative, and in some ways it is. This is because the CIO is not directly concerned with the business logic of the divestment, just the technical complexity of the disconnection.

The other critical factor, however, is the limited amount of time available to complete the exercise. In most cases the disconnection has to be carried out cleanly within as short a time as possible, and this can put the IT function under extreme stress. The reasons for this time pressure are simple. When a company decides to divest part of its business, the sooner this can be done, the quicker the financial benefits will be realised. But more importantly, the longer the process is dragged out, the greater the likelihood that key staff within the divested business unit will be demotivated and decide to leave, thus diminishing its attraction to potential buyers.

In respect of divestments, what are some of the typical architectural issues?

Shared Services

The divested portion of the business will usually share common services with the rest of the company: procurement, finance, IT, HR, etc. A major concern here is whether some of the employees in these service functions will also transition out of the company and support the divested business. If none of the staff move with the divested business, these services may have to be built from scratch. Also, the portion of the overhead costs previously charged to the divested business will now be spread over the remaining business units, so there will be pressure to restructure and streamline the parent company’s service functions.

Business Process Dependencies

Unless the divested business is a completely stand-alone unit, there are likely to be critical dependencies with other parts of the business. This is particularly true when companies have implemented common systems and databases to serve their portfolio of business units. The problems involved in carving out chunks of these assets are likely to be exacerbated if the systems are poorly documented. The dealmakers will often be unaware of these dependencies and of the risks and costs involved in unscrambling them.

Data Management and Data Protection

A major issue is the ownership of customer, product and manufacturing data, and what can be shared between the parent company and the divested business. This is particularly important if the divested business unit is to be sold to a competitor. One often overlooked consequence of hiving off part of the business is that much historical data may no longer be relevant for comparison purposes.

Legal, Regulatory and Contractual Obligations

Licences, contracts and regulatory approvals will need to be revised in respect of the parent company and negotiated afresh for the divested unit. This is a tedious but necessary process that has to be done meticulously, so accurate knowledge of the relevant information will be necessary to avoid difficulties in this area.

Keeping the business going

During the transition period it will be important to ensure that the parent company and the business to be divested are both able to continue trading with minimal disruption. This may involve running parallel processes and systems until the separation is complete. This will inevitably be confusing for existing customers, particularly those who purchase products or services from both the parent company and the divested unit. The other problem here is that overworked staff may struggle to resolve conflicting priorities: keeping the divestment project on track or fixing the parent company’s problems.

 

Learning from Real Life

Sometimes the parent organisation commits to providing IT services for the divested business unit during an agreed period following the completion of the divestment. While this arrangement may help reduce disruption during the transition period, it can prove to be a poisoned chalice. We know of one company in the chemicals industry that concluded such an agreement to simplify and accelerate the divestment of a business unit. After the event it soon became clear that the parent company was not willing to give the divested unit the priority service that had been promised. Then, over a period of around six months, all the IT staff who had specialised knowledge of the divested unit’s systems left the parent company, and the deal subsequently collapsed. This had serious consequences for the hived-off business and its reputation with customers.

The lesson provides an important lesson that is relevant for any divestment situation. Unlike M&A initiatives, the parent company has little or no interest in the future of a divested business unit. Otherwise, it would not have wished to get rid of the unit in the first place. A clean break, with all the architectural challenges that this entails, should be the preferred way forward.

 

 

 

 

Contact Us