Article
Rethinking the capital-project portfolio
Why major projects need portfolio-level prioritization, stronger economics and more adaptive governance as cost, demand and risk shift.
Choose a delivery model that reflects project complexity, risk and the capabilities you can actually mobilise
We align delivery structures, responsibilities, interfaces and owner roles with the specific conditions shaping capital execution.
Capital projects can pursue similar outcomes through fundamentally different delivery structures, yet model selection is often driven by precedent or procurement convention. Decisions about integration, packaging, owner involvement and responsibility allocation shape interfaces, risk exposure and the ability to respond when conditions change. A model that works for a repeatable project may be unsuitable for a complex first-of-a-kind investment. Delivery strategy therefore requires an explicit view of project characteristics, market conditions and the capabilities the owner is prepared to retain before execution responsibilities become embedded.
Focus
Which delivery model fits the project you actually have?
Complexity, maturity, interfaces and owner capability matter more than familiarity when deciding how execution should be structured.
Read nowStrategic Challenges
Delivery models redistribute complexity rather than eliminate it
Transferring responsibility externally can change where risk sits without removing the interfaces and decisions that create it.
Read nowStrategic Impacts
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.
Read nowObserved Patterns
Inherited delivery models can hard-wire the wrong assumptions
We often see familiar structures reused despite major differences in project maturity, market depth and owner capability.
Read nowStrategic Challenges
Delivery models redistribute complexity rather than eliminate it
Transferring responsibility externally can change where risk sits without removing the interfaces and decisions that create it.
Read nowStrategic Impacts
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.
Read nowObserved Patterns
Inherited delivery models can hard-wire the wrong assumptions
We often see familiar structures reused despite major differences in project maturity, market depth and owner capability.
Read nowPOV
Risk transfer is meaningless when the recipient cannot control the risk
A contract can allocate liability, but delivery strategy must determine who is actually capable of managing the underlying exposure.
Read nowOur approach
Design the delivery architecture around project realities rather than inherited conventions
Our approach begins by examining project complexity, scope maturity, interfaces, uncertainty, market conditions and the owner's internal capabilities. We identify the decisions and activities that require integration or direct owner control, then test alternative delivery architectures against these requirements. Packaging, responsibilities, risk allocation and governance interfaces are considered together rather than as separate contracting choices. We then define the preferred model, owner organisation and transition requirements, including conditions that could justify adapting the structure as project maturity or market circumstances change.
The data and estimates presented are indicative and intended for illustrative purposes. Actual outcomes may vary based on each company’s specific context, market conditions, operating model, implementation choices, and the quality and consistency of execution, including actions undertaken by the client.
Keypillars
Explore the key pillars that define this capability and shape how we create focused, measurable business impact.
Delivery architecture
Define how project responsibilities, packages and delivery parties should be structured around execution requirements.
Owner control
Determine which capabilities, decisions and integration responsibilities should remain directly with the asset owner.
Interface clarity
Make organisational, technical and commercial interfaces explicit before fragmented accountability creates execution risk.
Is your delivery model designed for this project, or inherited from the last one?
Get in touch with our Delivery model strategy team to examine how responsibilities, interfaces and control should be structured.
Get in touchStrategic Framework
Explore our Strategic Framework
Explore our strategic framework applied to page_title and discover which model we apply to help you achieve your goals and objectives.
Discover our framework01. Characterise project
Assess complexity, maturity, uncertainty, interfaces, scale and other conditions shaping execution requirements.
06. Set transition
Establish how the model should be implemented and adapted as project maturity and execution conditions evolve.
05. Design architecture
Define the preferred delivery structure, owner role, packages, responsibilities and critical interfaces.
02. Assess capabilities
Determine which technical, integration and management responsibilities the owner can credibly retain.
03. Frame models
Develop alternative delivery architectures with different responsibility, packaging and integration structures.
04. Test trade-offs
Compare models across control, interfaces, market feasibility, risk allocation, flexibility and execution requirements.
How we help
Establish who should deliver what, how the pieces connect and where the owner should retain control
We provide delivery-model architectures that translate project characteristics into explicit organisational and execution choices. The work can include delivery-model assessment, owner-role definition, work packaging, interface design, responsibility allocation, delivery option comparison and owner capability requirements. Outputs clarify how delivery parties should interact, where integration accountability sits, which responsibilities should remain with the owner and how the selected structure should evolve from project development through execution.
-
Delivery model assessment
-
Delivery architecture design
-
Owner role strategy
-
Work packaging strategy
-
Delivery model option analysis
-
Project interface strategy
-
Delivery responsibility design
-
Owner capability assessment
-
Delivery model transition planning
Explore our FAQs
Find answers to the most common questions about this service, including key features, processes, and practical considerations. Explore our FAQs for additional insights and guidance.
It defines how responsibilities, work packages, interfaces and control are distributed across the owner and delivery parties.
Early enough to shape project development, but after sufficient evidence exists on scope, complexity, risks and market conditions.
Only where project characteristics are sufficiently similar. Standardisation should not override material differences in execution.
The model must reflect which integration, technical and management responsibilities the owner can credibly retain.
Not automatically. Risk may remain where external parties cannot control the underlying causes or interfaces.
Packaging should consider interfaces, market capability, scope maturity, accountability and the owner's integration capacity.
Yes. Changes in maturity, risk, market conditions or owner capability can justify revisiting the original structure.
Delivery strategy defines the execution architecture; contracting strategy defines commercial mechanisms within that architecture.
Related services
Discover related services and capabilities designed to help organizations connect strategic priorities, address complex challenges, and unlock value across the business.
Editorial overview
Articles
Capital allocation under radical uncertainty
How companies can preserve strategic flexibility while directing capital toward the opportunities most likely to create durable value.
Read articleRethinking the capital-project portfolio
Why major projects need portfolio-level prioritization, stronger economics and more adaptive governance as cost, demand and risk shift.
Read articleFocus
How much infrastructure will the business actually need?
Demand forecasts rarely justify a single answer. Capacity strategy must account for uncertainty, timing and the cost of being wrong.
What problem does tokenization actually solve?
Digital ownership creates value only when it changes access, transferability, governance or economics in a meaningful way.
Strategic challenges
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.
Complex programs fail between organisational boundaries
Cross-project dependencies can create systemic consequences even when individual components appear to be performing adequately.