Where the leverage is lost
Four patterns account for most of it.
Senior people doing junior work. A principal safety case engineer spending two days formatting a document, chasing comments or reconciling a reference list is the most expensive administrative resource in the business. This happens because the support structure around technical specialists is usually thinner than the specialists themselves, and because quality expectations make delegation feel risky.
Knowledge held in individuals. When the method for doing something exists only in one person’s head, the organisation’s capacity for that activity equals that person’s availability. Absences interrupt the work, and departures can take the method out of the organisation altogether. Writing the method down is unglamorous and consistently the highest-return intervention available.
Rework caused by late input. Specialist input arriving after a design or a submission has taken shape produces rework that consumes more specialist time than early involvement would have. The usual cause is a programme sequence that treats assurance as a review gate rather than a design input.
Unclear decision rights. Where it is not clear who can approve something, work queues behind the most senior person available, regardless of whether their judgement was needed. The symptom is a director’s diary that is full of decisions nobody else felt able to take.
What actually multiplies capability
The interventions that work are mundane and cumulative rather than transformational.
Codifying method is the first. Templates, worked examples, decision trees and documented acceptance criteria let competent but less experienced people produce work that a specialist reviews rather than writes. The specialist’s throughput rises substantially, and the quality floor rises with it.
Second is deliberate pairing. Putting an experienced specialist alongside a developing one on real work transfers judgement in a way that training courses do not, and it produces deliverable output at the same time. It costs some efficiency on the first few jobs and repays it repeatedly afterwards.
Third is moving specialist input earlier. Leaving the safety case, the environmental case and the regulatory interface until submission rather than involving them in optioneering is a major avoidable source of rework in nuclear projects. The cost is a modest amount of specialist time at the front. The saving is measured in programme months.
Fourth is explicit delegation. Writing down what each role can decide, and then holding to it, removes a surprising amount of queueing. It also makes capability gaps visible, because a decision that nobody below director level is authorised to take is usually a decision nobody below director level has been developed to take.
Where external support fits
External specialists multiply internal capability when they are used to fill a defined gap and to leave method behind. They dilute it when they become a permanent substitute for capability the organisation should hold.
The distinction is usually visible in how the engagement is scoped. An engagement that produces a deliverable and a documented method that the client team can run next time has built capability. An engagement that produces a deliverable and an expectation that the same supplier will produce the next one has not. For scarce disciplines — probabilistic safety assessment, criticality, specific regulatory interfaces — the second may be the right commercial answer, but it should be a decision rather than a drift.
The other thing external support does well is break the circularity of a team that is too busy delivering to improve how it delivers. Someone has to write the templates, document the method and run the pairing, and the people best placed to do it are the ones with no spare capacity. Buying that capacity for a defined period is often the fastest route out.
Measuring it
Capability improvement is measurable if you choose the measures before you start. Useful ones include the proportion of deliverables produced by someone other than the named expert, the time from specialist request to specialist input, the volume of rework attributable to late assurance involvement, and the number of decisions escalated above the level at which they are formally delegated. None of these require new systems to collect, and all of them move when the underlying problem is addressed.
NCL works with client organisations on exactly this: assessing where capability is being lost, building the method and structure that recovers it, and providing specialist support in a form that leaves the client stronger. Talk to us about your organisation.