Section 4

The UK-Specific Obstacles

Honest acknowledgement of UK-specific obstacles is necessary because unnamed obstacles cannot be navigated. Four obstacles warrant direct treatment: Treasury risk culture, civil service incentives, prime-contractor embedded dependencies, and parliamentary oversight expectations. Members will recognise that each of these is, in part, a product of choices made by Parliament itself.

4.1 Treasury risk culture

Her Majesty's Treasury operates risk management through the Green Book, the Orange Book, and a long-developed culture of scrutiny that treats visible programme overspend as a grave institutional failure and treats capability non-delivery as a softer category of failure with more diffuse accountability. This culture is rational within its own terms — the British state has a long history of IT and procurement disasters, and Treasury discipline exists to prevent recurrence — but it produces the specific failure mode in which novel approaches are under-resourced to the point of non-viability while legacy programmes are over-resourced through political inertia.

Ukraine's equivalent arithmetic is different because the cost of capability non-delivery is measured in territorial losses and dead soldiers rather than in future adjustments to the equipment plan. The United Kingdom cannot and should not replicate Ukrainian incentives. It can, however, create specific ringfenced envelopes within which different risk arithmetic applies. The £400 million UK Defence Innovation unit is a first step in this direction; the envelope is an order of magnitude too small to be the instrument of strategic change, but its existence establishes the principle. The question is how to scale it without importing the legacy Green Book scrutiny that would defeat its purpose.

Practical proposal. A Ukrainian-pattern defence-technology envelope should be structured as a sovereign defence innovation fund with its own risk tolerance framework agreed by the Treasury, the Ministry of Defence, and the Cabinet Office, with explicit acceptance that a proportion of funded projects will fail and that this failure is the price of achieving the distribution of outcomes the Review's ambition requires. The model is closer to a strategic venture fund than to a traditional defence programme, and the governance should reflect that.

4.2 Civil service incentives

The senior civil service's promotion incentives, performance measurement, and institutional culture all favour risk-minimisation and continuity. This is not a criticism of individuals; it is a description of the system. An official who delivers a novel capability at wartime pace and survives is not rewarded disproportionately; an official who presides over a visible failure, however unfairly attributed, may see a career setback. The result is predictable risk-aversion in aggregate, even when individual officials are personally willing to take risk.

Ukraine's Ministry of Digital Transformation solved this through specific institutional design: staff on private-sector-adjacent pay, recruited from the technology community, with performance measured against public delivery metrics rather than process compliance, and with explicit political protection that insulated the ministry from conventional bureaucratic challenge. The Government Digital Service in its early years (2011–2015) operated on similar principles and produced results of similar order, before its mandate was steadily attenuated by conventional civil service reabsorption.

The implication is that a UK defence-technology cluster cannot be built inside the existing Ministry of Defence civil service, with existing pay scales, existing performance management, and existing promotion tracks. It must be established as a separate entity — either as a non-departmental public body, a Ministry-sponsored arms-length body, or in the model of UK Research and Innovation — with bespoke terms and conditions designed to attract technology-sector talent. This costs more per head than standard civil service employment and produces political friction with wider pay restraint, but without it the architectural ambition cannot be staffed.

4.3 Prime-contractor embedded dependencies

BAE Systems, Babcock, Rolls-Royce Defence, Leonardo UK, Thales UK, MBDA UK, and QinetiQ together employ more than 150,000 people in the United Kingdom, operate plants and shipyards in politically salient constituencies across the country, and maintain relationships with the Ministry of Defence, the Treasury, the Department for Business and Trade, and successive governments that are measured in decades. These firms are strategically important to the United Kingdom. They produce categories of equipment — submarines, combat aircraft, armoured vehicles, complex weapons, warships, radar systems — that venture-backed startups cannot and will not produce. They will continue to be the principal contractors for those categories for the foreseeable future, and the architecture proposed in this paper does not challenge that.

The architecture does, however, challenge the primes' position in categories where they are structurally ill-suited to compete: cheap attritable drones, AI-first battle management software, rapid-iteration autonomous systems. Rheinmetall's chief executive comments in The Atlantic in March 2025 — describing Ukrainian drones as "playing with Lego" produced by "housewives" with "3-D printers in their kitchens" — were symptomatic of how legacy primes understand the new category. Rheinmetall's own Skyranger counter-drone system is running substantially behind schedule. The UK primes are no better positioned in these categories, and their incumbency risks crowding out the venture-backed sector the Review identifies as necessary.

Members with significant prime-contractor employment in their constituencies should note that the architecture proposed in this paper does not threaten those jobs; it creates a parallel ecosystem in the categories where primes are not competitive.

4.4 Parliamentary oversight expectations

Parliamentary oversight of defence procurement, through the Defence Committee, the Public Accounts Committee, the National Audit Office, and occasional ad hoc inquiries, is structured around the assumptions of traditional procurement: a small number of large programmes, visible delivery milestones, unit cost and quantity accountability, and retrospective value-for-money assessment. A marketplace-pattern procurement architecture does not map neatly onto these expectations; the accountability question becomes "is the marketplace functioning as intended" rather than "is programme X delivering on time and on budget."

This is a genuine challenge and should not be understated. Parliament's oversight function is legitimate and necessary, and a procurement architecture that cannot be scrutinised effectively is one that should not exist in a democracy. The solution is not to reduce oversight; it is to redesign oversight instruments for the new procurement architecture. The National Audit Office has shown willingness to develop new methodologies for digital procurement; the Defence Committee has demonstrated intellectual engagement with Ukrainian lessons in its 2024 and 2025 inquiries. The groundwork exists; it requires explicit cultivation by the Ministry of Defence and the Cabinet Office, including early engagement with Committee Chairs and their clerks in the design phase. Members have a specific role here: pressing ministers to co-develop oversight arrangements with Parliament rather than to present them as fait accompli.