Summary
In 2012, U.S. Army brigade commanders began documenting in writing that the Distributed Common Ground System—a $5 billion intelligence platform—was failing in theatre. Commanders reported that DCGS "translates into operational opportunities missed and lives lost." The institutional response was not to investigate the system. It was to investigate the commanders.
Army leadership went to "extraordinary lengths" to suppress criticism. Service members who spoke about DCGS failures feared career consequences. The system's primary advocates were the acquisition offices and prime contractors whose budgets depended on programme continuation.
The Double Victim Problem
Military operators face a structural bind identical to crime victims who receive no institutional support. When a fielded system fails, the operators who depend on it must simultaneously improvise a solution under operational pressure, document the failure, propose alternatives, navigate the acquisition bureaucracy, and withstand institutional resistance—while continuing to fight. The people with the clearest evidence of failure are the least equipped to force a procurement correction. The institutions with the authority to correct are the most captured by the incumbent solution.
Need-Definition Inversion
The fundamental failure is not technology selection. It is need definition. When requirements are well-defined, acquisition processes can select appropriate solutions. When requirements are ambiguous or evolving, the process inverts: vendors define the need to match their existing product. The match appears perfect until deployment.
This inversion explains DCGS persistence despite a decade of negative field reports. The need was defined at a level of abstraction—"fuse ISR data across the enterprise"—that the system could claim to satisfy on paper. The operational need—"give the analyst in this FOB usable intelligence in thirty minutes"—was specific enough to be tested and therefore specific enough to fail. The procurement system optimised for the abstract requirement and became structurally unable to hear the concrete one.
Bad Contracts Produce Bad Technology
Observers who inspected cleared contractor facilities noted that poor technology consistently traced to poor contracts, not poor engineering. The defence acquisition process requires graduate-level education to navigate. As systems grow more complex, the gap between what operators need and what contracts specify widens.
One serving officer's assessment: "Publicly held companies with huge profit margins and demanding stockholders tell the military what they need, versus the military going to the companies telling them what they need to accomplish their mission."
Counter-Drone Procurement Risk
The counter-drone sector is entering this cycle now. The proliferation of small UAS threats has produced a rush of C-UAS programmes, each with its own requirements process, prime contractors, and problem definition. Programmes that define "counter-drone" as a sensor-and-interdiction problem will produce sensor-and-interdiction systems. The operational need—maintaining logistics, movement, and evacuation in a battlespace saturated with persistent surveillance—will go unaddressed because it does not fit an existing programme of record.
The Palantir precedent is instructive. A commercial data integration tool, not purpose-built for military intelligence, was adopted by field operators over a $5 billion programme of record because it solved a defined problem at the point of use rather than satisfying an enterprise architecture requirement at the point of procurement. The equivalent opportunity in contested logistics is not another C-UAS platform. It is the integration layer that connects existing systems—route planning, casualty tracking, supply chain—under the assumption that adversary surveillance is persistent and sensor denial is temporary.