Tuesday, 8 June 2010

Knowledge Management in mergers and acquisitions

Knowledge management delivers maximum value when applied to high value knowledge, to support high value decisions, and in areas where that knowledge is otherwise at risk of being lost. A typical high value area is Mergers and Acquisitions. These are high cost, complex operations, where crucial decisions need to be made very well, and yet happen relatively rarely, so it is easy for tacit knowledge to be lost. People caught up in the high pressure activity can easily forget the detail of how the decisions were made, and fail to pass the knowledge on to future mergers and acquisitions teams. This combination of high value decisions made relatively infrequently, so that human memory alone cannot be relied on as a knowledge store, means that there is great value on documenting the learning for use in future mergers, acquisitions and divestments

The approach to KM for Mergers, Acquisitions and Divestments would be as follows;

Learning Before. Through Peer assists, the M&A team would seek to acquire lessons, guidance, success factors and pitfalls from previous Mergers, Acquisitions and Divestments.

Learning During. If possible, and for high value Mergers, Acquisitions and Divestments only,a Learning Historian would be seconded to the M&A team to capture lessons, practices and key documents as the exercise progressed, perhaps through a series of After Action reviews.

Learning After. Interviews and Retrospects of the key players would be held to determine the success factors to repeat, and the pitfalls to avoid. The focus will be on capturing tacit knowledge and experience; the 'golden rules', 'top tips', recommendations and advice that will allow success to be repeated routinely. This might include interviewing any external consultants who had been an integral part of the team.

Knowledge Asset. Output from the interviews and the Retrospect will be packaged into a knowledge asset; a web-based package or secure wiki that provides helpful accessible advice for future re-use. This advice will be at varying levels of detail; from the managerial overview of the "top 10" bullet points, down to operational advice.

Case History

The learning approach outlined above was applied by Company A to their merger with Company B, and again with Company C two years later. In the latter case, 14 of the core acquisition team were interviewed, and lessons were derived on leadership, the team and team processes, the role of the investment bank, the transaction process, communication, and staff issues. One year after acquisition, 31 staff were interviewed to gather lessons on the Integration process. Interviewees included the Chief Counsel, one of the Country unit Presidents, and several other very senior staff. Learnings were captured on topics such as managing the Integration project, dealing with delay, and getting ready for Day 1 of the integrated company.
Lessons from the first merger were used to guide the process for for the second, and lessons from the second acquisition and integration were used to guide the process for several further acquisitions. The value of the knowledge management approach was seen in the reduced involvement of external consultants in successive mergers. Initially the bill to Big 5 consultants had been very high, but this reduced from one acquisition to the next as Company A internalized the knowledge.


Md Santo said...

My suggestion is, take notes that merged organizations each had their own cultures, processes, terminology and technology. Understanding how best to rationalize these organizations is only possible using models at an enterprise level – hence the recent upsurge in interest in Enterprise Knowledge Architecture. By referring to Ian Bailey (2006) it is suggested that : Enterprise Knowledge Architecture closes the gap between business and IT. It provides a way for management to understand the consequences of their decisions and allows simple questions to be asked about complex organizations. It is difficult to measure specific cost benefits of an Knowledge Architecture approach, but figures are starting to emerge that show how IT disasters can be averted by closing the gap between business and IT. On Knowledge Architecture, visit our K-base http://delicious.com/mobeeknowledge/knowledgearchitecture with special emphasized on http://mobeeknowledge.ning.com/forum/topics/enterprise-architecture-ea

Nick Milton said...

Well, that may or may not be the case, but I would rather let the lessons speak for themselves. To be honest, in none of the M&A knowledge management exercises that I have been involved with has anyone said "the most important thing in ny future merger is to have an Enterprise Knowledge Architecture".

Blog Archive