Rethinking the capital-project portfolio
Why major projects need portfolio-level prioritization, stronger economics and more adaptive governance as cost, demand and risk shift.
Read articleRelated macro
Capital strategy
Align capital allocation, funding and investment priorities with strategy, risk, returns and long-term objectives.
Discover the macroEditorial overview
Articles
Infrastructure strategy becomes enterprise strategy
How infrastructure capacity, asset lifecycle choices and delivery ecosystems increasingly shape growth, resilience and competitive advantage.
Read articleFocus
Who is allowed to say no?
Capital governance is weak when everyone can advocate for investment but responsibility for rejecting or reducing a proposal remains unclear.
Can your contractor market actually deliver the capital plan?
Investment ambition means little when critical engineering, construction or specialist capacity is unavailable at the required scale.
Strategic challenges
Infrastructure decisions outlive the assumptions that created them
Long asset lives force companies to make capacity choices while demand, technology and operating requirements remain uncertain.
Capital projects become harder to govern precisely when uncertainty rises
Complex delivery environments expose weak decision rights, inconsistent escalation and governance forums overloaded with reporting.
POV
Saving the project is not always the same as saving the investment
Turnaround should protect remaining economic and strategic value, not defend sunk cost, reputations or the original project plan.
The lowest bid is irrelevant if the ecosystem cannot absorb your pipeline
Capital strategy that ignores contractor capacity mistakes procurement competition for genuine delivery-market depth.
Strategic impact
Portfolio balance protects future choices
Combining investments with different horizons and uncertainty profiles can prevent today's commitments from eliminating tomorrow's strategic options.
Program governance makes cross-project trade-offs visible
Integrated decisions reveal where local optimisation would otherwise undermine milestones, interfaces or the overall program outcome.
What we observe
Project pipelines can hide the absence of an infrastructure strategy
We often see individual investments proposed without a common view of future capacity, system dependencies or development logic.
Large projects develop their own momentum
We frequently see the original strategic rationale receive less scrutiny as engineering progress, committed spend and organisational sponsorship increase.