It can take years after a merger has been declared "complete" for the IT processes and systems to be truly merged. Over the years, we've all seen stories in the business press about this sort of thing, and yet it keeps happening, despite what can be dire consequences.
I'm sure you aren't reading it here first, but it's worth repeating: The merging of IT processes and systems should be planned as soon as negotiations are finalized, and the integration of IT staff and systems should begin as soon as the legal documents are signed. There are many reasons why this is important. Here are some of them:
Disappointed consumers. Shortly after the American Airlines/USAir merger was announced, the two carriers announced that they would share frequent-flier numbers and associated elite status rankings. For several months, this seemed to work as advertised. Recently, however, a frequent flier with over 3 million American miles traveled on USAir; while the computer accepted his American frequent-flier number, it did not recognize his elite status and did not grant early boarding or better seating, as American would do. The gate agents eventually made the adjustments, but the traveler was frustrated, given the expectations set by the merger. Disappointed customers sometimes seek alternate products
Unmet large-account expectations. Customers, especially the biggest accounts, expect to receive better service or more product choices after a merger. A few years ago, a specialty manufacturing company became a global, $10 billion organization as a result of multiple mergers and acquisitions. Customers who bought from 10 to 15 different suppliers found that MegaManufacturer now offered a much more complete product line. Unfortunately, MegaManufacturer did not integrate the sales force or internal systems quickly, forcing customers to order from multiple sales reps and preventing consolidated billing. MegaManufacturer invested in full integration only after several large customers threatened to depart.
Fragmented loyalty. Until there are visible breaks with the past (business objectives, systems, management structures, etc.), most employees remain loyal to their old business unit. Frequently, business units don't cooperate and even put individual business unit priorities ahead of the new organization's objectives. Efforts to create a new enterprise culture are crucial.
After several acquisitions, one multi-brand restaurant chain began expanding geographically. New stores were included in each brand president's objectives. At one point, brand development teams even bid against one another for new store sites, artificially inflating the prices. The brand management met their objectives, but the extra cost of the internal bidding war reduced company earnings and impacted shareholder value.
Eroding ITservice levels. Integrating IT infrastructure and foundational IT systems is an enormous and complex undertaking. It is also an opportunity to address necessary projects that never get approved. For example, funding for standardization, DRP and single sign-on are often neglected, but are significant components of a reliable and cost-effective infrastructure.
Sign up for CIO Asia eNewsletters.