FM 3-0 Wasn’t Ready: The Doctrinal Shock from Ukraine’s First 90 Days
Ukraine didn’t win the opening rounds because of better doctrine—they won because they moved faster, fought smarter, and turned every cheap drone into a sensor and every squad into a strike cell. FM 3-0 wasn’t ready. But maybe we still can be.

Photo: Petro Zadorozhnyy / State Border Guard Service of Ukraine
No plan survives first contact with the enemy. But some plans don’t even survive the first drone.
Welcome to the Firestorm
When Russia kicked off its full-scale invasion of Ukraine in February 2022, a lot of us—doctrine nerds and trigger-pullers alike—watched to see how well the West’s theories on Large-Scale Combat Operations (LSCO) would hold up under real fire. It didn’t take long to realize something: FM 3-0 (2022) wasn’t ready for this kind of war.
That’s not a dig—it was written with good intentions and solid fundamentals. But what unfolded in those first 90 days of combat in Ukraine dropped a doctrinal nuke on how we think about tempo, fires, C2, and even what “maneuver” means in a drone-saturated battlespace.
This isn’t just about Ukraine. It’s about the U.S. and NATO getting doctrinally punched in the face—and having to evolve. Fast.
The Opening Shock: What Happened in Ukraine
When the first Russian columns rolled toward Kyiv, they ran into more than ATGMs and javelins. They ran into a defense that had adapted—fast. Ukrainian forces:
- Used commercial UAVs and field comms to compress the kill chain down to minutes.
- Practiced mission command in the truest sense—local initiative without permission-based paralysis.
- Coordinated fires using Starlink, Telegram, and tactical mesh nets, bypassing traditional military comms structures entirely.
- Employed a hybrid blend of civilian terrain, digital ISR, and decentralized resistance to turn cities into hellscapes for invading armor.
It looked a lot more like digital guerrilla warfare married to LSCO than anything in FM 3-0.
What FM 3-0 Got Right—and What It Missed
FM 3-0 (2022) was written in the shadow of MDO—multi-domain operations. It anticipated contested domains, peer fights, and the reemergence of large-scale formations. But it didn’t anticipate how wildly nonlinear the battlefield would become.
Here’s what FM 3-0 didn’t prepare us for:
1. Kill Chain Compression
Ukrainians fused ISR and fires like it was their full-time job. Drone-spotted targets were getting smoked within minutes—no lengthy fires approval cycle, no delay in “requesting support.” RAND called this a “flattened sensor-to-shooter loop,” and it shattered traditional command timelinesMilitary Doctrine.
👉 See: FM 3-09 Fire Support still assumes a phased process. Ukraine’s tempo didn’t allow for it.
2. Mission Command on Steroids
Ukrainian units didn’t wait for higher. They executed. A platoon might spot a tank column, drop a pin in a drone feed, and call in HIMARS—no battalion-level mediation. This isn’t an abuse of mission command; it’s the pointy end of it.
👉 FM 3-0 talks about initiative, but what Ukraine proved is that initiative requires trust, tools, and a flattened hierarchy.
3. Non-Linear Terrain = Non-Linear Doctrine
Russia kept trying to fight by map lines and objectives—Kyiv, Kharkiv, Severodonetsk. Ukraine fought by opportunity and denial, turning terrain into digital traps.
Think less “seize the objective” and more “make you bleed every meter you take.” Urban areas weren’t objectives—they were kill boxes.
What Changed After the First 90 Days
By summer 2022, everyone was playing catch-up—including NATO. RAND and NATO’s own war colleges began quietly scrubbing their playbooks. Here’s what started shifting:
Multi-Domain Ops Became Multi-Node Warfare
The tidy separation of domains blurred. Drones fed fire missions. Telegram channels passed targeting data. Starlink became a lifeline.
👉 TRADOC Pam 525-3-1 (MDO 2028) needed to evolve into a more “mosaic” warfare model, as RAND suggested: dispersed, modular, adaptable.
ISR Is Everyone’s Job Now
Every soldier with a DJI became a reconnaissance asset. Field manuals like ATP 2-01.3 (IPB) and ATP 3-12.3 (EW Techniques) started getting real-world rewrites based on Ukrainian improvisations.
Comm & Control Became “Find & Kill”
Old-school comms nets? Too slow. Ukraine used mesh networking, commercial satcom, and real-time group chats. This created what RAND called “ad-hoc battlefield internets”—a doctrinal nightmare for centralized militaries, but a lethal reality.
So What? Why It Matters to Us
This is more than a Ukraine thing. It’s a warning. FM 3-0 may serve as a foundational guide, but future LSCO against near-peer adversaries like Russia or the PRC is going to look more like Ukraine’s first 90 days than any clean doctrinal scenario.
Here’s what we need to fix fast:
- Doctrine must be iterative, not static. Push updates like software patches.
- Commanders must train for chaos, not just coordination. Friction is the new normal.
- Tech literacy has to be tactical. Every squad leader should know how to use a drone, spoof signals, and plug into a fire support loop.
- Decentralization isn’t a buzzword anymore—it’s survival.
From Paper to Dust: What FM 3-0 Changes Might Look Like at NTC/JRTC
Alright—so we’ve chewed through the doctrinal gaps exposed by Ukraine. But theory doesn’t matter unless it gets forged in the crucible, and for the U.S. Army, that crucible is NTC (Fort Irwin) and JRTC (Fort Johnson).
Here’s how the new FM 3-0-inspired adjustments might actually play out in training—and how a thinking OPFOR could punch back.
1. Mission Command Gets Truly Untethered
What changes:
Battalion and below are encouraged to operate with broad operational intent and minimal check-ins, empowered by live ISR and data feeds, not PowerPoint syncs. Units train on rapid kill-chain autonomy—not “report up, wait, maybe shoot.”
In practice at NTC:
- Company-level elements given fire mission authority based on drone ISR and pre-coordinated ROE.
- Observer-controllers (OCs) look for whether they exploit opportunities or freeze waiting for battalion blessing.
- Communications injects simulate degraded networks. If a platoon can’t call higher, can they still kill with what they’ve got?
What OPFOR does:
- Cuts comms or spoofs ISR feeds. Mimics a near-peer SIGINT unit, targeting drone signals, radios, and tactical chat networks.
- Runs a disinfo op during the fight—injecting fake enemy locations to see if units can validate intel in contact.
2. Drones and Ad-Hoc ISR Get Center Stage
What changes:
Drone teams embedded at platoon/squad level. Every element can call targets, validate with drone ISR, and request fires in compressed windows. Drone loss becomes part of the exercise. No free refills.
In practice at JRTC:
- Units issued limited drone inventory per phase. If they burn them on recon with no kill, they feel it.
- Simulated drone feeds get patched into TOCs and even squad tablets (or phones). Can they exploit that data under pressure?
What OPFOR does:
- Launches their own drone swarm with EW overlay.
- Tracks U.S. drone patterns to bait units into ambush kill zones.
- Uses commercial-looking drones for deception—U.S. forces have to decide: is it hostile, civilian, or bait?
3. Non-Linear Terrain and Objective Fracture
What changes:
Maps are less “terrain-centric” and more digitally contested zones. Instead of seizing Key Terrain Alpha, the objective might be: “Deny enemy fires network access within Grid X for 12 hours.” It’s about denial, not dirt.
In practice at NTC:
- A mission objective might be “interdict an OPFOR digital kill chain,” not “secure OBJ Cobra.”
- Teams assigned to hunt enemy sensors, spoof nodes, and break the ISR→fires pipeline.
What OPFOR does:
- Places decoy emitters and bait ISR targets that look high-value.
- Pushes dismounted recon to slip past drones and tag Blue Force elements for HIMARS or 120mm sim rounds.
- Deploys mobile EW assets on timers, simulating real-time relocation and compounding kill chain frustration.
4. Cognitive Load and Chaos Injects
What changes:
NTC/JRTC start throwing faster tempo changes, simultaneous dilemmas, and deception plays. This isn’t about pacing—it’s about cognitive stack overload. Because that’s what near-peer war brings.
In practice at JRTC:
- Multiple injects during mission execution: partial drone feed loss, misinformation via spoofed friendly chat, friendly unit mis-ID’d on Blue Tracker.
- Commanders and platoon leaders are graded on how they manage friction, fog, and digital chaos—not just achieving the endstate.
What OPFOR does:
- Uses captured comms to insert false FRAGOs or update overlays.
- Fakes Blue Force drone chatter to steer real units into chokepoints.
5. Kill Chain Fusion Cells in the TOC
What changes:
TOCs evolve beyond planning shops into real-time kill chain fusion nodes. Analysts, drone ops, fires coordinators, and even AI tools work shoulder-to-shoulder. No more stovepipes.
In practice at NTC:
- TOC gets injected with rapidly unfolding ISR events, and evaluated on how fast they convert it to kills—not products.
- AI sim tools or SME surrogates suggest kill options—TOC staff must weigh human vs automated calls in tempo.
What OPFOR does:
- Feeds fake ISR into TOC’s workflow via hacked sim tool or compromised drone, testing trust in digital feeds.
- Drops multiple simultaneous events (ambush, drone sighting, cyber breach) to test TOC triage under tempo.
Bottom Line: Train Like You’ll Fight in a Future That’s Already Here
NTC and JRTC aren’t just places to get smoked by OPFOR anymore—they’re labs for doctrinal evolution. If FM 3-0 wants to be more than a shelf trophy, the Army’s training centers have to become chaos academies where kill chains are compressed, trust is decentralized, and information is both a weapon and a liability.
The next war won’t wait for approval. Neither should our doctrine.
Final Shots
Ukraine didn’t win the opening rounds because they had better doctrine. They won because they fought smarter, faster, and looser than Russia’s rigid machine. They turned every cheap drone into a sensor, every squad into a strike cell, and every city block into a digital ambush.
FM 3-0 wasn’t ready for that.
But maybe we can be.
