The Doctrinal Gap: Why Tech-First Innovation Fails Without War-First Thinking
Innovation without doctrine is just expensive improvisation.
Not easy, but simple.
Strategic Insights: At a Glance
The Army fielded the Multi-Domain Task Force before the playbook existed, then codified the shift in FM 3-0 Operations.
ERCA’s cancellation exposed how fragile tech-led modernization is without doctrinal integration.
Project Convergence proves a joint kill chain can work in bursts, but adoption lags without authorities, data standards, and rehearsal habits anchored in JADC2.
Historically, doctrine that leads—From Active Defense to AirLand Battle and interwar carrier aviation—creates the conditions for technology to matter.
The modern gap is cultural: demos and slides outrun the unsexy work of TTPs, permissions, and reps.
Opening Scene: Formations Without a Playbook
The Army’s first Multi-Domain Task Force began as a pilot in the Pacific in 2017—framed early as a centerpiece of modernization. A Europe-aligned MDTF followed in 2021, and a third activation in Hawaii arrived in September 2022. Yet the capstone doctrine that explains how the Army fights across domains—FM 3-0 Operations—didn’t codify the shift to Multi-Domain Operations until October 2022. We built the spear before we wrote the manual for how to throw it.
That sequencing meant commanders inherited a formation whose value proposition outpaced the guidance that tells planners where it sits in a campaign, what it enables, and how it integrates with joint fires and authorities. A formation with exquisite sensors and long-range effects can become a boutique asset when the institution hasn’t agreed on its employment. What happens when a unit outruns its doctrine? You get local brilliance, uneven replication, and a lot of “it depends.”
The brittleness showed again when the Extended Range Cannon Artillery moved from years of prototyping to an abrupt cancellation on March 11, 2024. Capabilities that were supposed to knit the joint kill web gained and lost pieces faster than doctrine matured. Readers who followed my note on brittle tech in Operating in the Dark will recognize the pattern: technology races ahead; the human system lags.
Doctrine Leads and Wins
There’s a reason the Army’s doctrinal pivot from Active Defense to AirLand Battle is still taught. The concept matured in schools and staff drills before the decisive hardware arrived in quantity. That sequence—concept first, kit second—built shared mental models so new sensors, munitions, and maneuver schemes found a playbook waiting for them.
Naval aviation’s interwar incubation tells the same story. Carriers didn’t win because they were shiny; they won because the Navy sweat the procedures—flight deck cycles, scouting doctrine, strike recovery—until machine fit method, an arc captured in interwar carrier lessons. When doctrine leads, technology amplifies. When technology leads, you get boutique demos and cold starts on Tuesdays with weather, jamming, and imperfect task org.
Racing to Nowhere: When Tech Outruns the Playbook
“Faster” became a talisman the last decade, as if speed could absolve sloppiness. The Army sprinted to prototype long-range effects, new sensing architectures, and cross-domain targeting workflows. Much was necessary; some urgent. But without a common picture for authorities, task org, and staff processes, demonstrations stayed demonstrations.
Project Convergence tried to break that trap by forcing a joint kill chain into the open—sensors feeding shooters across components, with algorithms collapsing targeting latency. It worked often enough to prove the physics. The problem is adoption. The joint force still lacks the shared muscle memory that turns a demo into doctrine, then doctrine into habit. How do you train a kill chain that stretches across Services if the playbook isn’t written and drilled in the units that will actually fight?
Adversaries don’t skip this step. China’s PLA publishes concepts like “Systems Destruction Warfare” before fielding new capabilities, then drives them into exercise cycles until they’re second nature. Russia’s reforms after 2008 did the same for battalion tactical groups. We are still prone to fielding the kit first and trusting doctrine to catch up in the next rotation.
Then came ERCA’s reversal. The program’s cancellation removed a deep-fires leg formations like the MDTF expected to lean on. That doesn’t doom the concept, but it exposes the risk of building an orchestra around instruments still in the workshop. As I argued when we weighed credibility in Strategic Deterrence: Why It Fails When It’s Needed Most, claims wither when pieces don’t show up together, coached by doctrine that actually gets reps.
Doctrine by PowerPoint: The Modern Gap
Today’s gap isn’t a lack of ideas; it’s a lack of institutional digestion. The enterprise rewards proofs of concept and wins on slide 12, then struggles to grind those wins into field manuals, resourcing lines, and training-center reps. ReARMM cycles talk alignment, but without hard doctrinal guidance on roles, command relationships, data standards, and battle rhythm, units meet new tech like a guest lecturer—interesting, not formative.
The MDTF is a case study. On paper, it’s built to fracture A2/AD and enable joint penetration, a centerpiece of modernization that senses, jams, and strikes while setting conditions for other formations. In practice, employment depends on theater, commander, and joint maturity. Variance is expected early; institutional variance years later signals doctrinal anemia. If doctrine is the genome, the formation shouldn’t change species at every boundary.
That’s why the real value of the initiative we explored in Will the Real Project Convergence Please Stand Up! isn’t a gadget buffet—it’s a forcing function for joint targeting discipline under a JADC2 Strategy umbrella. Until Services translate those lessons into the unsexy things—TTPs, permissions, interfaces, and staff training—“multi-domain” will remain more adjective than verb.
Experimentation vs Adoption (Rehearsal Without a Script)
Experimentation is supposed to be messy. Adoption isn’t. The first tolerates failure as teacher. The second treats failure as a signal that something in doctrine, training, or resourcing still isn’t real. Units don’t need more demos; they need more reps where the gear shows up with a script the formation recognizes—and a red team trying to break it.
A recent JRTC rotation illustrated the difference. A brigade deployed a new sensor-fusion tool during the opening days, dazzling in the first engagement. But without rehearsed contingencies for loss of comms or data-feed corruption, the system went dark in the second fight. The kit was there; the doctrine to fight through friction wasn’t.
Project Convergence’s best moments showed where adoption must go: distributed sensing, automated target nomination, and authorities sequenced to collapse the sensor-to-shooter timeline. That has to land in the schoolhouse and the CTCs as doctrine, not just as a highlight reel. Otherwise we repeat the cycle: a handful of experts make it sing in the desert; everyone else reads the AAR and hopes their S-6 got the slide deck.
Our readers know the stakes. In Paper-Ready, Combat-Dead, I laid out how paper-grade readiness masks combat-grade gaps. The unit with better rehearsal habits usually beats the unit with the better press release. That isn’t cynicism; it’s physics.
Counter-Arguments and Rebuttals
Urgency. “Threats don’t wait for manuals.” True—but urgency is a reason to accelerate doctrine, not skip it. The WWI-to-WWII arc shows what happens when Services iterate doctrine in contact with reality and then lock it in with ruthless training.
Do it now; write later. Learning scales only when the lesson is captured, codified, and injected into institutions with teeth. The Army’s own history turning Active Defense into AirLand Battle is proof.
Tech outruns doctrine anyway. Only if you treat doctrine as a book instead of a process. Doctrine is a living consensus about how to fight; if it can’t iterate alongside software drops, the problem isn’t doctrine—it’s ownership.
“Joint” is a policy problem. It’s both. Project Convergence showed the joint kill chain is possible; now doctrine must make it normal—under a resourced JADC2 framework the Services write to each other, not just about each other.
Building Without a Blueprint
The blueprint exists. We’ve used it before. Write the concept, train it into the force, then let technology slot into roles the formation already understands. That is the opposite of spray-and-pray modernization. It is slow in calendar time and fast in combat time because units don’t need a hero to make the slide come true—they need reps to make the outcome boringly repeatable.
So here’s the ask: treat doctrine as a production line, not a pamphlet. Push the Multi-Domain playbook into the hands of the people who will actually fight, then make them prove it works under friction, jamming, and bad weather. If the kill web only functions at the demo, it’s not readiness. If your plan depends on a program that just died in testing, it’s not integration. The joint force doesn’t need one more sizzle reel; it needs shared habits that survive first contact. Learn from the lessons of others so that you don’t become the lesson.
AI Summary
This essay argues that U.S. military innovation fails when technology outruns doctrine, using the MDTF timeline (Pacific pilot in 2017; Europe in 2021; Hawaii activation in 2022), ERCA’s 2024 cancellation, and Project Convergence to illustrate the gap between demos and adoption. Historical cases—AirLand Battle and interwar carrier aviation—show doctrine must lead before technology scales. It contrasts U.S. sequencing habits with adversary models, adds a CTC vignette to illustrate adoption gaps, and calls for embedding lessons into the DoD JADC2 Strategy framework. The conclusion: doctrine-first modernization beats technology-first improvisation in combat time.