Application Portfolio Management (APM) Best Practices

Overview

Applications depend on people in ways that are rarely captured in technical documentation. The developer who built a custom module and is the only person who understands its architecture and data logic. The operations engineer who knows the undocumented workarounds that keep a legacy system running. The business analyst who maintains the data quality procedures that no one else has ever been trained on. When these individuals leave the organization, they take with them knowledge that cannot be recovered from documentation because the documentation was never created. Key-person dependency is one of the most common and most underestimated risks in enterprise application portfolios.

Best Practice

Connect every application in the portfolio to the people inventory entries that represent significant human capital dependencies. For each dependency, capture the person’s name, their role in relation to the application, the nature of their unique knowledge or capability, and whether a succession plan or knowledge transfer plan exists. Flag applications with unmitigated key-person dependencies as elevated risk items in the portfolio risk register. Use this mapping as an input to workforce planning, knowledge management investment, and retirement planning - applications with high key-person risk require knowledge transfer as a prerequisite to any significant change, retirement, or team transition.

Benefit(s)

Connecting APM to the people inventory makes key-person dependencies visible as a manageable risk rather than an invisible vulnerability that is discovered only when the person leaves. Knowledge transfer investments are directed to the applications with the highest unmitigated dependency risk before those risks materialize. Retirement planning accounts for the cost and complexity of knowledge recovery. The organization develops a human capital perspective on its application portfolio that the technical and financial perspectives alone cannot provide.