Introduction
One of the critical discussions in program management revolves around what happens after a project or program is successfully delivered. Who owns the sustainment phase, and how do we ensure long-term success? This question often creates tension between program management and business process owners, as it defines where responsibility transitions from project execution to ongoing operations.
According to the PMI Standard for Program Management (Fifth Edition), the program manager prepares the sustainment plan to realize the intended benefits. However, the business owns sustainment. While program management facilitates the transition, the long-term responsibility lies with operational teams.
Additionally, the contract agreed upon during the program formulation phase determines the length of benefits management and program support. This contractually defined period provides a structured timeline for transitioning responsibility from the program to business process owners.
This article explores the collaboration between program management and business processes to ensure value is sustained beyond program closure.
Sustainment Belongs to Business Process Management, Not Program Lifecycle
One key distinction to understand is that sustainment is not a temporary effort—it’s a function of ongoing business management. The program lifecycle ends at benefits realization, not indefinite support.
Why is this distinction important?
- Sustainment is an operational responsibility: Embedding and maintaining change in daily operations ensures the program’s impact continues.
- The project lifecycle must have a defined end: Without a structured transition, projects risk becoming perpetual efforts, consuming resources long after they should have closed.
- Contractual agreements set expectations: The Standard for Program Management states that the duration of benefits management is defined at the program formulation phase. This means program managers must clearly plan and communicate the transition period, ensuring that process owners are prepared to take over when the contractually defined support period ends.
Process owners—typically business unit leaders or operational teams—must own the sustainment phase. Their role is to integrate the newly introduced changes into standard business processes.
Change Management is Essential, But It’s a Shared Responsibility
Change management is a critical aspect of sustainment. While program managers initiate change through training, documentation, and stakeholder engagement, process owners must own long-term change adoption.
Practical Responsibilities:
- PMO: Ensures the program delivers change enablement activities, such as training, documentation, and stakeholder engagement.
- Process Owners: Take ownership of long-term change sustainment, reinforcing new behaviors and ensuring integration into day-to-day operations.
Because many organizations lack dedicated change managers, process owners must take accountability for ensuring change is sustained.
Clear Roles in the Transition from Program to Operations
To prevent ambiguity, a structured handover process is necessary. Such handover ensures a smooth transition from program execution to operational sustainment.
| Phase | PMO Responsibility | Process Owner Responsibility |
| Project Execution | Ensure project governance, deliver intended business value | Engage as key stakeholders in solution development |
| Deployment | Oversee implementation, ensure readiness criteria are met | Prepare operations for adoption |
| Handover & Closure | Ensure proper knowledge transfer, track value realization | Take full ownership of the new process |
| Sustainment | (Optional) Track impact in reports | Ensure continuous improvement and process embedding |
This structured approach ensures no confusion between project closure and sustainment ownership.
The Handover Process: Avoiding the ‘Dump and Run’ Problem
Many process owners resist taking ownership of sustainment, often citing concerns that projects are not fully ready. This reluctance typically stems from an unclear or insufficient handover process.
To ensure smooth transitions, the PMO should formalize the handover process with the following:
✅ Sustainment Readiness Checklist (e.g., completed training, documentation, defined KPIs)
✅ Formal Acceptance Process by process owners
✅ Defined Support Period (e.g., 30-90 days of post-closure support, as defined in the program contract)
The standard reinforces that the duration of benefits management is predetermined during the program formulation phase. This prevents sustainment from becoming an open-ended responsibility for program managers.
If process owners feel sustainment should remain part of the project, it usually signals a lack of structured transition rather than a real need for extended project involvement.
Final Recommendations: PMO Facilitates the Transition But Does Not Own Sustainment
To ensure sustained success, the following best practices should be implemented:
- PMO should lead the transition but not sustainment. The responsibility for continuous improvement belongs to business process owners.
- A structured handover process is critical. This includes documentation, training, and a clear transition of ownership.
- The contract defines the length of program support. The sustainment duration should align with the agreed contractual period set at the program’s formulation.
- The PMO should track impact, not operate the process. While value realization tracking can be beneficial, operational teams must manage and sustain the new processes.
- Clear roles and responsibilities must be defined. The project team enables change, but process owners ensure it lasts.
By embracing a structured, collaborative approach, program managers can ensure that the benefits they deliver do not fade away once the project is closed, and businesses can fully capitalize on the changes implemented.