Manage the organizational and cultural dimensions of technology portfolio integration

Overview

Technology portfolio integration is not only a technical exercise — it is an organizational and cultural one. Engineering teams have professional and sometimes personal attachments to the technology stacks they have chosen, built expertise in, and standardized on. Teams whose preferred technology is designated as the deprecated instance rather than the surviving standard experience the consolidation as an organizational and sometimes personal loss. Teams asked to migrate to the acquirer’s technology standards may resist a transition they perceive as the acquirer imposing its preferences rather than objectively selecting the best available option.

Best Practice

Address the organizational and cultural dimensions of technology portfolio integration as explicitly as the technical dimensions, with defined owners and defined activities in the integration roadmap. Communicate the rationale for every consolidation decision in terms that acknowledge the quality and history of the technology being deprecated and recognize the disruption migration creates for the engineering teams involved. Where feasible, involve engineers from both technology stacks in migration planning. Select surviving technologies based on objective assessment criteria — already established through the Technology Assessment and Rationalization discipline — and communicate those criteria transparently so consolidation decisions are understood as merit-based rather than politically motivated by acquirer preference.

Benefit(s)

Actively managing the organizational and cultural dimensions of technology portfolio integration reduces the resistance that delays consolidation programs during the critical post-acquisition period when organizational trust is being established. Engineering teams who feel their technology choices were evaluated fairly accept consolidation outcomes more readily and remain more productive through the transition period.