Shipping a platform after four years of trying

The situation

A technology function inside a large energy company — 2,000 people in the function, 70,000 people in the wider organisation — had been trying to ship a new platform for four years.

The intent was clear. The investment was substantial: around £250 million per year of run rate spend plus investment, across the four-year period. The headcount was real — 2,000 capable professionals, a mix of engineers, architects, analysts, project managers, and leaders. Everything that a platform delivery of that scale should have.

And yet nothing shipped.

Not in year one. Not in year two. Not in year three. And as the fourth year began, the organisation was still running the same programme, with the same kind of plans, under the same pressure to deliver.

The financial picture was stark. Around a billion pounds spent across the four years. Zero tangible financial value produced. Everything that had been spent was, structurally, cost. The platform existed partially in various stages of completion, but nothing had reached a customer, nothing had been adopted, nothing had returned on the investment.

What was really happening inside

The numbers alone don't capture what the work felt like from the inside.

Of the 2,000 people in the function, only around 850 were doing the work that would actually become the platform — the Category 1 building work. Another 500 were in varied supporting roles.

250 had been effectively assigned themselves to the Netflix challenge — an informal culture that had emerged among some of the workforce of watching as much Netflix as possible during work hours without being caught. That wasn't a rumour; it was a documented cultural pattern that was later written up in a separate essay on how disengagement metastasises in organisations that don't know how to use their people.

Roughly 400 of the 2,000 were effectively unknown — the organisation couldn't tell me reliably what they were working on, or why.

Engagement data from the function was sobering: 75% disengaged. Of the people whose work could be characterised, 65% were in management and coordination roles; only 35% were in direct idea-realisation work.

This is what a delivery ratio problem looks like at scale. Too many people organising, too few people building, a culture that had quietly given up on shipping, and a billion pounds of internal cost accumulating without producing a pound of financial value.

What changed

I came in as a business change coach, partnering directly with the function's leadership. The role was less about running the transformation and more about helping the leadership team see their own situation clearly enough to make different decisions — thinking partnership – at the altitude where decisions about thousands of people and hundreds of millions of pounds get made.

The work took three interconnected shifts.

Seeing the system honestly. The first work was helping leadership see what they were actually running — not the plan version, the real version. Where cost was accumulating. Where decisions were stalling. Where the coordination overhead had grown beyond what the delivery required. This wasn't a cost-cutting exercise. It was a diagnostic one. Before anyone could decide what to change, everyone had to agree on what was actually happening.

Rebalancing the delivery ratio. Once the picture was clear, the shift began. Roles moved from coordinating to building. Layers of approval and reporting were thinned. The people who had drifted into organising work — often because reporting and governance had crowded out their original craft — were invited back to the work they'd started their careers on (and actually wanted to do). Many of them welcomed it. Few of the organising roles were cut; most were repositioned closer to the making.

Changing the climate. The third shift was the hardest to name but the most important. The culture that had produced the Netflix challenge wasn't a discipline problem. It was a meaning problem. People had disengaged because the work wasn't producing anything they could point to with pride, and the environment had stopped expecting them to. Rebuilding that expectation — gradually, through how decisions got made, how progress got talked about, how success was recognised — changed what it felt like to be inside the function. Engagement became a lead indicator rather than a lag one.

The outcome

The platform shipped in eight and a half months.

The budget required was around £155 million against the £200 million that had been provisioned for the following year — saving roughly £45 million on the original forecast.

Value produced, net of the cost reduction and the revenue from platform adoption, was estimated at around £200 million in the first year after shipping.

Engagement, measured through the function's internal surveys, moved from 75% disengaged to 81% engaged — an inversion, not a drift. Of the engaged 81%, the delivery ratio also inverted: 70% now in direct idea-realisation, 30% in management and coordination. Same people. Different structure. Different expectation.

The remaining budget that had originally been set aside for year five of the programme — around four months of run rate — was redirected to the next platform project, which had been stacked in the queue un-started for the same four years. So the organisation got not one shipped platform but the acceleration of a second one, without additional funding.

The before-and-after, in numbers

What this is, and isn't, evidence of

Case studies are useful but they require care in how they're read.

This engagement worked because the conditions were specific. The leadership team was willing to see their own situation clearly — which is not a given, and is the single biggest filter on whether this kind of work is possible.

The function had capable people; the problem wasn't talent, it was how the system around the talent was organised. The organisation had enough runway to sustain the shift through the months where the numbers didn't yet show change. And the broader business was willing to wait for a real shipping event rather than demand another round of partial milestones.

Where those conditions don't hold — where leadership is defensive, where the talent isn't there, where the runway has already run out, where the organisation demands monthly proof points — the same approach produces different results. Sometimes no result at all. This isn't a methodology that works mechanically. It works when the conditions for thinking clearly together are present.

The principles underneath what changed are the ones this site is built on: everything between idea and value is cost unless it's deliberately shaped; the delivery ratio matters more than the headcount; climate and meaning are part of the system, not variables within it. Those are the Idea to Value system in practice. The case study is one instance of what happens when they're applied to a situation where they're badly needed.

If you're reading this because you're navigating something similar

The starting point isn't a transformation programme. It's a clear look at what's actually happening — the delivery ratio, the painted picture, the cost accumulation, the disengagement, the meetings-to-value ratio, the place where cycles stall. Most organisations haven't seen their own situation that honestly in a long time, because the internal politics of the view make it hard to produce.

If that sounds like where you are, the first call is where we talk about it. Not a pitch — just a conversation about whether the kind of work described here is the kind of work you need. If it isn't, we'll say so, and point you somewhere better suited.