Feb. 7, 2020 —
Lieutenant Colonel Trent J. Lythgoe, USA, is an Aviation Officer currently serving as an Instructor at the U.S. Army Command and General Staff College. He is pursuing a Ph.D. in Political Science at the University of Kansas.
The U.S. Army’s mission command doctrine has sparked considerable discussion and criticism among Service professionals. Most agree that mission command is the right approach for commanding and controlling Army formations. However, some argue that the Army’s de facto implementation of mission command fails to live up to its intellectual predecessor, Auftragstaktik,1 a Prusso-German command philosophy that emphasizes decentralization, commander’s intent, and low-level initiative.2 These critics maintain that the Army must decentralize command as much as possible in order to realize the Auftragstaktik ideal.
This article sets out to show that the argument for hyper-decentralized command is flawed and that the concept itself is dangerous. The case for hyper-decentralization relies on a misinterpretation of Auftragstaktik, which underappreciates the role of planning and coordinating in Prusso-German warfighting. Moreover, decentralizing as much as possible is no guarantee of command effectiveness and is often harmful. This is not to say, however, that the current approach is effective. Army doctrine advises commanders to “balance” centralization and decentralization. This static approach fails to account for the dynamic nature of operational context. It also frequently results in overly centralized control because many Army commanders lack trust in subordinates, are uncomfortable with uncertainty, and are risk-averse.
Ultimately, mission command must enable forces to win by bridging the gap between doctrine and operational context. It must resolve the inherent tension between centralization and decentralization. Mission command must allow forces to mass combat power on decisive points while remaining adaptable to emergent opportunities and threats. Perhaps most important, it must enable the commander to operate in diverse, dynamic, and violently entropic operational contexts. An iterative approach to mission command is necessary to satisfy these requirements. An iterative approach would allow the commander to move continually between centralization and decentralization based on the demands of the operational context. By iterating continuously through a cycle of four activities—synchronization, dissemination, initiative, and reporting—Army commanders would be able to continuously adjust to the demands of the operational contexts within which their formations must fight.
Auftragstaktik and Moltke’s Dialectic
Born in the aftermath of the Napoleonic Wars and rooted in the theories of Carl von Clausewitz, the philosophy of Auftragstaktik was an exceptionally effective tactical innovation. One factor that made Auftragstaktik successful was its emphasis on lowering decision thresholds. By allowing company- and field-grade leaders to act without first seeking permission, the Prussians/Germans increased their tactical decision cycle speeds. In World War II, the German Wehrmacht gave a spectacular demonstration of Auftragstaktik’s tactical potency. The Germans combined Auftragstaktik with well-trained soldiers, aggression, and mechanized formations. The Wehrmacht penetrated, exploited, encircled, and collapsed its hapless opponents with ruthless efficiency.
The U.S. Army explicitly modeled its mission command doctrine on Auftragstaktik for good reason.3 An unfortunate side effect of this linkage is that many Service leaders evaluate mission command vis-à-vis Auftragstaktik rather than on its own terms. They argue that mission command falls short because it fails to live up to the Prusso-German ideal. These criticisms follow a predictable script. They begin by claiming the Army’s adoption of mission command is deficient. Next is a brief history of the Prusso-German way of warfighting that characterizes Auftragstaktik as a completely decentralized command philosophy. Critics then contrast the ostensibly decentralized, improvisational character of Auftragstaktik with the Army’s centralized, methodical approach. Finally, the proposed fix is hyper-decentralization—lowering decision thresholds as much as possible—to bring mission command in line with what critics imagine Auftragstaktik to be. The problem with this argument is that it relies on a flawed interpretation that equates Auftragstaktik with decentralization. While decentralization was an important part of the Prusso-German way of warfighting, it was not the sole factor that made Auftragstaktik effective.
Helmuth von Moltke the Elder is widely credited with institutionalizing Auftragstaktik in the Prussian/German army. His famous dictum that “no plan of operations extends with any certainty beyond the first contact with the main hostile force” is a favorite among mission command critics.4 However, Moltke’s views on command were more nuanced than his famous quotation suggests. For example, he observed that “it is always a serious matter to abandon, without the most pressing necessity, a once settled and well-devised plan for a new and unprepared scheme.”5 Moltke resolves the apparent conflict between this notion and his more famous dictum by acknowledging the dialectical interaction between planning and reality:
[S]trategy affords the tactics the means for fighting and the probability of winning by the direction of armies to their meeting place of combat. On the other hand, strategy appropriates the success of every engagement and builds upon it. The demands of strategy grow silent in the face of a tactical victory and adapt themselves to the newly created situation.6
For Moltke, higher level planning sets the conditions for lower level actions by creating favorable conditions for those actions. Upon execution, however, the results of lower level actions drive subsequent higher level planning. Though Moltke was writing about the interaction between the levels of war, the dialectic can also be seen in German tactical and operational warfare. Planning drives action, the results of action drive subsequent planning, and the cycle continues.
The Battle of Sedan is a characteristic example of Moltke’s dialectic at the tactical level. In May 1940, the German XIX Panzer Corps—consisting of the 1st, 2nd, and 10th Panzer divisions and led by the legendary Heinz Guderian—spearheaded the advance through the Ardennes. Knowing they would have to cross the River Meuse at Sedan, Guderian’s corps had planned and rehearsed crossing operations extensively before the campaign. Upon arriving at the Meuse on May 12, Guderian’s chief of staff wrote and issued a detailed operations order to synchronize crossing operations. The Panzer divisions did the same. The 1st Panzer Division order, for example, included a fires synchronization matrix, a centralized coordination tool that critics would view as anathema to Auftragstaktik.7
Despite being well planned, the crossing was only partially successful. Guderian’s three Panzer divisions began crossing at three bridgeheads during the afternoon of May 13. At the center bridgehead, 1st Panzer had good success and penetrated several kilometers into the French rear. On the flanks, however, the defending French 55th Infantry Division checked the 2nd and 10th Panzer attacks. That night, 1st Panzer commander Friedrich Kirchner pressed his attack even further. Though he had no orders to do so, Kirchner’s aggressive actions were entirely within Guderian’s intent that “once armoured formations are out on the loose they must be given the green light to the very end of the road.”8 But Kirchner’s thrust had placed 1st Panzer in a vulnerable position. Lack of progress on the flanks left 1st Panzer occupying a narrow salient with little more than an infantry brigade and no armor.9
The French, meanwhile, had spent the night reorganizing from their initial setback. By the morning of May 14, they were ready to counterattack with a combined tank and infantry task force. Guderian himself had crossed the river and was forward with 1st Panzer when German reconnaissance reported the massing French tanks. While Kirchner prepared to meet the French assault, Guderian raced back to the bridgehead and directed his staff to rapidly move 2nd Panzer Regiment’s tanks across the river to support 1st Panzer. Guderian’s speedy reorganization succeeded; the German tanks narrowly beat the French to a key ridge near the town of Bulson, and the high ground proved decisive terrain from which the Germans were able to repel the French counterattack.10
Guderian’s victory at Sedan was as much a result of planning, preparation, and coordination as it was of improvisation and initiative. Detailed planning and rehearsals set the conditions for the river crossing. However, uneven success during the initial crossings resulted in a substantially different situation than Guderian’s initial plan had envisioned. Still, Guderian and his staff were able to rapidly adapt to the changed situation and coordinate the necessary changes to deal with it effectively. Those who advocate for hyper-decentralized command too often ignore the centralized aspects that made the German approach work at Sedan and elsewhere. They herald the aggression and initiative demonstrated by Kirchner but minimize or ignore the planning and rehearsals that made the crossing possible in the first place. Ignored too is the hasty coordination to get armor support forward, which saved Kirchner’s aggressive penetration from being a crippling defeat.
The Dangers of Hyper-Decentralization
The idea that Auftragstaktik is a hyper-decentralized command philosophy persists despite contrary evidence.11 Many Army officers have come to believe that decentralization is the most important tenet of mission command. For example, one Army major writes that mission command is “the practice of decentralizing decision-making and authority down to the lowest possible echelon.”12 This obsession with decentralization is not only ahistorical but also potentially dangerous. There are axiomatic reasons to be wary of hyper-decentralization.
First, decentralization is not inherently advantageous. It is true that in many cases, lower decision thresholds are necessary for operational effectiveness.13 At the extreme, however, a completely decentralized force is little more than an unruly mob. Beyond a certain point, more decentralization impedes operational effectiveness rather than enables it. Second, the operational context—the mission, the enemy, and the environment within which formations fight—is a critical factor in determining how a commander should organize command. Decentralized command is not desirable or effective in every operational context.14
The Israeli experiences in 1956 and 1967 illustrate the limits of decentralization. In the 1950s, the Israel Defense Forces (IDF) adopted German tactical doctrine with the aim of fighting a maneuver war against potential aggressors.15 A rapid and decisive blitzkrieg campaign was an ideal solution to Israel’s dual problems of being surrounded by enemies and lacking the depth necessary for a strategic defense. The Israelis decentralized command even more than the Germans, and this hyper-decentralized philosophy was tested in the 1956 Suez Crisis. IDF maneuver brigades operated nearly independently from one another with little more than mission orders and commander’s intent. The results, however, were middling. While some brigades were successful, others were not. Brigades did not mutually support each other, and fratricide was rampant. Although the IDF prevailed, Israeli soldiers paid in blood for the lack of coordination.16
After the war, IDF commanders decided that brigades had been given too much independence. The Israelis subsequently revamped their command philosophy by increasing centralization to coordinate operations more effectively. The IDF implemented this new approach in the 1967 Six-Day War. This time, division-level commanders ensured brigades were mutually supported, and corps-level commanders synchronized actions among divisions. The results were nothing short of spectacular.17 IDF commanders demonstrated the value of being able to dynamically centralize or decentralize command based on the operational context. In the Sinai, for instance, Brigadier General Israel Tal’s division conducted an armored penetration and exploitation along the Mediterranean coast toward El Arish. Faulty intelligence and unexpected events made Tal’s fight a series of improvisations that in the end only vaguely resembled his original plan. Major-General Ariel Sharon’s division, on the other hand, conducted a tightly controlled set-piece attack on the Egyptian strongpoint at Umm-Qatef. Both commanders were successful because they adapted the IDF command philosophy to suit their unique operational contexts.18
The IDF experience demonstrates both the limits of decentralization and the importance of considering the operational context. The principal shortcoming of hyper-decentralized command is that it drives commanders to decentralize as much as possible in all contexts. Yet not all operational contexts demand decentralization. This argument is elaborated below, but it bears mentioning the German case at Kursk (1943), where decentralization and individual initiative mattered little in the teeth of a well-planned and prepared Soviet defense. Commanders must consider the operational demands of a given situation when determining where to place decision thresholds.
Army Doctrine: A Tale of Two Traditions
Command is a means to an end, which is to win. The character of command is therefore strongly influenced by the methods by which winning is achieved—that is, a force’s fighting doctrine. A command philosophy must bridge the gap between how a commander wants to fight (doctrine) and how the force must fight given the operational context. The Army’s fighting doctrine presents a unique challenge because it is an amalgamation of two traditions—the Jominian and the Clausewitzian. Each tradition views winning through a different conceptual lens. This dichotomy leads to different command philosophies and an inherent tension in how Army doctrine approaches mission command.
The Jominian tradition subscribes to the “one great principle” of war—to throw the mass of one’s force on the decisive point. The Jominian imperative to “arrange these masses . . . at the proper time and with energy” requires synchronization, centralized control, and unity of effort.19 For Jominians, command primarily coordinates the application of combat power. The centralized control required to do so, however, risks sacrificing adaptability. Moltke’s dictum underscores the idea that the chaos of battle will eventually render preplanned controls obsolete, at which point they merely limit freedom of action. Lower level commanders are unable to adapt to changed conditions without permission, and enemies can exploit this inaction. Thus, the principal problem for Jominian command is how to coordinate the application of combat power at decisive points without sacrificing adaptability.
The Jominian tradition’s answer to the adaptability problem has historically been a technologically centered effort to push better situational awareness up the chain of command. The idea is that technologically enabled higher level commanders can make decisions with the big picture in mind but at the speed of adaptability. These efforts, however, have largely proved fruitless and even counterproductive.20 Technology has in some ways inhibited rather than enabled command by creating enormous information appetites that lower level commanders must continually feed.21
The second approach is the Clausewitzian tradition. Clausewitzians are skeptical of coordination because combat is inherently uncertain, and reality is unlikely to unfold according to any plan.22 For Clausewitzians, improvisation is necessary to cope with unanticipated conditions, and therefore adaptability should be command’s central concern.23 Since lower level commanders will be the first to recognize the need to adapt, higher level commanders enable adaptability by allowing their subordinates to act independently. The risk is that lower level commanders may fracture the higher commander’s unity of effort. Each lower level commander may act correctly according to his or her understanding of local problems but without appreciating how this might affect the higher level situation. Divergent actions may render disparate units unable to provide mutual support and make them vulnerable to defeat in detail. The Clausewitzian approach, therefore, has the opposite problem of the Jominian approach: how to adapt to the uncertainty of combat while retaining the ability to coordinate the application of combat power at decisive points.
The Clausewitzian tradition’s answer to its coordination problem is implicit control enabled by shared understanding and commander’s intent. The idea is that higher and lower level commanders come to a shared understanding of what needs to be done based on the higher commander’s intent, then use this understanding as a conceptual handrail when circumstances change. This is said to enable “decentralized and distributed formations to perform as if they were centrally coordinated.”24
The problem with implicit control is that it degrades over time. Commanders formulate their intent and build a common understanding with subordinates based on a shared visualization of the future situation. This estimate, however, is no more likely to be accurate than the one that underpins Jominian controls. Combat is violently entropic; it relentlessly moves toward disorder and chaos. The commander’s intent and shared understanding may initially synchronize action. But as disorder increases, reality diverges from the shared visualization. The implicit synchronization of otherwise disconnected actions erodes and eventually ceases. Unless commanders and subordinates periodically refresh their shared understanding, they will eventually cease to be on the same conceptual page. Implicit controls have the same limitation as the explicit controls favored by the Jominians; they have a short half-life in combat. In other words, the only thing that will make formations perform “as if they were centrally coordinated” is to centrally coordinate them.
Doctrinal and De Facto Shortcomings
The Army’s competing concepts of command create a paradox: neither centralization nor decentralization is independently sufficient, yet both are necessary. The Army’s command philosophy must provide enough control to synchronize combat power at decisive points, but at the same time be decentralized enough to deal with the uncertainty and chaos of battle.
Unfortunately, Army doctrine fails to resolve this tension in both theory and practice. It advises commanders to “use the guiding principles of mission command to balance the art of command with the science of control.”25 This “balancing” approach imagines a continuum of command with decentralization at one extreme and centralization at the other. The commander adjusts the level of control up or down based on the situation.26
In theory, the balancing approach is a modest (if still flawed) improvement over hyper-decentralization. It at least directs the commander to consider operational context to determine the degree of control necessary. Its weakness, however, is that it is missing the entire latter half of Moltke’s dialectic. It describes how control limits adaptability but fails to describe how adaptability must also shape control. In practice, the balancing approach frequently results in excessive control. Army commanders tend to overcontrol because they either lack trust in subordinates, are risk-averse, or both.
Adjusting the level of control based on trust (or lack thereof) is the same inward orientation error seen in hyper-decentralization. That is, it structures command based on internal concerns rather than operational demands. Moreover, it makes little sense. The purpose of decentralization is to increase adaptability in response to uncertainty. If we accept that war is inherently chaotic and uncertain, then we must also accept that some decentralization is required to win. Therefore, trust is required to win. Commanders who do not trust subordinates enough to decentralize are at a severe disadvantage. Lack of trust cannot be mitigated with additional controls.
While tightening control based on risk is a sound practice, too often commanders impose excessive controls because they are either risk-averse or because they mistake risk for uncertainty. Risk is a function of the probability that an event will happen and the consequences if it does. For example, a commander may judge that a subordinate unit that advances beyond a certain point may be vulnerable to counterattack and beyond the range of mutual support. If such a scenario is likely to happen (probability) and could result in that unit’s destruction (consequences), then a control (such as a limit of advance) is prudent.
Nevertheless, the urge to overcontrol is strong. One reason is risk aversion.27 Research suggests Army leaders are particularly risk-averse. Officers selected to attend the Army War College score lower than the general population on openness to experience using the Five Factor Model personality test, and those selected for brigade command score even lower.28 Research on personality and risk-taking shows that openness to experience correlates with less risk-taking behavior.29
Commanders also overcontrol because they are uncomfortable with uncertainty. Risk is not necessarily higher under conditions of uncertainty, but commanders often perceive it to be because they lack the information necessary to estimate risk. Many commanders instinctively tighten controls, but this is precisely the opposite of what they should do. Uncertainty increases the possibility of unforeseen threats and opportunities. Lower decision thresholds enable lower level leaders to respond quickly to these emergent demands, while more centralized control limits their ability to do so.
Operational Context and Iterative Command
The idea that the Army’s command philosophy must bridge the gap between fighting doctrine and operational context creates two challenges. First, the philosophy must resolve the tension between the Jominian and Clausewitzian imperatives. Second, it must do so in whatever operational context Army forces must fight. Adapting to the operational context is the more formidable task. While Army fighting doctrine is relatively stable, operational context is nearly the opposite. Operational context is diverse, dynamic, and violently entropic. Each operational situation is unique, constantly evolving, and continually moving toward disorder.
Neither hyper-decentralization nor the balancing approach has the means to address these challenges. Hyper-decentralization is explicitly biased toward the Clausewitzian imperative, and as a result it fails to account for synchronization and mass. It is inwardly oriented on maximum decentralization rather than outwardly oriented on the demands of the operational context. The balancing approach is likewise inadequate. It does not account for the dialectic between adaptability and control and in practice frequently results in overly centralized control, which is no better than hyper-decentralization.
The solution to these problems is an iterative approach to mission command. This approach enables the commander to move continually between centralization and decentralization based on the demands of the operational context. The iterative approach is a continuously repeating cycle of four activities: synchronization, dissemination, initiative, and reporting.
Synchronization is the process of implementing the minimum necessary control to mass combat power at decisive points and maintain mutual support while preserving as much freedom as possible for subordinates. Importantly, minimum necessary control is not the same as minimal control. The operational context drives how much control is minimally necessary. In some cases—such as a combined arms breach or an air assault—the minimum controls will be necessarily stringent. In all cases, however, the commander must avoid overcontrolling and should decentralize as quickly as the need to control diminishes.
The second activity, dissemination, involves the higher commander communicating his or her intent and mission orders to subordinates. Commander’s intent and mission orders should be short, easily understood, and contain the minimum necessary control measures to enable synchronization. When disseminating orders, commanders should not rely exclusively on voice and data communications. The best commanders move around the battlefield and communicate their intent to subordinates face-to-face.
The third activity is initiative. Commanders empower subordinates to take the initiative to respond to emergent conditions. Subordinates seize fleeting opportunities and mitigate emergent threats immediately and effectively when they do not have to seek permission or await directions from their higher command. Initiative allows units to adapt to uncertainty and change.
Finally, reporting means subordinates communicate information rapidly and accurately to the higher commander. Reporting mitigates the risk of units acting on their own initiative. By communicating and reporting, subordinates allow the commander to update his or her visualization of the battle and determine what additional decisions are required to maintain mutual support and unity of effort across the formation. The commander relies on this updated visualization to resynchronize the force, and the iterative cycle begins again. Each cycle is an opportunity for the commander to adjust the level of control. As the operational context changes, the commander can continually adjust his or her command approach to compensate.
Iterative command is in some ways already “out there” in the force. Commanders already synchronize, disseminate, take initiative, and report. The real change is the mental shift required from both junior and senior leaders to make iterative command work. Junior leaders often believe mission command means no higher level control and perceive reporting requirements as micromanagement. These misconceptions must be dispelled. Mission command is not equivalent to minimal control; some situations require more control and some less. Likewise, reporting requirements are not micromanagement. Reporting is necessary for the higher commander to create an accurate visualization, resynchronize the force, and maintain unity of effort.
Senior commanders must also change how they think about mission command. They must accept that mission command is both top-down and bottom-up. It is top-down in that higher commanders synchronize the activities of subordinate units. However, it is bottom-up in that subordinate initiative drives resynchronization. The higher commander must be responsive to and support lower level initiative. In this way, lower level initiative “pulls” higher level synchronization rather than the opposite and more conventional “push” from higher to lower. This arrangement may feel alien to many senior commanders who prefer the more conventional “higher says, lower does” hierarchical approach. However, allowing initiative to drive synchronization is required for mission command to succeed.
Calls for the Army to adopt hyper-decentralized command are misplaced. The case for hyper-decentralized command rests on a misinterpretation of Auftragstaktik, which underestimates the importance of planning and control in the Prusso-German approach while overestimating the importance of improvisation and low-level initiative. Moreover, hyper-decentralization provides no means to coordinate mutual support among units or mass combat power at decisive points. It relies on questionable assumptions regarding the degree to which the commander’s intent and shared understanding can coordinate actions.
The Army’s implementation of mission command is also problematic. Army doctrine’s balancing approach fails to resolve the inherent tension between centralization and decentralization and often results in overly centralized control. But the solution to this problem is not hyper-decentralization. Though Auftragstaktik has some qualities worth emulating, it should not be the ideal for which the Army strives. The degree to which a command system mirrors that of the Prussians or Germans is less important than its usefulness in enabling Army forces to win.
Instead, the Army should adopt an iterative approach to mission command that allows the commander to empower subordinates to take disciplined initiative while retaining the ability to coordinate and mass combat power. These opposing but necessary imperatives cannot be achieved through hyper-decentralization. Nor can they be achieved through the balancing approach found in doctrine. An iterative approach based on a continual cycle of synchronization, dissemination, initiative, and reporting is the most promising way ahead for mission command. JFQ
1 Tom Guthrie, “Mission Command: Do We Have the Stomach for What Is Really Required?” Army Magazine, June 2012, available at <www.ausa.org/sites/default/files/FC_Guthrie_0612.pdf>; Donald Vandergriff and Stephen Webber, eds., Mission Command: The Who, What, Where, When and Why; An Anthology (Scotts Valley, CA: CreateSpace, 2017); Donald Vandergriff, “How the Germans Defined Auftragstaktik: What Mission Command Is—AND—Is Not,” Small Wars Journal (June 2018), available at <http://smallwarsjournal.com/jrnl/art/how-germans-defined-auftragstaktik-what-mission-command-and-not>; Eitan Shamir, “The Long and Winding Road: The U.S. Army Managerial Approach to Command and the Adoption of Mission Command (Auftragstaktik),” Journal of Strategic Studies 33, no. 5 (October 2010), 645–672, available at <https://doi.org/10.1080/01402390.2010.498244>.
2 Werner Widder, “Auftragstaktik and Innere Führung: Trademarks of German Leadership,” Military Review 82, no. 5 (October 2002), 3–10.
3 Army Doctrine Reference Publication 6-0, Mission Command (Washington, DC: Headquarters Department of the Army, 2014), change 2, v.
4 Daniel J. Hughes, Moltke on the Art of War: Selected Writings (New York: Presidio Press, 1995).
5 Helmuth von Moltke, The Franco-German War of 1870–71, trans. Clara Bell and Henry W. Fischer (New York: Harper & Brothers, 1901), 70–71, available at <https://archive.org/details/francogermanwaro02molt>.
6 Hughes, Moltke on the Art of War.
7 Heinz Guderian, Panzer Leader, trans. Constantine Fitzgibbon (Cambridge, MA: Da Capo Press, 2001), 89–109, 480–486.
8 Ibid., 98.
9 Ibid., 104–105.
10 Karl-Heinz Frieser, The Blitzkrieg Legend: The 1940 Campaign in the West (Annapolis, MD: Naval Institute Press, 2013), 175–190.
11 Samuel J. Newland, “The Germans and the Exercise of Military Power,” Parameters 36, no. 3 (2006), 120–123; Gerhard P. Gross, The Myth and Reality of German Warfare: Operational Thinking from Moltke the Elder to Heusinger (Lexington: University Press of Kentucky, 2016).
12 Thomas A. Rebuck, “Mission Command and Mental Block: Why the Army Won’t Adopt a True Mission-Command Philosophy,” Armor, October–December 2015, 51, available at <www.benning.army.mil/armor/eARMOR/content/issues/2015/OCT_DEC/Rebuck.pdf>.
13 Martin van Creveld, Command in War (Cambridge, MA: Harvard University Press, 1987), 270.
14 Andrew Hill and Heath Niemi, “The Trouble with Mission Command: Flexive Command and the Future of Command and Control,” Joint Force Quarterly 86 (3rd Quarter 2017), 94.
15 Gershon Hacohen, The Six-Day War Was a One-Time Event, BESA Center Perspectives No. 487 (Ramat Gan, Israel: The Begin-Sadat Center for Strategic Studies, 2017), available at <www.infosperber.ch/data/attachements/BESA_Six-Day-War-One-Time-Event.pdf>.
16 Van Creveld, Command in War, 196–197.
17 Ibid., 199.
18 Eric M. Hammel, Six Days in June: How Israel Won the 1967 Arab-Israeli War (New York: Charles Scribner’s Sons, 1992), 172–218, 228–242.
19 Baron Antoine-Henri De Jomini, The Art of War, trans. G.H. Mendell and W.P. Craighill (Philadelphia: J.B. Lippincott & Co., 1862), 70.
20 Van Creveld, Command in War, 265–268.
21 Leonard Wong and Stephen J. Gerras, Lying to Ourselves: Dishonesty in the Army Profession (Carlisle, PA: U.S. Army War College Press, February 2015), 15–16.
22 Carl von Clausewitz, On War, ed. and trans. Michael E. Howard and Peter Paret (Princeton: Princeton University Press, 1989).
23 I am not arguing that these are Jomini’s or Clausewitz’s command philosophies, only that American interpretations of their respective theories of war create these command imperatives. Although American interpretations of Jomini’s and Clausewitz’s ideas frequently put them at odds, their theories are compatible in many ways. See Christopher Bassford, Jomini and Clausewitz: Their Interaction, Clausewitz.com, 1993, available at <www.clausewitz.com/readings/Bassford/Jomini/JOMINIX.htm>.
24 Martin E. Dempsey, Mission Command White Paper (Washington, DC: The Joint Staff, 2012), 4, available at <www.jcs.mil/Portals/36/Documents/Publications/missioncommandwhitepaper2012.pdf>.
25 Field Manual (FM) 6-0, Commander and Staff Organization and Operations (Washington, DC: Headquarters Department of the Army, 2016), change 2, 1–2.
26 Ibid., 2–15.
27 Ben Summers, “Slow, Inflexible, and Micromanaged: The Problems of a Military That Overstates Risk,” Modern War Institute, May 9, 2017, available at <https://mwi.usma.edu/slow-inflexible-micromanaged-problems-military-overstates-risk/>; David Barno and Nora Bensahel, The Future of the Army: Today, Tomorrow, and the Day After Tomorrow (Washington, DC: The Atlantic Council, September 20, 2016), 35, available at <www.atlanticcouncil.org/wp-content/uploads/2016/09/Future_of_the_Army_web_0921.pdf>.
28 Stephen J. Gerras and Leonard Wong, “Moving Beyond the MBTI: The Big Five and Leader Development,” Military Review 96, no. 2 (March–April 2016), 54–57, available at <www.armyupress.army.mil/Portals/7/military-review/Archives/English/MilitaryReview_20160430_art012.pdf>.
29 Nigel Nicholson et al., “Personality and Domain-Specific Risk Taking,” Journal of Risk Research 8, no. 2 (March 2005), 157–176.