Introduction
The United Kingdom has reformed defence acquisition twenty-eight times in sixty-five years. Each reform was designed in good faith. Each attempted to address genuine failures: cost overruns, programme delays, requirements drift, poor supplier engagement, fragmented oversight. And each, in its own way, fell short.
This is not a criticism of the people involved. Many of the reforms were well-structured, intelligently argued, and sincerely implemented. The problem is structural, not personal. The reforms kept fixing the same visible symptoms without addressing what was producing them.
The Missing Layer
Every acquisition system contains layers. At the top sits national strategic intent: the government's judgement about what defence must achieve. At the bottom sits the point of transaction: where money is spent, contracts are awarded and capability is built or bought. Between those two layers, there are requirements frameworks, programme structures, commercial instruments, supplier relationships and oversight mechanisms.
But there is a layer that has never been formally built. This report calls it Layer 2: problem architecture. It is the structured discipline of defining what capability is actually needed, in what form, to achieve what effect, before requirements, programmes, frameworks and suppliers take over.
"Without problem architecture, requirements float free of strategic intent. Programmes are optimised for delivery against specifications that were never properly validated. Suppliers respond to what they are asked for, not what is actually needed."
The absence of this layer is not a small omission. It is the reason that well-intentioned programmes produce outputs that do not integrate. It is the reason that SMEs with genuinely relevant capability struggle to navigate a system that cannot articulate what it needs. It is the reason that each new reform eventually produces the same complaints, because the layer that would hold the system together has never been built.
A Four-Layer Acquisition Model
The report proposes a four-layer model for thinking about defence acquisition:
- Layer 1: Strategic intent. What the nation needs defence to achieve. This layer is the responsibility of government and exists in policy documents, defence reviews and strategic guidance.
- Layer 2: Problem architecture. The translation of strategic intent into defined capability needs, structured problem spaces and coherent design questions. This layer does not currently exist as a formal discipline.
- Layer 3: Technology orchestration. The identification, integration and validation of technologies that address defined capability needs. This is neither procurement nor research. It is a distinct architectural function.
- Layer 4: Programme and commercial execution. The mechanisms through which capability is acquired, developed, contracted and delivered. This is the layer that receives the most attention and the most reform.
The current system effectively operates as a three-layer model, collapsing Layer 2 into Layer 1 and Layer 3 into Layer 4. The consequences are predictable and well-documented.
Five Load-Bearing Reforms
The report proposes twenty-one reforms across the four layers. Of these, five are especially load-bearing in that the others depend on them or are significantly constrained without them.
The first is building the missing problem architecture layer as a formal, resourced, standing discipline within the defence acquisition system. This is not a study team or a working group. It requires permanent capacity, professional standing and institutional authority.
The second is creating a standing strategic-intent function that translates government defence policy into structured, testable capability requirements at sufficient resolution to actually guide acquisition. Strategic intent at the level of published defence reviews is not actionable by the acquisition system without this translation.
The third is recognising technology orchestration as an architectural layer, distinct from both research and procurement, with its own professional community, vocabulary and accountability. SMEs are disproportionately relevant to this layer, and the current system has no coherent mechanism for engaging them at the point where their contribution would be most valuable.
The fourth is governing the architecture over time. Capability needs change. Strategic context evolves. Technologies mature. The architecture must be maintained as a living system, not produced once and filed.
On SMEs and the Access Problem
Small and medium-sized enterprises occupy an awkward position in UK defence acquisition. They are frequently cited as sources of innovation, agility and specialist technical capability. They are regularly invited to participate in defence engagement events, innovation programmes and framework consultations. And they are, with notable exceptions, structurally excluded from the acquisition decisions that matter.
This is not primarily a consequence of bad intent or deliberate gatekeeping. It is a consequence of missing architecture. When the problem space is not defined, there is no obvious point at which an SME's capability can be evaluated against a genuine need. The system defaults to familiar suppliers with established relationships, not because those suppliers are always best placed to deliver, but because they have the institutional relationships required to navigate a system that is not architected to receive new entrants at the relevant decision points.
The report does not argue that SMEs should receive preferential treatment. It argues that the architecture of the acquisition system should be rebuilt so that capability, rather than incumbency, becomes the primary factor in decisions about who contributes to national defence.
This Report
This report is published as a public-good contribution to the UK defence acquisition reform debate. It is not a product brochure or a sales document. Espanaro has interests in this space, and those interests are disclosed. But the argument stands or falls on its own merits, not on our commercial position.
The report is intended to be read, challenged, shared and improved by defence, government, industry, engineering and policy communities. If the argument is wrong, we want to know. If the architecture is incomplete, we want to understand where. If there are reform proposals in here that are impractical, politically impossible or technically naive, those are useful things to establish through open debate rather than to leave unexamined.
The full report, executive summary, policy brief, infographic, companion deck and one-page brief are available to download below.
Download the report pack