Discussion about this post

User's avatar
Denis Stone's avatar

Ajax was developed from an earlier European model by General Dynamics based in Oakdale/Newbridge in South Wales. This is the same General Dynamics that was responsible for the Army's Bowman radios. Draw your own conclusions.

The Observatory's avatar

This is a forceful critique of a programme that clearly warrants scrutiny. But it is more confident about causation than the available evidence justifies.

The argument reduces the problem to a choice between training failure and design failure, with track tension as the implied mechanism. That is an oversimplification. The issues publicly associated with Ajax, including vibration, noise, integration, and delayed usability, point to a system-level failure rather than a single-point defect. In complex platforms, these effects emerge from the interaction of design, operating conditions, maintenance, and institutional use. Isolating one variable and treating it as decisive risks misidentifying symptoms as causes.

The same applies to the treatment of official statements. ‘Safe within specification’ and ‘not the soldiers’ fault’ are presented as inconsistent. They are not necessarily so. A system can meet technical specifications while proving unsafe or impractical under realistic conditions. The gap between designed performance and usable performance is well established in complex systems and does not require either confusion or bad faith to explain it.

More broadly, the piece treats ambiguity as something that must be resolved into either incompetence or deception. That framing is too narrow. Defence systems are only partially legible by design. Readiness is distributed across personnel, logistics, maintenance, training, and industrial capacity, much of which cannot be exposed without distortion or risk. Under those conditions, explanations are often incomplete and indirect. That is a structural constraint, not in itself evidence of evasion.

There is also a more fundamental issue. The analysis remains at the level of the programme, when the pattern is systemic. Ajax is not unusual because it failed. It is typical of how capability struggles to translate from technical form into operational effect within existing institutional structures. Focusing on whether tracks were correctly tensioned does not address that problem.

The more relevant question is why failures of this kind persist across programmes with different technologies and contractors. That points towards procurement architecture, risk distribution, and the capacity of institutions to absorb new capability, rather than a single technical fault or a single misleading statement.

For a broader treatment of these constraints, particularly institutional absorption and the limits of publicly legible readiness, I have written about it here:

https://observatoryanalysis.substack.com/p/capabilitys-problem-is-not-technologyit

https://observatoryanalysis.substack.com/p/why-readiness-is-discussed-more-than

7 more comments...

No posts

Ready for more?