Delivery discipline answers whether a commitment was executed well; strategy asks whether it was worth making.
Executives are rightly concerned when a project misses its budget or schedule. Those failures are visible, measurable and difficult to ignore. A more dangerous failure can look successful.
The project finishes. The required output is accepted. The team closes the schedule. The budget is largely intact. Yet the organisation gains little strategic advantage because the work was weakly aligned, duplicated another initiative, consumed scarce capability at the wrong time or solved a problem that no longer mattered.
The supplied EY portfolio-management paper describes precisely this risk. Organisations can improve project-management capability and still experience value leakage because they lack a mature portfolio process capable of aligning programs and projects with strategy. The problem is not that delivery discipline is unimportant. It is that delivery discipline cannot compensate for a poor investment choice.
The Strategic Context
Most management systems produce better visibility of execution than of strategic causality.
Schedule variance can be calculated. Capital spend can be reported. Milestones can be counted. Strategic contribution is harder. It depends on assumptions about customers, operating conditions, organisational capability, adoption, competing investments and the continuing relevance of the strategic objective.
This creates a bias towards what is easiest to govern.
A project that is two months late may receive intense executive attention. A project that is perfectly on time but no longer supports the highest-priority strategy may proceed quietly because nothing in the project dashboard looks wrong.
Portfolio management exists partly to correct that bias. The supplied sources distinguish "doing things right" from "doing the right things". Project management primarily governs execution of an authorised undertaking. Portfolio management challenges which undertakings should be authorised, continued, accelerated or stopped.
What Leaders Commonly Misread
The most common mistake is assuming that project approval proves strategic value.
Approval proves only that the project passed whatever decision process existed at that time. Strategy may change. New evidence may appear. Costs may rise. Benefits may weaken. A competing initiative may offer greater value. Capacity constraints may become more severe.
The second mistake is treating sunk cost as strategic evidence. Money already spent explains the history of an initiative. It does not justify future spending.
The third is using delivery performance as a proxy for benefit. A project can produce a technically correct system that users do not adopt. A facility can be constructed to specification while the operating model required to use it remains unresolved. A new process can be implemented without producing the expected productivity improvement.
The fourth is treating strategic alignment as a label. Almost any initiative can be described as supporting "growth", "efficiency", "customer experience" or "risk reduction". Genuine alignment requires a more demanding chain of logic.
Reframing the Issue
A project should not be evaluated only by the question:
Did we deliver what we said we would deliver?
Leaders also need to ask:
Did the output create the capability required?
Did the capability change the target environment?
Did that change produce the expected benefit?
Does that benefit still matter to the strategy?
The supplied study material, drawing on Williams and Parr, separates outputs, outcomes and benefits for this reason. Outputs are specific and verifiable. Outcomes are changes in the target environment. Benefits are the value realised from those changes.
That chain creates a more rigorous view of strategic execution.
Related article: From Outputs to Enterprise Value: The Strategy-to-Delivery Chain
The Four Ways a Successful Project Can Destroy Value
It can deliver the wrong priority
An initiative may be technically sound but strategically marginal. Funding it still imposes opportunity cost because capital and specialist people cannot be used elsewhere.
This is particularly important when the organisation has more approved work than delivery capacity. In that environment, every low-priority project slows something more important.
It can deliver an output without an outcome
A completed system, plant, product or policy is an output. If processes, behaviours or operating conditions do not change, the intended outcome may never occur.
This is where program and change-management disciplines become essential. The output has to be integrated into the wider system.
It can optimise one area while weakening another
Projects are often sponsored inside functions. Their business cases may therefore emphasise local benefits while underestimating enterprise consequences.
A cost-reduction project in one function could shift workload into another. A digital initiative may improve customer access while creating new service demand the operation cannot absorb. A procurement saving may create supply concentration or lifecycle risk.
The project can meet its local objective while reducing total enterprise value.
It can remain "successful" after the environment changes
A baseline reflects assumptions at a point in time. Portfolio governance must decide whether those assumptions remain valid.
The supplied EY material explicitly includes agility in its portfolio-management objectives: organisations need mechanisms to realign the portfolio when strategic objectives change. That is not permission for undisciplined change. It is recognition that strategic discipline sometimes requires changing the commitment.
Decision Framework
Leaders can apply a five-question continuing justification test at major review points.
1. Strategic relevance: Which current strategic objective does this initiative materially support?
2. Causal logic: What output is expected to create which outcome, and how does that outcome produce value?
3. Relative value: Is this still a better use of scarce resources than competing initiatives?
4. Feasibility: Does the organisation still have the capacity, dependencies and adoption conditions required for success?
5. Reversibility: What is the cost of stopping, delaying, redesigning or continuing?
A project that performs well against its delivery baseline can still fail this test.
The purpose is not to destabilise every project. It is to distinguish legitimate delivery confidence from automatic continuation.
From Strategy to Execution
Immediately, add one portfolio-level question to major project reviews: "What has changed in the investment case since the last decision?" This moves governance beyond variance reporting.
In the medium term, link project outputs to program outcomes and named benefit owners. Where no program exists, the sponsor still needs to identify who owns the operational outcome after handover.
Longer term, portfolio reviews should compare initiatives against each other rather than review each project only against its own approved business case. That exposes opportunity cost.
Leaders should also be explicit about stop criteria. A project should not need to become a disaster before it can be terminated. Strategic misalignment, weakened benefits or unacceptable capacity pressure can be sufficient reasons.
Related article: Portfolio Prioritisation Is Not Ranking: Decide What to Accelerate, Defer and Stop
Signals to Monitor
Watch for a portfolio with high rates of project completion but weak benefit realisation; repeated claims that projects are "strategic" without clear causal links; initiatives whose business cases are not revisited after approval; benefits with no operational owner; and projects protected from challenge because of money already spent.
Another warning signal is a widening gap between executive strategy discussions and portfolio review discussions. If the strategy changes but the project list does not, the portfolio is functioning as a record of historic commitments rather than a vehicle for current strategy.
Questions for the Leadership Team
- Which current projects would we approve again today if they had not yet started?
- Where are we measuring completion rather than strategic effect?
- Which benefits depend on operating changes outside the project team's authority?
- What initiatives remain funded mainly because of sunk cost or political sponsorship?
- Where could a "green" project be consuming capacity needed by a more valuable initiative?
- How often do strategic changes result in actual portfolio rebalancing?
Closing Perspective
The hardest portfolio decisions rarely concern obviously failing projects. Obviously failing projects eventually demand attention.
The more difficult decisions concern projects that are being delivered competently but no longer deserve the same priority.
Execution excellence matters. But when the underlying investment is wrong, excellence can simply make the organisation arrive at the wrong destination faster.
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.