Military Doctrine Examples: AirLand Battle, the Gerasimov Myth, and How Doctrine Differs from Strategy

"Doctrine" is one of the most misused words in defense writing. Commentators attach it to a leader's speech, a single battle plan or a slogan, and then argue about whether it is "working." Real doctrine is duller and more useful: it is the shared way a military agrees to think and act, written down so thousands of officers can act without waiting for orders.

This briefing separates doctrine from strategy and tactics, then tests the definition against two well-documented cases: the U.S. Army's AirLand Battle, and a Russian "doctrine" that, by the testimony of the analyst who named it, never existed.

What Military Doctrine Means

The U.S. Department of Defense has long defined doctrine as the fundamental principles by which military forces guide their actions in support of national objectives, and has added that doctrine is authoritative but requires judgment in application. We have drawn that wording from mirrors of the Pentagon's dictionary rather than its current online edition, so check it before quoting it formally. The Air Force's own primer describes doctrine as a guide to action that recommends and does not mandate particular courses of action.

Both definitions make the same point. Doctrine is a default, not a script. It tells a commander what the institution expects, and leaves room to depart from it when the situation demands.

Doctrine, Strategy and Tactics: Three Different Levels

The easiest way to keep the terms straight is to ask a different question of each.

• Strategy asks what the war is for and how military force serves that aim. It belongs mainly to political leaders and senior commanders.
• Doctrine asks how this military fights in general. It is institutional memory, written in manuals and taught in schools.
• Tactics asks how a particular unit fights a particular engagement with the forces and terrain at hand.

Strategy can change in a day. Doctrine takes years to rewrite, because it requires new training, new equipment and new habits. That lag is why doctrine matters: it is the slow variable that explains why armies behave consistently, and why they are often prepared for the last war. For a general treatment, see our earlier explainer on military doctrine and why strategy shapes outcomes.

Why It Developed: A Case from the Cold War

AirLand Battle shows how doctrine is born from a specific problem. According to the Army's TRADOC history office, the concept appeared in the 1982 and 1986 editions of Field Manual 100-5, Operations, developed under TRADOC commanders Gen. Donn Starry, Gen. Glenn Otis and Gen. William Richardson. It revised the 1976 edition, which critics argued emphasised defense so heavily that "Active Defense" became its shorthand. They said it underplayed the human element, focused too narrowly on Western Europe and neglected the Soviet practice of attacking in successive echelons.

The answer was to fight the whole depth of the battlefield at once. Under AirLand Battle, air power, Army attack aviation and long-range fires would disrupt Soviet second-echelon forces while ground forces dealt with the front line, backed by local and deep counterattacks, according to the Army's account.

The TRADOC-led doctrine and force transformation "contributed directly to success in the Gulf War of 1990-1991."

- U.S. Army TRADOC Military History and Heritage Office, Army.mil

How It Works in Practice

Doctrine changes behavior through five channels. It sets the vocabulary, so a staff in one unit means the same thing as a staff in another. It shapes training, so soldiers rehearse the doctrine's assumptions. It guides equipment, since procurement follows the way the force expects to fight. It drives organisation, such as how formations are structured. And it frames planning, by giving commanders a standard approach to start from.

The Army's own source says AirLand Battle was never tested in Western Europe, its intended theatre, and credits it with contributing to success in the Gulf War. That is a claim from the institution that wrote the doctrine, and we present it as such. The connection between doctrine and results in a single war is always partly a judgment.

The Counter-Example: A Doctrine That Was Never Written

The "Gerasimov Doctrine" is the standard example of the word used loosely. The analyst Mark Galeotti coined the phrase in a 2014 blog post. In a 2018 Foreign Policy article he disowned it. He wrote that it was "a placeholder," that "it certainly isn't a doctrine," and that "there is no single Russian 'doctrine.'" The 2013 speech by Gen. Valery Gerasimov, he explained, was an analysis of how the Kremlin understood the Arab Spring, the color revolutions and Ukraine's Maidan, and of how to fight such uprisings. It was not a plan for war against the West.

"It certainly isn't a doctrine."

- Mark Galeotti, Foreign Policy, March 5, 2018

The episode matters beyond Russia. When a label spreads faster than the evidence behind it, analysts begin to explain events by reference to a document that does not exist. Our piece on information warfare covers a field where loose labels can mislead in the same way.

Strengths and Weaknesses

Doctrine gives an army coherence. Units can improvise within a common frame, and allies can plan together. Doctrine also has typical failure modes.

• It can be fought against the previous war's enemy.
• It can harden into dogma, with institutions defending it after the facts change.
• It can be written for a theatre or an opponent that never appears.

The Army's description of the 1976 manual, criticised for narrowness in just this way, is a case of the third failure. AirLand Battle was in part a correction.

Current Applications

The Army says AirLand Battle's influence can still be seen in its current multidomain operations concept, which extends the same logic of attacking across depth into more domains. For how new technology pushes doctrine, our analysis of layered counter-drone defense shows a doctrine being tested by cheap drones, and how to evaluate a new weapons system explains why equipment has to be judged against the doctrine that will employ it.

Final Assessment

Doctrine is how an army decides, in advance, what normal looks like. It is slower than strategy and broader than tactics. The useful test for any claim that a country "has a doctrine" is whether you can point to the manuals, the training and the force structure that embody it. If you cannot, you may be reading a slogan.

FAQs about military doctrine

What is military doctrine?

The fundamental principles by which forces guide their actions in support of national objectives. It is authoritative guidance that requires judgment in application.

What is the difference between doctrine and strategy?

Strategy decides what force is for. Doctrine describes how a military generally fights. Tactics apply that to a specific engagement.

What was AirLand Battle?

A U.S. Army doctrine in the 1982 and 1986 editions of FM 100-5, replacing the 1976 emphasis on Active Defense with attack across the full depth of the battlefield.

Is there a Gerasimov Doctrine?

The analyst who coined the term, Mark Galeotti, says no. He called it a placeholder and said it is not a doctrine.