A project is not truly successful because it finished well; it is successful when the organisation can live with what it created.
A project can be delivered on time, within budget and to its approved specification—and still be a poor investment.
That is uncomfortable because much of project governance is built around delivery performance. Boards see schedule variance, cost variance, milestone status, defects, risks and change requests. Project teams are rewarded for getting to handover. Closure confirms completion, releases resources and transfers responsibility.
Yet the asset, system, facility, policy or capability created by the project may operate for years or decades. Its environmental footprint, operating cost, resource dependence, maintenance burden, stakeholder consequences and exposure to future conditions can outlive the temporary organisation that produced it.
The strategic question is therefore not simply whether the project finished successfully. It is whether the consequences of the project remain successful after the project finishes.
The Strategic Context
The supplied project-management material makes a useful distinction between project-management success and project success. Traditional delivery measures emphasise time, cost and quality. Broader project success considers whether the intended objectives and stakeholder expectations were actually achieved.
The same material goes one step further: projects can satisfy conventional delivery measures and still fail against wider economic, social or environmental objectives. That observation matters because projects are not isolated production systems. They are mechanisms through which organisations convert strategy and capital into operating reality.
Once a project is approved, a series of design choices becomes progressively harder to reverse. A site is selected. Technology is specified. Suppliers are contracted. Materials are purchased. Interfaces are fixed. Operating assumptions are embedded. When the project closes, many of those choices become the starting conditions for operations.
This is why closure is a weak boundary for judging value. Closure tells leaders that a temporary endeavour has ended. It does not tell them whether the investment has become valuable, resilient or responsible.
In a 2017 interview supplied with the source material, sustainability practitioner Joel Carboni challenged the narrow tendency to think from initiation to close and argued for a broader, lifecycle-oriented mindset. The underlying point is stronger than any one project-management methodology: the organisational consequences of a project do not respect the administrative boundary of the project.
What Leaders Commonly Misread
The first misreading is to assume that good delivery automatically produces good outcomes.
A capable project team can deliver the wrong solution very efficiently. It can also deliver the right solution against assumptions that later prove weak. Neither situation is corrected by excellent schedule control.
The second misreading is to treat post-handover consequences as someone else's problem. Operational ownership may legitimately transfer, but strategic accountability cannot disappear simply because the project office closes. If an investment creates avoidable operating cost, environmental liability, regulatory exposure or stakeholder opposition, the enterprise still owns the consequence.
The third misreading is that sustainability is an additional objective competing with delivery. This framing encourages teams to treat environmental and social considerations as optional enhancements. In reality, these factors often influence core investment quality: energy demand affects operating cost; water dependence affects resilience; waste streams affect compliance and disposal cost; material choices affect maintainability and end-of-life options; community impacts affect approvals and reputation.
The fourth misreading is that long-term consequences can be evaluated later. By then, the decisions with the largest leverage may already be locked in.
Reframing the Issue
Leaders should separate three different questions:
- Was the project managed well?
- Did the project produce the intended outcome?
- Does the outcome continue to create acceptable value over its useful life?
These are related, but they are not interchangeable.
The first is predominantly a delivery question. The second is a benefits question. The third is an enterprise-value question.
This distinction changes governance. Instead of treating time, cost and scope as the complete definition of success, they become one layer of a wider performance model. Delivery discipline remains essential, but the investment must also be judged against the operating system it creates.
The practical implication is that the business case should not end at handover. It should define what must remain true after handover for the investment to deserve continued confidence.
Strategic Analysis: The Hidden Life of a Project Decision
Consider a hypothetical manufacturing expansion. The project team is asked to add capacity quickly. It selects lower-cost equipment that meets output specifications and enables delivery within budget.
From a project perspective, the decision may be rational. From an enterprise perspective, the equipment may require more energy, specialised consumables, scarce spare parts and a narrow supplier base. It may also perform poorly under future heat conditions or create a difficult waste stream.
None of those consequences necessarily appear as project overruns. They appear later as operating expenditure, downtime, supply risk, compliance work or replacement capital.
The same principle applies in infrastructure. A transport, water or public facility can be completed successfully while creating a future maintenance burden or exposing users to environmental conditions not adequately considered at design stage.
In technology, the equivalent problem is architectural debt. A digital platform can launch successfully while embedding vendor dependence, weak data portability or operating complexity. The domain changes; the governance problem does not.
The project converts assumptions into assets. If the assumptions are narrow, the asset inherits the narrowness.
Lifecycle cost is not just a finance calculation
Whole-of-life thinking should include more than discounted maintenance expenditure. Leaders should ask what the solution requires from the organisation over time.
Does it increase dependence on scarce skills? Does it create a single-source supply exposure? Does it constrain future options? Does it require environmental controls or monitoring? Does it make future adaptation more expensive? Does it create liabilities at decommissioning?
These are not peripheral questions. They are part of the economic architecture of the investment.
Benefits need an owner after the project team leaves
A project manager can coordinate delivery, but the benefits usually materialise in operations. That means the operating owner must inherit more than an asset. They must inherit clear performance expectations, assumptions, residual risks and measures.
If nobody owns those conditions after closure, the organisation loses the ability to tell whether value is being realised or eroded.
Portfolio governance must compare consequences, not only business cases
At portfolio level, the issue becomes even more important. Two projects may have similar headline returns but very different lifecycle exposures.
One may create flexible capacity with modest environmental and operating burden. Another may create higher short-term return but lock the organisation into fragile infrastructure, high resource consumption or costly future adaptation.
Selecting between them is not a project-management decision. It is a capital-allocation decision.
Decision Framework
ERANORTH proposes a Lifecycle Consequence Test for significant investments. Before approval—and again before major irreversible commitments—leaders should test six dimensions.
| Dimension | Executive question |
|---|---|
| Strategic value | Does the outcome still support the strategy if external conditions change? |
| Operating economics | What costs, dependencies and resource demands continue after handover? |
| Resilience | How does the solution perform under disruption, climate stress or supply constraint? |
| Stakeholder consequence | Who carries benefits, costs or unintended effects after delivery? |
| Reversibility | Which decisions become expensive or impossible to undo? |
| End-of-life liability | What obligations remain when the asset or solution is retired? |
The test is not designed to eliminate risk. Its purpose is to expose where project success depends on assumptions that the enterprise has not consciously accepted.
For high-value or long-life assets, leaders should also identify success conditions rather than only success metrics. A success condition is a statement that must remain true for the investment case to hold—for example, access to a critical input, acceptable energy cost, regulatory permission, community tolerance, workforce capability or infrastructure reliability.
When a condition weakens, the strategy should be reviewed before performance deteriorates visibly.
From Strategy to Execution
Immediate action: broaden approval papers and project charters so that they identify lifecycle consequences, not only delivery constraints. Require major assumptions to be explicit. Assign an operating owner early enough to influence design.
Medium-term capability: integrate benefits realisation, lifecycle costing, environmental risk, operational readiness and resilience into governance gates. Procurement teams should evaluate supplier and lifecycle implications rather than price alone. Risk registers should include post-handover exposures where they are created by project decisions.
Long-term positioning: build portfolio reporting that compares investments on value, resilience and strategic flexibility. Over time, this enables the organisation to favour initiatives that create durable capability rather than merely successful handovers.
This does not mean project teams become indefinitely accountable for operations. Responsibilities should transfer. What must not transfer into ambiguity is ownership of the investment logic.
Related article: Environmentalism Is Not Sustainability: The Executive Decision Behind Sustainable Projects
Related article: Build Environmental Risk Into the Project Life Cycle
Signals to Monitor
Warning signs that project success is being defined too narrowly include:
- benefits reporting ending at project closure;
- operating owners joining after major design decisions are fixed;
- business cases containing detailed capital costs but weak lifecycle assumptions;
- environmental or resilience issues being treated as late compliance checks;
- recurring post-handover remediation that was predictable during design;
- procurement decisions dominated by acquisition price despite long operating lives;
- portfolios reporting delivery confidence without reporting whether completed investments are creating intended value.
The strongest signal is organisational surprise: when operations repeatedly discover costs, constraints or liabilities that the project technically delivered exactly as approved.
Questions for the Leadership Team
- Which of our current projects could finish on time and on budget yet still leave the organisation worse off?
- What assumptions must remain true after handover for our largest investments to create value?
- Who owns those assumptions once the project team is disbanded?
- Which project decisions are difficult to reverse and therefore deserve executive scrutiny earlier?
- Do our portfolio decisions compare lifecycle resilience and operating burden, or mainly capital cost and schedule?
- What consequences are currently falling outside the formal definition of project success?
Closing Perspective
Project closure is necessary. Strategic closure is different.
A disciplined organisation should be able to end a project without ending its attention to the consequences the project created. Time, cost and scope remain essential measures of delivery competence, but they cannot carry the full burden of investment judgement.
The leadership responsibility is to ensure that success survives the handover. Otherwise the organisation may celebrate the delivery of an asset while quietly inheriting the cost of the decisions that produced it.