When a programme slips, the problem is rarely just the plan

Sixteen months behind. Nineteen per cent over budget.

A £45 million nuclear upgrade drifting far beyond what it was meant to be.

That is not a paperwork issue. It’s what happens when pressure builds, trust thins out, and decisions start arriving too late to matter. TEG’s Sellafield case study puts hard numbers around that reality, and it also points to something many complex organisations still miss.

The plan is rarely the first thing that breaks. The decision system is.

Leaders in complex engineering, defence, nuclear, and major contractor environments know this feeling. You can have capable people. You can have experienced managers. You can have controls, reporting, and endless meetings. Yet progress still stalls. Work slows. People defend their patch. Small issues sit too long. Teams stop speaking plainly. Nobody says “we have a trust problem”, but everyone feels the drag.

This is where this gets interesting.

TEG does not position itself as a one off training provider. Our model is built around something more useful, advisory to define what good looks like, delivery to build behaviour in practice, and insight to show what is really happening after the workshop ends. In other words, not activity for activity’s sake, but a connected system for changing leadership behaviour over time.

This matters because complex programmes do not fail in one dramatic moment. They slip through delay, hesitation, and weak alignment. A decision sits for three extra days. A risk gets softened in a meeting. One team assumes another team owns the next move. A manager avoids a hard conversation because the timing feels wrong. Multiply that across a live programme and the cost becomes real.

Our Sellafield case study gives a sharp example. The intervention included diagnostics, assessments, simulation workshops, transparent conversations, and monthly trust pulses. The outcomes were not vague. Decision latency fell by 38 per cent. The trust index rose from 3.1 to 7.4 out of 10. An estimated £3.2 million overspend was avoided, and the MDN bank moved back on track.

A lot of organisations still treat trust as soft. We can all treat communication as a side issue, treating behavioural clarity as something nice to have once the real work is done. Yet our case study points the other way. When trust improves, decisions move faster. When decisions move faster, drift becomes visible sooner. When drift becomes visible sooner, leaders can act before cost, delay, and frustration harden into the new normal.

So what should leaders take from this?

First, co-plan early.

This phrase appears in the case study for a good reason. If different functions start with different assumptions, you do not have alignment, you have parallel versions of the truth. Early co-planning forces teams to surface conflict while it is still cheap. It also shows where language, standards, and ownership are blurred.

Second, stop pretending collaboration happens because you asked for it.

The case study says it plainly, do not just talk collaboration, simulate it. That line should land with anyone who has ever sat through a polished strategy session and then watched the real world ignore it on Monday morning. People do not learn pressure by talking about pressure. They learn it by working through scenarios, constraints, and trade offs that look and feel like the job they actually do.

Third, use evidence before memory rewrites the story.

Many leadership teams rely too heavily on hindsight and instinct. Our broader offer is built on live behavioural intelligence, captured through TEGinsight, so leaders can spot weak handovers, decision bottlenecks, and inconsistency before the next survey or audit arrives. That is a serious shift. It means leadership conversations can move from opinion to usable evidence.

Fourth, treat delay as a signal.

If decisions keep slowing down, ask why. Is ownership unclear? Are people afraid of exposure? Has reporting replaced judgement? Has trust dropped between teams? You do not fix those issues with another slide deck. You fix them by clarifying standards, changing habits, and making behaviour visible.

This is where many growing and high risk organisations get stuck. We can invest in leadership development, but cannot prove what changed. Or can prove attendance, but not performance. Or launch an improvement push, but six months later the system has drifted back to where it started.

Our approach is useful because it closes that loop. It builds leaders, measures behaviour, and gives organisations a way to strengthen the system year after year rather than resetting every time pressure rises.

Now ask yourself something uncomfortable:

• Where is decision latency costing your organisation more than anyone wants to admit?
• Which conversations are happening too late?
• Which teams look aligned in the boardroom but not on the ground?
• Which project is telling you, quietly and repeatedly, that the real issue is not technical at all?

Because when a programme slips, the first casualty is rarely the schedule. It is the illusion that your people are still working from the same version of reality. And this is exactly where the recovery starts.