<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Top 3 Reasons That So Many Mergers &amp; Acquisitions Fail</title>
	<atom:link href="http://www.beaconintegration.com/resources/merger-blog/2009/07/top-3-reasons-that-so-many-mergers-acquisitions-fail/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.beaconintegration.com/resources/merger-blog/2009/07/top-3-reasons-that-so-many-mergers-acquisitions-fail/</link>
	<description>This blog is dedicated to technology aspects of Mergers &#38; Acquisitions</description>
	<lastBuildDate>Mon, 13 Jul 2009 13:26:51 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Alexander</title>
		<link>http://www.beaconintegration.com/resources/merger-blog/2009/07/top-3-reasons-that-so-many-mergers-acquisitions-fail/comment-page-1/#comment-409</link>
		<dc:creator>Alexander</dc:creator>
		<pubDate>Mon, 13 Jul 2009 13:26:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.beaconintegration.com/resources/merger-blog/?p=215#comment-409</guid>
		<description>I think your point about failure of achieving commonality in business processes and information systems is spot on! Many companies that undergo a merger hang onto legacy systems for years. This not only represents an opportunity lost in terms of synergies that could be achieved by eliminating redundancies, but also becomes a drag on any new initiatives or campaigns the combined entirety may undertake in the future. Any new information system or business processes will need to account for incorporating legacy systems into their planning, design, deployment, and maintenance. The problem is exasperated by each redundant system. The more redundancy, the greater the drag on every project the combined entity embarks on. This stifles cross sell an organic growth, and increases capital and one time expenditure required to deploy any new systems. The hidden cost of maintaining legacy systems after a merger is virtually immeasurable.</description>
		<content:encoded><![CDATA[<p>I think your point about failure of achieving commonality in business processes and information systems is spot on! Many companies that undergo a merger hang onto legacy systems for years. This not only represents an opportunity lost in terms of synergies that could be achieved by eliminating redundancies, but also becomes a drag on any new initiatives or campaigns the combined entirety may undertake in the future. Any new information system or business processes will need to account for incorporating legacy systems into their planning, design, deployment, and maintenance. The problem is exasperated by each redundant system. The more redundancy, the greater the drag on every project the combined entity embarks on. This stifles cross sell an organic growth, and increases capital and one time expenditure required to deploy any new systems. The hidden cost of maintaining legacy systems after a merger is virtually immeasurable.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
