Portfolio Thinking in Infrastructure Delivery

Managing a £38M portfolio across multiple concurrent sites requires portfolio-level thinking that most project managers don't develop. Project management is a skill of managing a defined scope to a defined schedule and budget. Portfolio management is a different skill. It's about managing multiple interdependent projects simultaneously, making resource allocation decisions that affect all of them, and maintaining strategic alignment between individual project outcomes and overall programme objectives.

Portfolio vs. Project Level Perspective

The fundamental difference between portfolio thinking and project thinking is the unit of analysis. Project thinking treats each project as the primary unit. Success means this project delivers on time and on budget. Portfolio thinking treats the portfolio as the primary unit. Success means the portfolio delivers its strategic objectives, which may require accepting individual project compromises in service of portfolio-level outcomes.

On Old Street and Farringdon, a project-level perspective would have treated each site as an independent delivery commitment. Portfolio-level thinking treated them as a connected programme serving TfL's connectivity agenda. The resource allocation decisions, the contractor team deployment, the governance structure, and the client communication approach were all shaped by the portfolio-level objective, not the individual site objectives. That perspective is what produced zero cascades between sites.

Resource Allocation Across Projects

Portfolio-level resource allocation requires explicit decisions about which projects get which resources when capacity is constrained. On concurrent delivery programmes, the same contractor teams, the same design resources, and the same governance time can't be in multiple places simultaneously. Allocation decisions have to be made based on programme priority, schedule criticality, and risk exposure.

The allocation methodology I use on concurrent programmes starts with critical path analysis across all projects simultaneously. Resources are allocated first to critical path activities on the highest-priority project. Near-critical path activities on other projects get the next allocation. Float activities get whatever remains. This methodology prevents the intuitive but incorrect approach of treating all projects as equally urgent, which produces a diffusion of effort that leaves critical path activities under-resourced.

Risk Cascading Across Sites

Portfolio-level risk management requires understanding how risks at individual sites can cascade across the programme. The Gas Networks critical path risk on Old Street and Farringdon was a portfolio-level risk because a delay at either site would cascade to TfL's programme. Individual site risks that had no programme-level implications were managed at the site level without portfolio governance involvement.

Identifying which site-level risks have portfolio-level cascade potential is the most important risk management task in concurrent programme delivery. It requires programme-level understanding of how individual project outcomes affect the strategic programme. That understanding is only available to a portfolio-level thinker. A project manager managing Old Street in isolation would not identify the TfL connectivity cascade risk without understanding the Farringdon programme and TfL's interdependency.

Organisational Learning Across Projects

One of the most significant benefits of portfolio-level management is the ability to transfer learning from one project to another in real time. The utility coordination protocol developed for Newington Green was adapted and applied to the Old Street and Farringdon concurrent delivery. The risk register methodology that separated site-level from programme-level risks was developed on one programme and became the standard for all subsequent programmes.

Portfolio-level thinking creates the organisational context for this learning transfer. Individual project managers managing their projects in isolation don't have the visibility or the incentive to transfer learning across project boundaries. Portfolio management creates both the visibility and the incentive. The portfolio manager sees what's working and what isn't across all projects, and has the authority to standardise effective approaches across the portfolio. That's the infrastructure delivery equivalent of the customer success manager who develops best practices from high-performing accounts and applies them across the customer base.