Author
Abstract
Growth by acquisition strategies is risky, first, because often the acquiring firm is uncertain about exactly what is being acquired, and second, because justifying the costs of acquisition is dependent on how well the firms can be integrated to achieve the necessary savings and/or increased market opportunities. In addition to integrating staff and processes, a key integration that must also take place is that of information technology systems. In knowledge intensive industries, such as banking, successful integration of technology platforms, especially software, hardware and networks, is critical to the long-term success of any acquisition strategy. This paper studies the growth by acquisition strategy embarked upon by a mid-sized UK bank, the Co-operative Bank; this strategy was a disaster, leaving a heretofore successful bank in dire trouble and on the block for buyers at a substantial discount to its original value. The case is an example of a board failing to manage its strategic risks and, in particular, its strategic technology risks. In 2008, the board of the Co-operative Bank, backed by its parent the large and profitable Co-operative Group, took the decision to acquire a larger competitor to increase its market penetration. However, despite being well capitalized, the execution of the strategy was botched, not least as regarded the replacement of the bank’s “core banking systems†to accommodate the larger, merged bank. This paper first provides some background on the bank as it embarked upon its growth strategy, before discussing the topics of strategic risk and strategic technology risks, in particular the risks in so-called core systems replacement programs. The events that caused the Co-operative Bank to fail so disastrously are then described, and finally the lessons that can be drawn are discussed.
Suggested Citation
Handle:
RePEc:rsk:journ3:7652121
Download full text from publisher
Corrections
All material on this site has been provided by the respective publishers and authors. You can help correct errors and omissions. When requesting a correction, please mention this item's handle: RePEc:rsk:journ3:7652121. See general information about how to correct material in RePEc.
If you have authored this item and are not yet registered with RePEc, we encourage you to do it here. This allows to link your profile to this item. It also allows you to accept potential citations to this item that we are uncertain about.
We have no bibliographic references for this item. You can help adding them by using this form .
If you know of missing items citing this one, you can help us creating those links by adding the relevant references in the same way as above, for each refering item. If you are a registered author of this item, you may also want to check the "citations" tab in your RePEc Author Service profile, as there may be some citations waiting for confirmation.
For technical questions regarding this item, or to correct its authors, title, abstract, bibliographic or download information, contact: Thomas Paine (email available below). General contact details of provider: https://www.risk.net/journal-of-operational-risk .
Please note that corrections may take a couple of weeks to filter through
the various RePEc services.