Why Infrastructure Delivery Experience Matters More Than You'd Expect

Infrastructure delivery isn't siloed from customer success. Every customer success manager in construction works within delivery constraints, utility dependencies, and stakeholder complexity that mirrors what I've managed for 9 years. The difference is that most CSMs in infrastructure don't have direct delivery experience. They manage client relationships around work they've never personally executed. That gap creates risk for the client and for the business.

Why Delivery Experience Translates Across Industries

Customer success is fundamentally about ensuring clients achieve the outcomes they were promised. In infrastructure, those outcomes are physical. A pedestrianisation scheme either gets built or it doesn't. A traffic management drawing either passes TfL approval or it delays the programme by 6 weeks. The stakes are concrete and the feedback loop is immediate. Managing in that environment builds a type of outcome-focus that's hard to develop in roles where failure is more abstract.

When I moved between concurrent projects at Old Street and Farringdon, managing Gas Networks as the critical path constraint across both sites, I was managing programme-level risk in real time. The same skill applies when a customer success manager is managing two enterprise accounts with shared implementation timelines and a single vendor dependency. The context is different. The thinking is the same.

What Customer Success Managers Learn from Infrastructure Delivery

Infrastructure delivery teaches constraint management. You can't extend a permit window by asking nicely. You can't move a utility by shifting a slide in a deck. You have to build coordination governance that makes the constraint manageable, and then you have to deliver inside it. That discipline transfers directly into customer success where timelines, resource constraints, and third-party dependencies are constant.

Delivery experience also teaches you to read risk before it becomes a problem. On Newington Green, the Thames Water sewer relocation was a potential 12-week schedule extension and £2.8M cost overrun. We identified it early, embedded Thames Water's delivery team in our weekly governance meetings, and turned it into a 4-week early completion. Customer success managers call this proactive account health management. In delivery, we call it reading the critical path.

How Delivery Thinking Solves Customer Success Problems

The most common customer success failure mode is reactive account management. A client escalates. The CSM scrambles. Relationships get damaged and commercial risk follows. Delivery thinking is inherently proactive because schedules are forward-looking by definition. You're always managing against a future state, not responding to a past event.

When I implemented the risk register methodology that separated site-level risks from programme-level risks on the Old Street and Farringdon concurrent delivery, I was doing exactly what a customer success manager should do when managing multiple accounts with interdependencies. Segment the risk. Prioritise the programme-level exposure. Don't let a site-level issue cascade upward unnecessarily.

Portfolio Thinking as Customer Success Framework

Managing a £38M portfolio across multiple concurrent sites requires portfolio-level thinking that most project managers don't develop. You have to hold individual project health and programme-level health simultaneously. Resource allocation decisions at the programme level affect individual project delivery. Communication cadence with TfL has to account for both Old Street and Farringdon without creating information overlap that confuses their programme team.

That's exactly the thinking a customer success manager needs when managing a book of accounts. Individual account health matters. But so does portfolio health. Which accounts are at risk of churn. Which are candidates for expansion. How does the overall portfolio trend affect the business. Infrastructure portfolio delivery is training for infrastructure customer success management. The full concurrent delivery case study is at olamapped.com/old-street-farringdon-programme.