Separate Health from Value

What’s Actually Happening

The project is green.

Schedule is on track. Budget is within variance. Risks are identified and mitigated. Milestones are hitting. The status report is clean. The project manager presents confidently. The governance forum nods and moves to the next agenda item.

Six months after the project closes, nobody can point to what changed in the business because of it. The system went live. The team handed off support. The project manager moved on. The sponsor has a new set of priorities. The outcome that was defined in the CBA — the one with a named owner and a measurement date — was never confirmed because nobody followed up and nobody asked.

The project was not a failure. It was green from start to finish. It delivered what it was scoped to deliver. It met its timeline and budget. It just never produced the return the organization said it was investing for.

This is not a delivery problem. It is a governance problem. And it is the most common expensive problem in portfolio management, because it wears the clothing of success right up until the moment someone tries to find the benefit.

Why This Step Exists

Because a project can be healthy and still be wrong.

Project health — schedule, budget, scope, risks, issues — tells you whether the team is executing the work as planned. Project value tells you whether the work is still aimed at the right outcome. These are not the same question and they do not have the same answer.

Health is a delivery metric. Value is an investment metric. Both need to be monitored throughout the life of a project. Most governance models monitor only health. Value is deferred to a post-implementation review that, in most organizations, either does not happen or happens long after anyone can do anything about the findings.

There is a specific failure that emerges when value is not monitored in flight. The assumptions that justified the investment change during delivery. The market shifts. The operational context changes. The problem the project was designed to solve gets partially addressed by something else while the project is still running. The sponsor who championed the investment moves to a different role and the incoming sponsor is not as committed to the original outcome. Any of these changes can make the original value hypothesis less valid during delivery — but if nobody is asking the value question, the project continues on its original trajectory because the health metrics say it should.

What Good Looks Like

Every project in the active portfolio has two conversations in the governance cycle. Not one.

The first conversation is about health. Is the project executing as planned? Are there schedule, budget, or scope issues that need resolution or escalation? Are the risks being managed? Are dependencies being met? This conversation is about delivery. The project manager leads it.

The second conversation is about value. Is the original investment hypothesis still valid? Has anything changed in the business environment, the operational context, or the assumptions underlying the CBA that affects whether this project is still worth what the organization is committing to it? Has adoption planning kept pace with delivery? Is the outcome owner still engaged? This conversation is about investment. The sponsor leads it.

These two conversations can happen in the same meeting. They should not happen in the same breath. The governance forum needs to be clear about which question it is answering at any moment, because the actions that follow a health concern are different from the actions that follow a value concern.

A project that is green on health but showing value concerns needs a different response than a project that is red on health. Mixing these conversations produces confusion about what the governance forum is actually governing.

How to Do It

Define the health and value signals that matter before the first status cycle begins.

Health signals for most projects include: schedule variance against baseline, budget actuals versus forecast, scope changes since authorization, open risks above a defined threshold, open issues without resolution owners, and dependency status for critical path items. These are the signals that indicate whether execution is on track.

Value signals are different and require more active management. They include: the status of the key assumptions from the CBA (still valid, revised, invalidated), the readiness of the operational environment to absorb the change the project is delivering, the engagement level of the outcome owner, the current forecast for benefits realization against the original projection, and any external factors that have changed the value of the outcome since the project was authorized.

In practice, the value conversation is the one that gets skipped. It requires honesty about whether the original investment rationale is holding up, which can be uncomfortable when significant resources have already been committed. The governance forum needs to protect this conversation from two pressures: the pressure to only talk about health when health is green, and the pressure to avoid bad news about value because of sunk cost reasoning.

Sunk cost reasoning is the belief that because resources have been spent, the project should continue. It is one of the most reliable ways to compound a bad investment. The governance forum’s job is to evaluate the future return on continued investment, not to justify the past spend. Those are different calculations and they should be treated as such.

When material changes in delivery conditions occur — scope expands significantly, a key assumption in the original CBA no longer holds, a dependency fails and the project timeline shifts by more than a quarter — the investment case should be updated, not just noted in the risk register. The CBA is not a one-time approval document. It is the running statement of what the organization believes this investment will return. When that belief changes materially, the document should reflect the change.

Two roles carry specific accountability in this step. The Product Owner is responsible for the value conversation on product investments — they track whether the features being delivered are validating the product hypothesis and whether adoption is trending in the right direction. The Business Analyst, if still engaged post-authorization, is often the best person to maintain the assumptions log and flag when the problem definition the project was built on no longer matches the operational reality. The Product Manager should be named in the governance cycle when a product investment is under active review — they hold the roadmap context that determines whether continued investment in this direction still makes strategic sense.

What Breaks When You Skip It

The governance model optimizes for green status rather than for investment return.

Project managers learn that green reports produce smooth governance conversations, so they report green when the reality is more complicated. Sponsors disengage from value questions because the governance forum is not asking them. The portfolio accumulates projects that are technically on track and practically not delivering value — and the organization has no way to distinguish between them because it is only measuring health.

The deeper damage is cultural. When the governance model rewards green status regardless of value trajectory, it teaches the organization that the appearance of good execution is what matters. Teams optimize for the metrics being measured. The metrics being measured are health metrics. Value metrics are not being measured. The organization becomes very good at executing projects that do not change anything.

The Gotchas

Where the Disciplines Show Up

The Artifacts