The strategic value of project management begins before a project is approved: it begins with deciding which changes the organisation should fund at all.
An organisation can become very good at delivering the wrong projects. Schedules improve, governance becomes more sophisticated, dashboards become more precise—and enterprise performance still disappoints because scarce capital, specialist people and executive attention are spread across initiatives that do not collectively move the strategy forward.
The supplied material contains a simple but powerful system view. Permanent organisations use resources and assets through operations to create products, services, benefits and performance. When leaders decide that something must change, temporary organisations—projects and programs—are created to make that change. Portfolio management sits above them to help determine which proposed changes should proceed.
That framing moves portfolio management away from administrative project reporting. It becomes a mechanism for enterprise choice.
The Strategic Context
Projects are temporary. Strategy and operations are not.
This distinction matters because a project is usually designed around a defined change: a new asset, system, product, process, facility, policy or capability. The permanent organisation must absorb that change, operate it and convert it into benefits. A completed project therefore sits inside a much longer value chain.
The source material adapted from Silvius and colleagues depicts this relationship explicitly: strategic management sets and evaluates goals; permanent operations use assets and resources to create performance; project management delivers outputs that change the permanent organisation; and portfolio management helps select the “right” changes.
The leadership implication is that a project business case cannot be judged only as a stand-alone proposition. Every approval consumes part of a finite enterprise system: money, people, risk capacity, change capacity, management attention and often the ability to absorb yet another operating-model change.
That is why a portfolio can contain many individually sensible projects and still be strategically weak.
What Leaders Commonly Misread
The first misread is equating demand with priority. A business unit may have a valid need. That does not automatically make its project the best use of enterprise resources. Portfolio leadership requires comparing value across competing needs, not merely validating each request in isolation.
The second is treating approved projects as permanent commitments. Approval should authorise investment under stated assumptions, not create immunity from later challenge. If strategy changes, benefits weaken, dependencies fail or capacity becomes constrained, the portfolio should be able to pause, redesign or stop work.
The third is optimising project utilisation instead of enterprise throughput. Loading every specialist to 100 per cent can appear efficient while increasing queues, handovers and delay across the portfolio. Organisational capacity is not just a headcount total; it includes bottleneck skills, decision bandwidth, procurement capacity, systems integration capacity and the ability of operations to absorb change.
The fourth is assuming delivery output equals realised value. A project can install a new system, complete a facility or release a product and still fail to generate the expected benefit because adoption, operating readiness, market response or post-project ownership is weak.
Related article: A Project Can Finish While the Change Still Fails
Reframing the Issue
Portfolio management should be understood as the governance of competing claims on the future of the organisation.
Every meaningful initiative says, implicitly: “Use capital and capacity here rather than elsewhere because this change will produce greater strategic value.” That is an investment claim, not just a delivery request.
The correct unit of analysis is therefore not the project alone but the combination of:
- strategic contribution;
- expected benefits;
- risk and uncertainty;
- resource demand;
- dependencies;
- timing;
- reversibility;
- organisational change load; and
- opportunity cost.
Opportunity cost is particularly important because it often remains invisible in project governance. A project may have a positive business case and still be inferior to another investment that uses the same scarce engineering team, digital platform, capital budget or executive sponsor.
Strategic Analysis: From Project Approval to Portfolio Design
A strong portfolio is designed, not accumulated.
At the strategic level, leadership must first translate broad ambitions into investment themes. A manufacturer may need to protect margin, improve safety, digitise planning and enter a new market. Those themes then compete for capital and organisational capacity.
At portfolio level, initiatives should be tested for both individual merit and collective coherence. A digital transformation, for example, may depend on data governance, process standardisation and workforce capability. Funding the front-end technology without the enabling projects may create a portfolio that looks active but is structurally incapable of delivering the intended outcome.
Program thinking becomes important where several projects must combine to create one benefit. The projects may each deliver successfully while the program fails because the interfaces between them were not governed. Portfolio leadership must therefore see dependencies that individual project managers cannot resolve alone.
There is also a sequencing problem. Organisations can overload themselves with simultaneous change. Even when financial capital is available, the permanent organisation may not be able to absorb multiple process changes, systems releases, relocations and restructures at once. Change saturation is a portfolio constraint.
A hypothetical engineering firm illustrates the point. Suppose it approves a new ERP system, automated production line, warehouse relocation and product-platform redesign in the same year. Each business case is credible. Yet all four require the same process engineers, master-data experts, production supervisors and executive decision makers. The portfolio is not four independent investments. It is one constrained system competing for the same bottleneck capacity.
Decision Framework
A practical portfolio test is the VALUE–CAPACITY matrix.
| Dimension | Core question | Evidence leaders should expect |
|---|---|---|
| Strategic value | Which strategic objective will this materially advance? | Clear link to an enterprise outcome, not a generic alignment statement. |
| Benefits | What measurable improvement should occur after delivery? | Benefit owner, baseline, target and timing. |
| Dependency | What else must succeed first or at the same time? | Dependency map and interface ownership. |
| Capacity | Which scarce resources will this consume? | Named bottleneck skills, funding, leadership and operational absorption needs. |
| Risk | What could destroy or materially reduce value? | Key assumptions, uncertainty and exposure. |
| Reversibility | How difficult is it to stop or change direction later? | Exit points and sunk-cost profile. |
| Timing | Why now? | Window of opportunity, regulatory date, market logic or sequencing need. |
| Opportunity cost | What will we defer or stop by funding this? | Explicit displacement decision. |
The final question is deliberately uncomfortable. If the sponsor cannot say what should receive less attention because this project is important, the organisation may be pretending capacity is unlimited.
Portfolio governance should also distinguish three types of decision:
Fund when strategic value is strong, capacity is available and critical assumptions are credible.
Stage when value may be high but uncertainty or irreversibility warrants an evidence-building tranche.
Stop or defer when benefits no longer justify capacity, strategic alignment has weakened, or dependencies cannot be secured in time.
Stopping work is not portfolio failure. Continuing low-value work because nobody wants to reverse an earlier decision is.
From Strategy to Execution
Immediate action is to make the portfolio visible as one system. Create a single view of active and proposed investments, their strategic objectives, major benefits, critical dependencies and bottleneck resources. The purpose is not another reporting layer; it is to expose conflicts that are invisible inside separate project plans.
Medium-term capability building should formalise benefit ownership and portfolio decision rights. Sponsors should remain accountable for the value case, while operational leaders own benefits that occur after project handover. Portfolio governance should have authority to challenge sequencing, reallocate funding and stop initiatives when conditions change.
Long-term positioning requires linking strategy cycles, capital allocation and delivery governance. When these operate as separate processes, projects can continue long after the strategy that justified them has moved on. A mature system continuously connects enterprise direction to investment choices and then back to realised performance.
Related article: Why the Iron Triangle Is Too Small for Strategic Project Success
Signals to Monitor
Warning signs include a rising number of projects without a corresponding increase in realised benefits; repeated competition for the same specialist resources; executive committees spending most of their time on project status rather than portfolio choices; projects remaining active after their business assumptions have changed; operational teams receiving more changes than they can absorb; and strategic objectives with little funded delivery behind them.
Another signal is the absence of termination. In a large portfolio operating under uncertainty, a record in which every approved initiative survives to completion may indicate weak challenge rather than exceptional foresight.
Questions for the Leadership Team
- Which current initiatives make the largest measurable contribution to strategy?
- Which projects compete for the same bottleneck people, systems, suppliers or executive attention?
- What are we choosing not to fund because of our current portfolio?
- Which active projects would we not approve today if they were presented as new proposals?
- Who owns each benefit after project delivery ends?
- Where have we funded outputs without funding the enabling changes required to realise value?
Sources and Notes
This article develops an original ERANORTH synthesis from MPM416 material on projects as temporary organisations, the relationship between permanent operations and project delivery, and portfolio management as selection of the “right” organisational changes. The supplied study notes attribute the underlying temporary/permanent organisation model to Silvius, Schipper, Planko and Planko, Sustainability in Project Management (Routledge, 2012).
Closing Perspective
Projects are instruments of change. Portfolios are instruments of choice. Enterprise value improves when leaders stop asking only whether projects can be delivered and start asking whether the organisation is investing its finite capacity in the changes that matter most.