A common question Forrester gets from organizations planning an application rationalization strategy is “How many applications should I aim for?” It is a good question, but can be symptomatic of an approach where less equals success. This is very common with executives and senior stakeholders, who often can take this type of singular view of application portfolios. While it is a straightforward way of examining your application portfolio, inherently it is a binary dimension. It does not account for the multiple prisms through which organizations should view and make decisions about their application portfolios.
Enterprise architects can help organizations determine where their objectives are placed on a wider range of applications continuums than just the number of applications, for example:
§ Customized Vs Standardized– What degree of customization do my organization's applications require? What differentiation does standardization provide? What is the opportunity cost of customization? What is the right balance for my industry sector ?
§ Control Vs Freedom – What level of freedom on application choice best serves my organization? How much control of the application portfolio is appropriate or mandated for my market and what is the cost of this? What is the cost/benefit of decentralization of choice compared with control of choice?
§ Centralized Vs Localized – What differentiation is provided by localized applications? What is the opportunity cost of centralized applications? What is the right balance of localized differentiation and centralized standardization for my organization?