Application Portfolio Management (APM) Best Practices - Rationalize the combined portfolio - identify and resolve redundancies between acquirer and target
Application Portfolio Management (APM) Best Practices
Rationalize the combined portfolio - identify and resolve redundancies between acquirer and target
Overview
The application portfolio of an acquired organization almost always contains applications that perform functions already performed by applications in the acquirer’s portfolio. ERP systems, CRM platforms, collaboration tools, HR systems, and countless operational applications are typically duplicated across the two organizations because both organizations independently built or procured solutions to the same business needs before the acquisition brought them together. Without a systematic redundancy identification and resolution process, both instances of every redundant application continue to operate indefinitely - generating double the cost, double the support burden, and double the operational complexity of a rationalized alternative. The deal value the acquisition was expected to generate through operational synergies is not realized because the redundant, unrationalized portfolio continues to cost as if the two organizations had never combined.
Best Practice
Conduct a systematic redundancy analysis of the combined portfolio within the first ninety to one hundred eighty days post-close, using the integration roadmap as the framework for sequencing remediation. Map every application in both portfolios against functional categories and identify functional overlaps where both organizations maintain applications serving the same business purpose for the same or consolidable user populations. For each functional overlap, conduct a comparative assessment using the standard assessment framework: business value, technical fitness, cost, user base size and engagement, and migration complexity. Develop a rationalization plan that identifies the surviving instance for each functional area and sequences the migration and retirement of the redundant instance in an order that manages organizational change and operational risk.
Benefit(s)
Systematic post-acquisition rationalization captures the operational synergies that M&A investment cases typically promise but that are only realized through active, deliberate portfolio management rather than passive integration. Redundant applications are retired, eliminating their full cost contribution from the combined portfolio. The operational complexity of managing two instances of the same business function is reduced to the complexity of managing one well-governed instance. The combined portfolio is leaner, less expensive, and more coherent than the unrationalized combination - delivering the tangible technology integration benefits that justify the M&A investment.
Copyright for the International Foundation for Information Technology (IF4IT): 2008 - Present
Legal Disclaimers