Thought Leaders

When Every Programme Is Amber, Who Gets The Specialist?

Status colours tell an aerospace PMO how far each programme has drifted. They cannot say which one should get the next week of a scarce engineer. A price on that week can, writes Dr Albert Ponsteen.

At the end of March, 143 of the 189 projects in the Government Major Projects Portfolio were rated amber or red, according to the annual report NISTA published in July. The Ministry of Defence runs 44 of those 189 projects, more than a fifth of the portfolio, and carries the highest whole-life costs of any department. Anyone who runs a PMO in aerospace or defence will recognise the picture from their own dashboard. When three programmes in four are amber or red, the colour stops telling you what to do next.

What it leaves behind is a queue. The stress engineer, the certification lead and the systems integration specialist are wanted by four programmes in the same fortnight, and the industry cannot hire its way out: ADS puts unfilled technical vacancies across UK aerospace, defence, security and space at around 10,000 a year. So the next week of those people goes to whoever escalates hardest. The useful test for any PMO software, or any planning method, is whether it can settle that argument with a number: what a week of delay costs on each programme, based on what your people can actually deliver.

Red is a status, not a priority

A RAG rating measures how far a programme has drifted from its baseline. It says nothing about what the drift costs. Two programmes can carry the same red and differ enormously in what a week of waiting is worth.

Take a simplified example. A component supplier runs two programmes through the same certification team. Programme A is a development project whose next gate is eighteen months away, with float to spare. Programme B must deliver a qualified part to a customer’s final assembly line by a fixed slot. Miss the slot and the next one is a quarter away, and the milestone payment moves with it. Both are red. Both programme managers will call their request critical. A week of the certification lead’s time is worth almost nothing to Programme A. On Programme B, it protects a quarter of cash.

The status report treats them as equals. The contract does not.

Aerospace contracts already price the week

Few industries write down the cost of delay as clearly as aerospace and defence. Liquidated damages. Payments released on acceptance. A delivery slot on an assembly line. A booked test range, flight trial or hangar slot. The price of a late week is already in the contract. Most programmes see it only when the penalty lands.

The cost also has a shape. It rarely rises in a straight line. It climbs in steps. A week late into a test window may cost little; the week that misses the window can cost months. And some weeks cost nothing at all. That is good news for a PMO. It means most escalations can wait, and a few cannot.

The expensive weeks queue in front of the same few people

In most aerospace portfolios, the costly weeks gather in front of one or two teams: certification, stress analysis, systems integration, test. Every programme passes through them. When they are overloaded, everything behind them waits, and the waiting is where the money goes.

This is why extra effort elsewhere does not help. A faster design team only lengthens the queue at certification. A week saved upstream is worth nothing if the work then waits a fortnight for the same three specialists.

So the plan has to be built on the real availability of those people, not on the headcount the budget hopes for. The dates will move to where they will really land. Put a price on each of those dates, and you can see which week of waiting is expensive and which costs nothing.

Rewrite the Monday agenda

Most priority meetings walk through the programmes by colour. Replace that with three questions per programme, answered on one page.

Which specialist does this programme wait for next? Name the person or the team, not the work package. It is usually the same few names.

What does a week of waiting cost? Take it from the contract and from finance: damages, milestone payments, slot dates, margin per month. A rough number beats no number. A programme earning £2 million a year in margin loses close to £40,000 for every week it delivers late.

When will it really finish? Use a forecast built on that specialist’s actual availability, not on the baseline.

Then rank the specialist’s queue by the price of the week, not by colour and not by volume. Write down why the cheap weeks wait, so the decision survives the next escalation. Re-rank every week as the forecast moves.

The meeting changes character. “Who is most urgent?” becomes “Where does an hour of this person’s time return the most?” Programme managers still argue. Now they argue about a number they can check.

Spend only where the week is expensive

The same price disciplines every other lever: overtime, contractors, a second shift in test, AI tools. Each pays back only in front of the bottleneck. Anywhere else, it adds cost and no earlier delivery. Before any spend, ask three questions. Is anything waiting on this work? Does the wait cost real money? Can someone, or something, else do it well?

AI is the newest of these levers and the easiest to waste. Aimed at the queue, the arithmetic is simple: free 10 per cent of your bottleneck’s time with first-pass reviews, and you deliver up to 10 per cent more with the same people. Aimed anywhere else, the same tool saves effort that the portfolio never turns into earlier delivery.

Price the week before you sign 2027

November is when next year is committed: delivery dates, bid schedules, hiring budgets. A plan that assumes the specialists are always available is a promise without a price. And the decisions about their time matter more than most PMOs assume. On a sample portfolio of late projects and overloaded teams, a $330,000 loss became nearly $1.3 million of profit. Nothing about the work changed. The decisions did.

Start at your next priority meeting. Ask what a week of delay costs on the programme at the top of the list. If nobody in the room can answer, the order of work is being set by noise, not by value. Scarce people are your strategy. Guard their hours like money.

Dr Albert Ponsteen is CEO of Epicflow, a project portfolio platform used by aerospace and defence organisations including QinetiQ and Fokker Services. His PhD research at the Open Universiteit examined resource allocation in multi-project environments. He has worked with Goldratt’s methods since 2003.

Albert Ponsteen
Related Thought Leaders
Related sized article featured image

Jeremy Campbell
Related sized article featured image

Small firms can now outgun corporate giants, if they stop postponing decisions.

Matthew Barrington-Packer