Assessment, command, and training (ACT) theory seeks to explain why some wartime militaries are better than others at learning so as to correctly update how they fight. It is therefore useful to start by defining two concepts that are at the center of this outcome: learning and doctrine.
LEARNING
As traditionally understood, learning involves the act of acquiring new knowledge, skills, and experience. We usually think of learning as something that individuals do. Nevertheless, scholars have long believed that organizations can also learn.1 Of course, I must modify this definition, because I want to understand how a specific subset of organizations (militaries) learn while under extraordinary conditions (warfare). War is a complex phenomenon, and militaries invariably acquire all sorts of new knowledge, skills, and experiences from fighting them. To keep my analysis manageable, I focus specifically on one type of learning: how militaries update, revise, and otherwise change their war-fighting doctrines (which I define below). Learning is also usually treated as something worth pursuing for its own sake. Although I do not dispute this view, wartime imperatives lead me to look at learning in instrumental terms. I am particularly interested in how learning helps a military force become more effective on the battlefield.
These considerations lead me to define learning as the act of updating and refining an existing war-fighting doctrine so as to make it as effective as possible. In other words, it is the iterative process by which a military determines the best way to fight given its goals, adversaries, resources, and limitations. Previous scholars, including Richard Downie, John Nagl, and Janine Davidson, similarly highlight both doctrine and effectiveness in their definitions of military learning.2
It is still relatively unusual to look at military change through the lens of learning. Scholars have traditionally preferred to focus on innovation, adaptation, and emulation. Learning has an advantage over these concepts, because innovation, adaptation, and emulation overlap to such a degree that it is practically impossibleâand analytically arbitraryâto distinguish between them.3 There are, after all, few pure examples of each, particularly in a wartime context. If one looks closely enough, every innovation contains countless smaller adaptations and emulations. The opposite is also true. Emulations involve elements of innovation and adaptation, since organizations cannot copy practice, doctrine, or technology wholesale, at least not if their goal is to improve performance. Subtle differences in culture, structure, geography, and capacity mean that emulators need to modify imported doctrines to make them fit. Such modifications represent adaptationsâand even innovationsâin their own right.
Take, for example, the US Armyâs AirLand Battle, which scholars and policy makers often use as an example of doctrinal innovation. Unveiled in 1982, AirLand Battle outlined a radical new vision for defeating the Soviet Army in Europe. This vision called for American ground troops to conduct rapid combined-arms attacks against Soviet frontline units by harnessing a range of new communications and long-range precision strike technologies. Simultaneously, American airpower would conduct strikes against Soviet command-and-control assets and follow-on forces deep behind enemy lines.4 As such, AirLand Battle represented a radical break from the far more conservative active defense doctrine that preceded it. And at least according to its most ardent proponents, AirLandBattle set the stage for institutional reforms and acquisition programs that helped the United States defeat Iraq in the 1991 Persian Gulf War.
But how innovative was AirLand Battle? Carl von Clausewitz talked about combining speed and maneuver to strike at an enemyâs center of gravity. The microprocessing technologies, long-range weapons, and rapid communications technologies behind AirLand Battle had been around for decades, at least in the private sector. And American planners borrowed the entire idea of using computers and microprocessors to develop long-range deep-strike weapons from the Soviet Union, which was a generation ahead of the United States in thinking about how computers could revolutionize warfare but a generation behind in its ability to actually build them.5
It is ultimately hard to argue that AirLand Battle represented a pure case of innovation, adaptation, or emulation, since it clearly involved pieces of all three. This observation suggests that how one categorizes organizational change largely reflects where one chooses to look. To ignore or privilege innovation, adaptation, or emulation over the other two is to omit a critical part of the causal story.
Thinking in terms of learning helps us bypass these arbitrary distinctions. After all, most of us do not care whether a military is better at navigating wholesale transformation or empowering ad hoc modifications per se. Instead, we care about whether it can change so as to meet wartime challenges and realitiesâchanges that will often require a mix of innovative, adaptive, and emulative behavior. A learning approach helps us pay attention to the organizational characteristics that impede and enable all three important forms of change.
DOCTRINE
If learning is the process through which a military acquires new skills, knowledge, and expertise about how to fight, then doctrine is the mechanism by which it codifies and transmits these lessons. At its most essential, doctrine refers to how a military plans to fight and win on the battlefield.6 Doctrine plays at least five key roles. First, it provides a standard playbook that allows units to coordinate their actions on and off the battlefield. In peacetime, it serves as the basis for developing the training standards that help units prepare for combat. Once the fighting starts, doctrine helps units synchronize their operations in accordance with an overarching set of principles and objectives, even when they cannot communicate with one another directly.7 Second, doctrine educates and socializes junior leaders. By articulating an overarching âtheory of victory,â it prepares new frontline officers and noncommissioned officers to make decisions under conditions of fog, friction, and uncertainty, providing them with guidelines and rules of thumb for acting in the absence of concrete direction.8 Third, doctrine serves as a source of institutional memory, capturing experience and knowledge that might otherwise be lost.9 This function is especially important in wartime, given the casualties and personnel turnover caused by combat. Fourth, doctrine serves as a prescriptive conceptual framework that informs long-term decisions about weapons procurement; recruitment, training, and education; and organizational structure.10 Finally, doctrine helps the entire organization think about the future. The act of bringing officers and experts together to debate about what future battlefields will look like and the best way to prevail on them represents an invaluable opportunity.11 In many respects, the process of developing a new doctrine is probably more important than the document that ultimately emerges.
Unfortunately, it is usually easier to describe what doctrine does than what it is or looks like. Scholars and policy makers alike have a bad habit of using doctrine as a catchall term to describe everything from national strategy (e.g., the Truman Doctrine) to nascent operational concepts (e.g., multidomain operations).12 As I use the term, doctrine has several defining characteristics. It is officially endorsed by top-level leadership and widely promulgated within an organization. It is usually written down, albeit in sometimes frustratingly vague language.13 Yet imprecision does not imply irrelevance. The nebulous and abstract way in which many modern doctrines are written serves an important purpose. As military historian M. A. Ramsay reminds us, military âplanners and writers can deal only in probability and estimates.â14 They must therefore write in general terms that offer âguidance for the force to use in its war preparation without being so specific that it binds too tightly the hands of the future commanders who will have to use it.â15 Doctrine is also multifaceted, not monolithic, insofar as militaries often have multiple overlapping doctrines. Scholars tend to talk about doctrine in singular terms, as if a given military can only have one doctrine at a time. However, contemporary armed forces must perform a wide range of missions, and they often develop separate doctrines for each one. Take the US Army, for example. It had 344 service-level doctrinal manuals as of early 2020, each of which applies to a distinct technical, tactical, operational, or strategic task.16 Field Manual 3-0: Operations, outlines the US Armyâs preferred approach to deter and defeat peer and near-peer adversaries on conventional battlefields. Meanwhile, Field Manual 3-24: Counterinsurgency, describes its doctrine for combating insurgents, guerrillas, and other violent subversive movements.