Can You See the Golden Thread? Why Infrastructure Productivity Depends on the Value Chain
Picture an infrastructure programme in which every decision, from the initial investment case to the final maintenance intervention, is made at the right time by competent people holding the right information. There is no rework, and nobody reopens the budget in year three. That is what a functioning value chain looks like, and it sits closer than most organisations realise.
Most programmes operate differently, more like a relay in which every runner has a different finish line. Investors, designers, constructors and operators each optimise their own leg, and the thread that should connect them, the Golden Thread of productivity, breaks at every handover. So can you see yours? If you cannot trace a decision from the asset owner's required outcome to the work on site, you are almost certainly paying for that gap.
Discover: see the system, not the sequence
Investment, development, design, construction and operation form a single interdependent system rather than five separate stages. That system performs only when the people within it demonstrate the right behaviours, apply the right processes, and bring the right skills and experience. The result is consistent decision velocity: timely decisions, made by competent companies and individuals, that deliver the planned productivity. That is the value chain.
Notice where the weight sits. A process map cannot make a decision; a person must. Whether that person decides quickly and well depends on psychological safety, clear accountability and trust in the underlying data, so every delayed decision carries a cost and every reversed decision carries a larger one.
Diagnose: where the thread breaks
Three sources help us identify the root causes.
• PAS 4010 (9/11/26) provides the sector with a shared framework for managing productivity in infrastructure.
• The HM Treasury Green Book supplementary guidance on optimism bias sets upper-bound uplifts of 44% on capital expenditure for standard civil engineering and 66% for non-standard work.
• The Stewart report on HS2 deserves a place on your reading list, and I would suggest reading it with one question in mind: where did the thread break?
My reading of the Green Book figures is straightforward. The less standard the work, the more the system depends on behaviour rather than precedent, because the unknowns multiply and the cost of misaligned decisions multiplies with them. That is my interpretation rather than the guidance itself, so test it against your own programme.
Procurement and contracting sit at the centre of the problem. The way you package work, select a procurement route and contract form, and conduct tendering and selection determines whether productivity is rewarded or quietly penalised.
Design: build productivity in from day one
Embed productivity considerations before the first work package reaches the market. That means shaping how work is packaged, how the market is engaged, and how value chain members are appointed and commercially aligned.
Apply asset owner and client requirements in proportion to the scale, complexity and risk of the programme. Where a funder or sponsor exercises material control over procurement, packaging or delivery strategy decisions, treat that organisation as part of the chain, because it is one. Then engage every value chain member at the earliest practicable stage, so that each contributes expertise to a credible budget and schedule and remains actively involved throughout delivery. Specialists can then concentrate on the constraints they are best placed to remove, and the value improves for everyone.
Deliver: turn behaviour into return
This is where behaviour meets return on investment. Early engagement from competent specialists produces a budget and schedule that people believe, and believable baselines mean fewer re-baselines, less contingency held against uncertainty, and faster decisions because everyone trusts the numbers. Each of those represents time and money you keep.
Continuous improvement then compounds the gain. Once the chain shares a Lean mindset and a single set of outcomes, a lesson learned in operation reaches the design team before the next renewal rather than after the next failure.
Your next step
Start thinking about maintenance, renewal and enhancement as a system of systems. This week, select one work package on your programme and trace its decisions back to the outcome your asset owner actually requires. Identify the point where the thread breaks, then ask who else in the chain could have resolved it earlier.
Stop diverging. Start cooperating.
Dr Martin Perks FRICS MICW FQSi | Black Pear Advisory Ltd | +44 7771 865271 | Worcester, UK
Comments