The United States is racing to field AI and autonomous systems. It is not racing to figure out how to fight with them. This imbalance between technology and concepts is widening a gap the U.S. is ill prepared to close. Ukraine has shown us why this gap is a threat: every new capability breeds a countermeasure, and technological advantage now spoils in months. The answer is not just faster innovation. It is making concept development a continuous military function, one that ties new technology to experimentation, validation, and adoption at the speed the fight demands. Not just a function of schoolhouses and Headquarters.
Russia’s full-scale invasion of Ukraine began in 2022 as a war of armored columns and maneuver. Today, trenches and minefields stretch for hundreds of miles, reminiscent of World War I; while drones, unmanned ground vehicles, precision munitions, and persistent surveillance hunt anything that moves.
The United States has poured considerable energy into buying and fielding new technologies faster, and has shown how we are endeavoring to learn from Ukraine. But the U.S. has put far less energy into the institutional processes we need to determine how we fight as technology and adversary behavior changes. This creates a consequential gap between what we build and how we fight.
This growing gap has two parts. The first is substance: technology and concepts need each other. A concept that ignores new technology will overlook new operational possibilities, while a new technology without a concept is a demonstration… not a warfighting capability.
The second is tempo: technology moves in weeks and months, while the processes that decide how formations should use it operate in years. Our fastest-ever concept cycle, from counterinsurgency doctrine to the Iraq Surge, took eighteen months. Most move slower still: gradual, methodical, and caked in decades of calcified bureaucracy.
The problem isn’t just that doctrine changes more slowly than technology. Units in combat adapt fast. The greater challenge is translating those adaptations into concepts that can be tested, refined, integrated into combined-arms operations, and adopted across the force.
That doesn’t mean rewriting concepts every time a new drone appears. It means recognizing when a change in technology (or in the enemy) breaks assumptions behind how we fight, then testing and spreading the fix before it goes stale.
Concept development must become a continuous military function, not a periodic publication. The winner won’t be the side that buys technology fastest, but the side that turns it into battlefield advantage before the enemy adapts. Today, the U.S. is not built to do that quickly.
Ukraine: Adaptation as Necessity
Ukraine illustrates the increasingly reciprocal nature of battlefield adaptation. To date, every advantage has invited an answer. Both sides have changed their technology and tactics again and again in response to each other, and neither has held an edge for long.
Consider the first-person-view (FPV) drone. Cheap, attritable, and easy to build, FPVs turned every squad into a precision strike force. Electronic jamming became its counterpoint. Fiber-optic drones, immune to jamming, then entered the field. Each move created new openings and new limits, and forced changes in both the technology and how it was used.
The operational consequences extend well beyond FPV drones. Persistent surveillance paired with cheap precision strike has changed where and how formations can move, mass, resupply, and survive. Concealment, dispersion, and deception matter more than ever. A unit that concentrates in a location, moves in the open, or runs a predictable supply route becomes a target.
This is the more consequential lesson from Ukraine: a technological innovation may initially improve the effectiveness of a particular weapon or unit, but its broader significance emerges when it changes the conditions under which formations operate. Then the enemy adapts, and the cycle starts again. And again.
In Ukraine, technological advantage is perishable. The hard part isn’t fielding new capabilities. It’s recognizing when they, or the enemy’s countermeasures, demand a different way of fighting.
The American Challenge: From Innovation to Institutional Learning
For the United States, Ukraine demonstrates why concept development cannot remain an episodic activity conducted in schoolhouses and periodically revisited. The lesson is not that Ukrainian solutions are universally applicable. It’s that new technology and countermeasures can break operational assumptions faster than our institutions are built to respond.
The United States cannot just replicate Ukraine’s approach. U.S. forces fight expeditionary campaigns, integrate across joint and coalition formations, and answer to policy, legal, and safety requirements that a nation like Ukraine, fighting for its survival and territorial integrity, does not. The goal is Ukraine’s capacity to adapt, built to American requirements.
Our gap isn’t a shortage of experiments or innovation offices; efforts like the Army’s “Transformation in Contact” are putting new capabilities into units and learning from them. Our gap is having a pathway from what one unit learns, to what the whole force learns. A concept that works in one brigade may fail against a different enemy, in different terrain, or at a higher echelon. And a successful experiment rarely changes training, force design, or acquisition on its own.
Autonomy has raised the stakes and made our pathway to institutional learning an even greater necessity. A software update, a retrained model, or a new way of employing a system can change how technology behaves, and can quietly invalidate the conditions under which it was tested and fielded.
That is the problem assured autonomy is meant to solve. Assured autonomy is justified confidence that an autonomous system will do what it is supposed to do. It must therefore account for the whole relationship: the technology, how it is employed, and the environment it operates in. Continuous, evidence-based assessments can tell commanders when a change requires fresh evaluation and where the boundaries of responsible use lie. Built into the adaptation process, assurance can support speed without abandoning safety, reliability, accountability, or established approval authorities.
Building an Adaptive Concept-Development Enterprise
The United States needs a repeatable process that links new technology, operational concepts, experimentation against a thinking enemy, validation, and adoption across the force.
We are suggesting neither a prototype nor a concept paper. It’s a validated, revisable concept of employment, backed by operational evidence: how a formation can fight differently, under what conditions that works, and what it takes to make it happen. Four functions are needed to get us there:
First, connect concept and technology development directly to operational formations.
Operators, technologists, testers, and concept developers should work alongside commanders. Their job goes beyond improving systems or inventing tactics: they should identify which operational assumptions a new capability breaks, and draft concepts to test.
Not every improvement demands a new concept. A better jammer may only need a new tactic; a capability that changes how a brigade moves, masses, or resupplies demands a new way of fighting. The force needs people close enough to the fight to tell the difference.
In Ukraine, operational units have designated innovation officers liaising directly with industry; industry partners provide prototypes, receive feedback on battlefield experimentation and adaptation. Through this relationship, operators, technologists, and testers converge on a specific requirement, and battalion-level Commanders have the authority to acquire the necessary prototypes to integrate into their formations.
Second, establish a persistent cycle of adversarial operational experimentation.
The question isn’t whether the technology works as designed. It’s whether the formation using it accomplishes the mission better against an opponent who adapts. Experiments should also find where a concept fails: what works against one threat may fail against another, and a promising system may impose unacceptable costs elsewhere in the formation.
Combat training centers, experimentation units, and operational formations already provide the foundation. The task is to link them into a persistent learning loop, fed by operational evidence and intelligence.
Ukraine offers a cautionary tale. For nearly three years, intelligence indicated Russia was developing jet-powered Shahed variants, by most accounts ample time to prepare countermeasures. But when Russia began launching these faster one-way attack systems, Ukraine had too few interceptors capable of that speed, and their previous interception tactics were insufficient to stop them. The warning did not sufficiently feed a cycle of experimentation before the threat was fielded. That gap cost lives.
Third, connect operational validation to adaptive fielding.
Today, a system is typically tested, approved, and fielded as a finished product. But in a fight like Ukraine’s, nothing stays finished: software is updated, models are retrained, and units find new ways to employ what they have. Each change can quietly invalidate the evidence behind the original fielding decision. Adaptive fielding treats validation as continuous, asking what has changed and whether the earlier evidence still holds.
For autonomous systems, this is where assured autonomy matters most, and where scrutiny should match the modification. A minor software patch for a drone flying the same mission in the same conditions may need only a quick check. Retraining its targeting model, sending it into a new environment, or reducing human supervision demands full re-evaluation. This doesn’t bypass approval authorities or testing requirements. It gives them a faster, evidence-based way to decide when more evaluation is needed.
Fourth, institutionalize validated concepts across the force.
This is the decisive step. Experimentation produces evidence; learning happens only when that evidence changes how the force trains, organizes, equips, and fights.
A counter-drone tactic proven in one division should appear in the next combat training center rotation, the next force design update, and the next acquisition…not in an after-action report on a shelf.
This change requires a defined pathway and clear authorities. Commanders, testers, capability developers, and acquisition officials each own different decisions, but those decisions must draw on a common body of operational evidence, with clear decision points for when the evidence is strong enough to act. The result is a continuous cycle: develop, experiment, validate, field, learn, institutionalize, adapt. Then repeat, as the technology and the enemy change.
In Ukraine, Aerorozvidka, a non-governmental organization, plays this role: not a think tank but an empowered change agent -- capturing evidence from the field and shepherding it through commanders, technologists, and acquisition officials until new tech is deployed or new concepts (like deep strike) are fielded.
Operational Advantage Depends on the Capacity to Learn
The United States possesses substantial technological, industrial, and innovative capacity to compete in AI and autonomous warfare. But technological leadership alone will not produce operational advantage. Adapting a system isn’t the same as adapting a force, and a better-performing unit doesn’t change the course of a campaign.
Four questions will dictate our capacity to learn: The technical question is what a system can do. The tactical question is how formations should employ it. The operational question is how it changes the way maneuver, fires, intelligence, protection, sustainment, and command combine to win. The strategic question is whether the institution can answer all three, again and again, faster than the enemy.
The race isn’t to build the best autonomous systems or to field them first. It’s to turn technological change into operational advantage, faster than the enemy can take it away. In the age of AI and autonomy, the force that learns fastest wins.
The Cipher Brief is committed to publishing a range of perspectives on national security issues submitted by deeply experienced national security professionals. Opinions expressed are those of the author and do not represent the views or opinions of The Cipher Brief.
Have a perspective to share based on your experience in the national security field? Send it to Editor@thecipherbrief.com for publication consideration.
Read more expert-driven national security insights, perspective and analysis in The Cipher Brief
