Your project is on time, on budget, scope is intact, quality is acceptable, and identified risks are controlled. Eighteen months ago the organization approved it based on assumptions about customers, competitors, costs and expected benefits. Nobody has checked whether those assumptions are still true. Is it still a healthy project? Should it continue? Who should check the assumptions?
The project can be green and still be the wrong project to continue. Schedule, budget and scope tell us how efficiently we are delivering, not whether the original business case still makes sense. I would regularly validate assumptions, expected benefits and strategic alignment with the sponsor and business owner. Sometimes stopping a healthy project is the best project decision. Saving Changes...
If the status report does not include anything about expected benefits vs. forecast benefits then it is only reporting on project delivery health and not on project outcome health. The latter is more important to your stakeholders who expect the former to be table stakes.
In the absence of a defined benefits owner from the sponsoring department or organization, the PM might need to find an appropriately skilled person (e.g. a BA) within their team to play this role over the life of the project.
Kiron
...
1 reply by Aaron Porter
Aug 15, 2026 11:27 PM
Aaron Porter
...
Kiron, you bring up a good point, and it raises another question - how frequently do you (or other project managers) see project outcome health metrics on the status report? If you consider PMI's 2025 Pulse of the Profession In-Depth Report, stating that 83% of organizations lack maturity with benefits realization, the answer might be pretty small.
In a perfect world, I would want to see:
- delivery metrics - is the project on track?
- outcome metrics - is the project going to deliver the expected benefits?
- investment metrics - is the project still worth pursuing, based on the benefits it is expected to deliver and compared to other investments in progress and being considered? (this isn't necessary for every project, like compliance projects or replacing/upgrading software that is business critical and the current version is no longer supported)
Early in my career, the organizations I worked for didn't have good mechanisms for monitoring outcome or investment metrics, or canceling projects. Fortunately, that's changing. I hope it's changing for other project managers, as well; it's just not always something a project manager can control.
Since the project’s progress, budget, scope, and risk are all showing as normal, it is moving forward in a healthy and orderly manner in line with expectations—there is simply no valid reason to cancel it at this point. To halt it prematurely would only waste all the effort and resources invested so far, which goes against sound project management logic. A project should only ever be considered for termination when serious and irreversible problems arise—such as core metrics spiraling out of control, the business case for the project disappearing entirely, insurmountable external constraints emerging, or the cost clearly outweighing any possible benefit. I recommend continuing as planned while maintaining your current oversight and regular reviews; if you have lingering concerns, you can additionally verify that the business value, stakeholder needs, and external conditions remain unchanged. Only when the fundamental business purpose itself ceases to exist should you formally begin evaluating whether to proceed. Saving Changes...
If the status report does not include anything about expected benefits vs. forecast benefits then it is only reporting on project delivery health and not on project outcome health. The latter is more important to your stakeholders who expect the former to be table stakes.
In the absence of a defined benefits owner from the sponsoring department or organization, the PM might need to find an appropriately skilled person (e.g. a BA) within their team to play this role over the life of the project.
Kiron
Kiron, you bring up a good point, and it raises another question - how frequently do you (or other project managers) see project outcome health metrics on the status report? If you consider PMI's 2025 Pulse of the Profession In-Depth Report, stating that 83% of organizations lack maturity with benefits realization, the answer might be pretty small.
In a perfect world, I would want to see:
- delivery metrics - is the project on track?
- outcome metrics - is the project going to deliver the expected benefits?
- investment metrics - is the project still worth pursuing, based on the benefits it is expected to deliver and compared to other investments in progress and being considered? (this isn't necessary for every project, like compliance projects or replacing/upgrading software that is business critical and the current version is no longer supported)
Early in my career, the organizations I worked for didn't have good mechanisms for monitoring outcome or investment metrics, or canceling projects. Fortunately, that's changing. I hope it's changing for other project managers, as well; it's just not always something a project manager can control.
...
1 reply by Kiron Bondale
Aug 16, 2026 7:30 AM
Kiron Bondale
...
Aaron -
It has been a few years since I've been directly or indirectly involved with project delivery but over twenty-five years of working with hundreds of organizations I can honestly just point to a handful where there was regular re-forecasting of expected benefits over a project's life and only one of those who would pause or terminate funding when a variance threshold was exceeded.
Beyond delivery factors, this is a key symptom of lower or higher organizational PM maturity.
Kiron
Saving Changes...
Luis BrancoCEO| Business Insight, Consultores de Gestão, LdªCarcavelos, Lisboa, Portugal
A project can be green on delivery and still no longer be justified as an investment. Those are different evaluations, and good governance needs to preserve both.
The project manager may be well placed to detect and surface evidence that important assumptions have changed, but that does not necessarily mean the PM has the authority to determine whether the investment should continue. Sensing, evaluating materiality and deciding what follows may legitimately sit with different actors.
I would therefore go beyond asking whether the original assumptions are still true. The more important questions are which assumptions remain material to the project's justification, what evidence indicates that they have changed sufficiently to warrant reassessment, and who has the authority to act on that evidence.
The appropriate response may then be to continue, adapt, pause or terminate. A green status tells us how the project is performing against its current commitments. It does not, by itself, tell us whether those commitments remain worth pursuing. Saving Changes...
Kiron, you bring up a good point, and it raises another question - how frequently do you (or other project managers) see project outcome health metrics on the status report? If you consider PMI's 2025 Pulse of the Profession In-Depth Report, stating that 83% of organizations lack maturity with benefits realization, the answer might be pretty small.
In a perfect world, I would want to see:
- delivery metrics - is the project on track?
- outcome metrics - is the project going to deliver the expected benefits?
- investment metrics - is the project still worth pursuing, based on the benefits it is expected to deliver and compared to other investments in progress and being considered? (this isn't necessary for every project, like compliance projects or replacing/upgrading software that is business critical and the current version is no longer supported)
Early in my career, the organizations I worked for didn't have good mechanisms for monitoring outcome or investment metrics, or canceling projects. Fortunately, that's changing. I hope it's changing for other project managers, as well; it's just not always something a project manager can control.
Aaron -
It has been a few years since I've been directly or indirectly involved with project delivery but over twenty-five years of working with hundreds of organizations I can honestly just point to a handful where there was regular re-forecasting of expected benefits over a project's life and only one of those who would pause or terminate funding when a variance threshold was exceeded.
Beyond delivery factors, this is a key symptom of lower or higher organizational PM maturity.
Senior IS Project Manager| Baycare Health SystemsClearwater, Fl, United States
Hi Aaron - if your project is on time, on budget, scope is intact, quality is acceptable, and identified risks are controlled, these are not reasons to cancel your project. 18 months into a project seems like a large time for the projects that I normally work with, however, these longer projects tend to be more strategic than most projects and also get the most attention from leadership. In my opinion, the vast majority of these projects would continue to completion, the only exception would be if there was some type of change to the industry or environment that makes the project obsolete or impacts the value that will be delivered. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
It is just a matter of project objective. which is created from the concept of you are creating a solution, where solution is equal to the thing to be created plus the way to create it. If the solution is not able to solve the business problem (getting the basic objectives related to survive, growth and develop) then it could be canceled. But it is an strategic decision out of the hands of project manager. Saving Changes...
A green project status does not always mean the project is still healthy or should continue. A project can be on time, on budget, within scope and have risks, but the assumptions behind the original business case may have changed.
I will share an example, a banking project was developing new services that would charge customers additional mortgage fees under certain conditions chosen by the customer. The project was planned, developed, tested, and nearly ready for production after more than 10 months of work. However, just as implementation was about to begin, the COVID-19 pandemic created a major financial crisis. The organization recognized that introducing additional fees could financially burden customers, so the project was paused and ultimately cancelled.
Although the project was green and healthy according to its original scope and plan, the external environment had changed, making the business case no longer appropriate. This demonstrates that project health is not only about schedule, budget, scope, and risk, it also depends on whether the project's assumptions and expected benefits remain valid.
Therefore, the project should not automatically be cancelled simply because assumptions have changed. The project sponsor, leadership, stakeholders and the project manager should reassess the assumptions and business case. If the project no longer provides sufficient value or creates unacceptable risks, it should be paused, changed or cancelled. The project manager should then communicate the decision clearly to the project team and stakeholders. Validating assumptions and benefits throughout the project ensures the projects are aligned with the business and customer or end user needs. Saving Changes...
Thanks for the responses. I'm interested in other people's experiences, as well, and wanted to take a moment to call out that, even though there are differences in some of the responses, they are likely contextually correct for their organization. An organization that optimizes for delivery will have a different approach than an organization that's optimizing for benefits realization. To Kiron's point, it may be a question of maturity, and it may also be due to trade-offs, intentionally made. Saving Changes...
Community Champion
