Application Portfolio Management (APM) Best Practices

Overview

Rationalization Postures classify applications by what the organization should do with them now, based on current assessment of business value and technical fitness. Strategic Dispositions serve a different and complementary purpose: they declare where the organization intends to take each application over the strategic planning horizon. A Rationalization Posture is an assessment output — it emerges from evidence gathered during the rationalization review cycle. A Strategic Disposition is a strategic declaration — it is set by architecture governance and strategic planning, reflects organizational intent rather than current condition, and remains in force across multiple assessment cycles until a deliberate governance decision changes it.

The distinction matters in practice. An application can carry a Tolerate posture — meaning its current condition does not warrant active investment or immediate retirement — while simultaneously carrying a Move-Away disposition, meaning the organization has declared a strategic intent to migrate away from it over time regardless of its current operational acceptability. Conversely, an application can carry a Migrate posture — meaning its technical fitness requires modernization — while carrying a Move-To disposition, meaning it is the organization’s declared strategic target and investment in its modernization is fully justified by that strategic intent. Neither framework alone produces the complete strategic picture. Together they give the organization both a current assessment and a declared direction for every application in the portfolio.

Strategic Dispositions also operate at two levels within the enterprise. At the application level — addressed in this document — dispositions declare the organization’s intent for each specific application in the portfolio. At the technology level — governed by Technology Portfolio Management and addressed in the IF4IT Technology Portfolio Management Best Practices document — dispositions declare the organization’s intent for each technology platform, framework, or runtime environment. Technology-level dispositions directly influence application-level dispositions: when a technology carries a Move-Away disposition in the Technologies Inventory, every application built on that technology inherits a strategic pressure that the application-level disposition should reflect. Organizations are encouraged to govern both levels and to connect them explicitly in the Enterprise Model.

Best Practice

It is recommended that every application in the portfolio carry an explicitly assigned Strategic Disposition that is reviewed and reaffirmed at least annually as part of the portfolio governance cycle. The following five dispositions represent the IF4IT suggested vocabulary. Organizations are encouraged to adopt these dispositions as defined, adapt the definitions to reflect their own strategic context, or define an entirely different disposition vocabulary that better serves their organizational needs. The critical requirement is not adherence to any specific vocabulary but the consistent, governed use of whatever disposition framework the organization adopts — applied to every application, reviewed on a defined cadence, and used as a primary input to investment, rationalization, and roadmapping decisions.

Move-To — The organization has declared this application as a strategic target. It is the intended destination for capabilities currently served by other applications. Active investment in this application is justified by its strategic role. Migration of related workloads toward it is encouraged and may be mandated by architecture governance. A Move-To disposition does not guarantee indefinite retention — it reflects the organization’s current strategic intent and should be reviewed whenever the strategic context changes.

Sustain — The organization intends to maintain this application at its current capability level for the foreseeable planning horizon. It is neither a strategic target attracting new workloads nor a candidate for active migration or retirement planning. Investment is limited to maintenance, compliance obligations, and minor enhancements required to maintain current capability. A Sustain disposition is not a default — it is a deliberate declaration that the current state of the application is appropriate for the organization’s current and foreseeable strategic needs.

Move-Away — The organization has declared a strategic intent to migrate away from this application toward an alternative over the planning horizon. New adoption is discouraged or prohibited. Existing usage is maintained operationally until migration to the alternative is complete. Active planning for the replacement or migration is underway or expected to begin within the current planning cycle. A Move-Away disposition differs from a Retire disposition in that it implies the capability the application serves will be preserved in a successor — the vehicle changes, not the capability.

Avoid — The organization has determined this application should not be adopted or expanded under any circumstances in the current planning horizon. It may exist in the portfolio in a legacy capacity that is operationally tolerated, but no new usage is permitted and no investment beyond the minimum required to maintain current operational state is authorized. An Avoid disposition signals organizational consensus that this application represents a direction the enterprise is not willing to move further toward, regardless of its current operational condition.

Retire — The retirement decision has been made, a timeline is established, and the decommissioning process is actively in progress or imminent. Retire is distinct from Move-Away in that it implies the capability itself is being eliminated rather than transferred to a successor application. No replacement is planned. Resources currently consumed by the application will be redirected upon retirement.

The five IF4IT Strategic Dispositions arranged from most to least favorable, with a continuous color scale from green to red. Organizations are encouraged to adapt these definitions and scoring criteria to their own strategic context.

Organizations should define the specific criteria they will use to assign and review each disposition. Criteria typically address dimensions such as strategic alignment with current organizational priorities, architectural fit with the target state architecture, vendor health and product roadmap viability, total cost trajectory, user adoption and engagement levels, regulatory and compliance trajectory, and the availability and maturity of alternative solutions. It is recommended that organizations weight these criteria explicitly — rather than applying them through informal judgment — and derive disposition thresholds from the weighted scores, producing a repeatable and defensible disposition assignment process that can be consistently applied across the full portfolio and consistently explained to governance bodies, business leaders, and application owners.

Benefit(s)

Strategic Dispositions give the portfolio a forward-looking governance layer that Rationalization Postures alone cannot provide. Every application in the portfolio has not only a current assessment but a declared organizational intent — a governance statement about where the organization is heading with that application that persists across assessment cycles and anchors investment, migration, and roadmapping decisions in explicit organizational strategy rather than point-in-time condition. Dispositions make portfolio strategy visible and communicable: a portfolio map showing every application’s current Rationalization Posture alongside its Strategic Disposition tells a complete and actionable story that neither dimension alone can tell. Leadership can see at a glance which applications are strategic targets attracting investment, which are being sustained at current levels, which are earmarked for migration, which are being avoided, and which are in active retirement — and can evaluate whether that collective disposition profile reflects the organization’s actual strategic priorities or reveals misalignments that governance should address.