Many delivery problems are inherited, not created.

There is a particular kind of frustration that comes with leading a delivery function.

Not the frustration of difficult projects. Difficult projects are the job. The frustration comes from what arrives at the door before delivery even begins.

Plans delivery had no hand in shaping

Sometimes it is a study or a design developed entirely by people without delivery experience. The scope looks reasonable on paper. The cost estimate and timeline feel plausible to whoever produced them. But to an experienced delivery leader, the numbers don't add up. The assumptions about what it will actually take, the sequencing, the resource requirements, the risk, have been undercooked. And the delivery function is now expected to execute against a plan it had no hand in shaping and no confidence in.

A portfolio nobody stress-tested

The other frustration is harder to name but just as real. Individual projects get approved through the investment process and each one, in isolation, looks manageable. But when you look across the portfolio, at everything that has been approved and committed to, the aggregate demand on people, capability and organisational bandwidth is virtually impossible to meet. The portfolio was never stress-tested against what the delivery function can actually absorb.

In both cases the delivery function inherits the consequences of decisions made upstream, without having had a meaningful seat at the table when those decisions were made.

Three things that help

Bring delivery input into studies and business cases before they are finalised, not after. A senior delivery leader reviewing a proposal before approval can identify in hours what will take months to unravel in execution.

Build a simple capacity view across the approved portfolio. Not a detailed resource plan, just an honest picture of aggregate demand versus realistic delivery capacity. If it hasn't been done, the answer is almost always that the portfolio is overcommitted.

Create a formal mechanism for the delivery function to flag concerns about incoming work before it is approved. Without it, those concerns surface informally, too late, or not at all.

Delivery is a planning input

The organisations that deliver well have usually worked out that delivery capability is not just an execution resource. It is a planning input. The earlier it is in the conversation, the better the decisions that follow.