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
What problem does tokenization actually solve?
Digital ownership creates value only when it changes access, transferability, governance or economics in a meaningful way.
When does a group of projects become a major program?
The distinction emerges when outcomes, interfaces and decisions become too interdependent for projects to succeed independently.
Strategic challenges
Infrastructure turns forecasts into commitments
A demand assumption that proves wrong in a spreadsheet can be changed quickly; the same assumption embedded in physical capacity can persist for decades.
Scarce delivery capacity is becoming a strategic capital constraint
Competing infrastructure programmes can create bottlenecks in contractors, equipment, specialist skills and engineering resources.
POV
Maximum borrowing capacity is not investment capacity
A business can technically finance more capital than it can strategically afford once resilience, optionality and future obligations are considered.
A business case should be allowed to fail after approval
Capital discipline requires the organisation to revisit original assumptions and withdraw support when new evidence weakens the investment logic.
Strategic impact
The right delivery architecture makes accountability easier to locate
Clear roles and interfaces reduce ambiguity over who integrates work, manages dependencies and resolves consequential decisions.
Earlier performance signals widen the window for intervention
Understanding trajectory before variance compounds gives decision-makers more time to examine causes and available responses.
What we observe
Adding another governance layer does not create integration
We often see program structures aggregate project reporting while leaving cross-project decisions and dependencies unresolved.
Recovery plans often preserve the assumptions that caused the failure
We frequently see new schedules and budgets imposed without resolving scope instability, weak governance or unrealistic forecasts.