Establish an enterprise-wide APM governance model

Overview

Without a defined governance model, APM decisions are made inconsistently and without accountability. Different teams apply different standards to what belongs in the portfolio. Applications are introduced without review, modified without oversight, and retained beyond their useful life because no clear authority exists to challenge or retire them.

Over time, this lack of governance produces predictable outcomes: duplicated capabilities, rising costs, unmanaged risk, and increasing technical debt. Complexity does not accumulate through deliberate strategy—it accumulates through the absence of decision discipline. An APM capability without governance is not operating as a program; it is reacting without control.

Best Practice

Establish a formal, enterprise-wide APM governance model that defines decision rights, lifecycle control points, and enforcement mechanisms across the entire application portfolio.

At a minimum, the governance model should clearly define:

• Which applications are in scope for portfolio management

• The required process for proposing, assessing, approving, operating, and retiring applications

• Who holds decision authority at each stage of the application lifecycle

• How conflicts between business units are escalated and resolved

• How compliance with governance standards is monitored and enforced

Document this model as a formal APM Governance Policy. The policy should be published, communicated to all stakeholders, and reviewed regularly to ensure it remains aligned with organizational priorities and operating models.

Limit the number of people with decision authority over each portfolio action — involving too many approvers slows decisions and creates bottlenecks.

Benefit(s)

A defined governance model with clear decision makers transforms APM from a collection of isolated decisions into a disciplined, accountable enterprise capability. Portfolio changes are evaluated before they occur rather than rationalized after the fact. Applications enter, evolve, and exit the portfolio through controlled processes aligned to business and technology strategy.

Decision-making becomes consistent because authority and process are clearly defined. Technical debt is actively managed rather than passively accumulated. Leadership gains confidence that the portfolio reflects intentional organizational choices, with known trade-offs, rather than the unintended consequences of ungoverned growth and deferred decisions.

Best Practice

Instead of creating new and separate meetings for APM governance and control, look to weave it all into existing Architecture Review Board (ARB) and/or Technology Review Board (TRB) meetings, if you already have them.

Benefit(s)

Doing so ensures APM acts as air-traffic-control for architecture and technology governance meetings by ensuring all decisions are informed by the APM and all decisions get fed back into the APM – in near real time.

Additionally, APM conversations become a normal and regular part of the agenda, filling the agenda gap during periods when initiative and project related agenda items ebb.