Why the Tactician-Technician Exists

In Ukraine, drone systems are modified in real-time to counter GPS jamming, electronic warfare, and other disruptions. Operators and engineers refine software, adjust navigation methods, and swap hardware in the field to keep systems effective under combat conditions. The adversary adapts in turn, and the cycle repeats.

This dynamic has produced a new kind of operator that our panelists described at the Warfighting Innovation Summit: "We're seeing the emergence of what some are calling the tactician-technician. Someone who understands the engineering well enough to modify the tool, and the combat environment well enough to know why it needs to change. It's not something we have a good word for yet. But the fact that it exists tells you everything about how fast the battlefield is moving."

These operators are not outliers. They represent a different model of war, one where modifying and redeploying a system within hours matters more than what it was originally built to do.

The U.S. acquisition and accreditation infrastructure was not built for this. These legacy processes were designed to ensure reliability and lifecycle management for complex systems, and they do that well. But they were also built around a theory of war that prioritized platform sophistication over adaptation speed. Contracting structures built around fixed requirements and defined deliverables make it difficult to push continuous software updates or mission-specific hardware changes once a system has been fielded, and advanced capabilities end up sitting in warehouses rather than reaching the operators who need them.

High-attrition conflict follows a different calculus. When individual units are expected to be lost, the investment shifts away from the resilience of each platform and toward the ability to produce, deploy, and coordinate large numbers of lower-cost systems that collectively stay in the fight. The technology to build effective autonomous systems at that scale largely exists. The procurement and industrial policy infrastructure to produce them in the millions does not.

Fixing that requires structural changes to how the U.S. acquisition and fielding system works. Open architecture standards would allow faster modification and third-party integration in the field. Outcome-based contracting, where the government pays for mission results rather than fixed specifications, would give industry room to keep improving systems throughout a contract rather than locking in decisions made years earlier. Engineers embedded with operational units, rather than siloed in separate development organizations, would feed real battlefield experience directly back into what gets built next. These reforms would create a feedback loop: open architecture enables faster fielding. Outcome-based contracting enables continuous improvement of what gets fielded. Embedded engineers ensure that what gets built next reflects what is actually working in the field.

None of this will happen automatically. The contracting structures, certification timelines, and procurement incentives that slow the current system down were built intentionally. They are the product of decades of institutional decisions that optimized for reliability, lifecycle management, and platform sophistication over speed and adaptability. Changing them requires deliberate policy action, not just organizational goodwill.

What Ukraine and Israel are showing is that this is not a future problem. The institutions that restructure around adaptation speed will define the next era of military advantage. Those who do not will be left behind, and that gap will not be closed by buying better platforms. It will only close when the system that develops, certifies, and fields those platforms moves as fast as the conflicts it supports.