Tag Archives: Tactics

Learning War and The Evolution of U.S. Navy Fighting Doctrine with Author Trent Hone

By Christopher Nelson

Author Trent Hone joins us today to talk about his new book Learning War: The Evolution of Fighting Doctrine in the U.S. Navy, 1898-1945. This is a great book. And as others have noted, it’s a fine compliment to John Kuehn’s work on the Navy General Staff, Scott Mobley’s book Progressives in Navy Blue, and I would add, Albert Nofi’s To Train The Fleet For War: The U.S. Navy Fleet Problems, 1923-1940.

We talk about everything from Admiral Frank “Friday” Fletcher to “safe-to-fail” systems vs. “fail-safe” systems. And stick around to the end. Trent Hone offers some advice to the CNO on how we can build a better learning organization.

Nelson: For the readers, could you tell us briefly what your book is about?

Hone: My book investigates how the U.S. Navy of the early twentieth century learned to innovate. I explore how the Navy invented new technologies, created new tactics, and found ways to rapidly evolve its combat doctrine based on peacetime exercises and wartime experience. Today, we would describe the Navy of that era as a “learning organization.” I explain what that means and describe the mechanisms the Navy used to effectively learn and innovate. I believe there are lessons from that time that are very relevant for today’s organizations, both military and civilian.

Nelson: Why did you want to write this book?

Hone: I’ve been interested in naval tactics for a long time. I remember reading Wayne Hughes’s Fleet Tactics when it first came out in the 1980s and being fascinated (It’s a great book now on its third edition). In the 1990s, I decided to explore the Navy’s surface warfare tactics before and during World War II. I wanted to know what Admiral Husband E. Kimmel might have done if Pearl Harbor hadn’t been attacked. That research led to a series of articles on the development of Navy tactics—including a prize-winning one in the Naval War College Reviewand, ultimately, began to overlap with other work I was doing. 

I started my career as a software engineer. As I assumed positions of greater responsibility, what became most interesting to me was not the development of the software, but how teams organized to create software and do innovative work. I studied various techniques and methods to improve the teams I supervised and eventually transitioned into advising and coaching organizations to help them get better at learning and innovating. 

As I continued looking at the evolution of the Navy’s tactical doctrine in the early twentieth century, I saw patterns that resonated with today’s most-effective learning techniques. The language was quite different, and the specific processes were different, but some of the underlying principles were remarkably similar. I realized it was a story that had to be told. I describe an arc of innovative creativity that stretches back decades by charting the evolution of surface warfare tactics.

Nelson: Early in the book you talk about “fail-safe” systems and “safe to fail” systems. The latter, you say, are best for a culture that encourages innovation. With this in mind, what would you say Rickover’s submarine culture consisted of? Is he a rare exception in the case of a system that is “fail-safe” yet innovative?

Hone: I’m glad you brought this up. Alicia Juarrero’s term “safe to fail” gives us a new way to think about failure modes and how to account for them. The key difference between the two is that with “fail-safe” we attempt to anticipate possible failure modes and design ways to mitigate them. With “safe to fail,” we recognize unanticipated failure modes will occur and organize to ensure survival when they do. This has relevance to organizations because when we want to learn and innovate, we are going to fail. A “safe to fail” organization finds ways to explore new ideas and experiment with them without endangering its long-term survival. The Navy was good at that in the early twentieth century. 

I’m less familiar with Rickover’s time, but from what I understand, it would be inaccurate to describe the culture he developed as primarily “fail-safe.” Certainly, it used procedures with rigidly prescribed steps in order to prevent known failures, so in that sense it was “fail-safe.” However, he recognized that unanticipated failure modes can and will occur. Defined procedures are inadequate to account for these circumstances. Instead, it’s essential to rely on the collective skill and experience of people, so the culture integrated crewmembers together. Layers of human observation and experience became the means to identify, anticipate, and address unforeseen circumstances. In that sense, the culture has a “safe to fail” component. Things will go wrong; people will make mistakes. But trust and experience become the means to identify and resolve them. 

As it turns out, that’s the most effective way to deal with problems in complex environments. Standard procedures and automated routines free our mental capacity so that when unforeseen circumstances arise, we can quickly identify and address them. That’s what made the Combat Information Center (CIC) and its successors effective: the artful integration of standard processes, technology, and human judgment. I worry that with the increasing emphasis on automated systems, we might be taking the talents of our people too far out of the loop. There’s no substitute for human experience and skill when the unanticipated occurs. 

Nelson: What is the “edge of chaos” and why does it matter to any organization that is trying to be innovative?

Hone: The concept of the “edge of chaos” is easily misunderstood, so I’ll try to explain it succinctly. In any complex system—like a corporation or a military service—there are processes, procedures, and rules. In the language of complexity, these are called “constraints.” They channel and limit behavior. When constraints are restrictive, they inhibit the ability of people to experiment and try something new. Obviously, that’s a problem if you want to innovate. But the other end of the spectrum is problematic also. If constraints are too loose, there’s no coherence; it becomes difficult to assign cause and effect or make sense of an experiment. The “edge of chaos” is located between these two extremes. It is a space where constraints are sufficiently loose to allow room to explore new ideas and concepts but also rigid enough to focus that exploration and provide feedback on its effectiveness. 

Many of us intuitively understand this from our own experience. Software teams, for example, are most innovative (and generally most effective) when they’re given a clear objective and the creative freedom to determine how best to accomplish it. The objective serves as a constraint and focuses their energy. They use their initiative to explore several potential solutions, often arriving at the best combination of technologies that addresses the need. That’s why there’s been such an emphasis on moving away from rigidly detailed requirements documents; they overly constrain teams and limit their creativity. The parallels to military command, and the importance of well-written orders that foster the initiative of subordinates, are obvious. 

Nelson: What was the importance of the 1921 Destroyer Instructions?

Hone: The Atlantic Fleet’s 1921 Destroyer Instructions were important for two reasons. It was the first Navy doctrinal manual produced by a deliberately created system of learning. Immediately after World War I, the Navy was transitioning back to peacetime. Many valuable lessons had been learned during the war and officers set out to capture them. Two “colleges” were established, one in the Atlantic Fleet and another in the Pacific Fleet. They combined exercises at sea, wargames ashore, and experience from the recent war to devise new approaches. A regular correspondence was maintained between these two fleet colleges and the Naval War College. The result of their collective learning was incorporated into the Destroyer Instructions. 

The Destroyer Instructions were also important because they assumed individual commands—each destroyer squadron—would develop their own specific doctrines that reflected the strength of their ships and men. The Instructions were deliberately written to foster creativity within subordinate commands and avoid being overly prescriptive. The War Instructions of 1923 took the same approach, so Navy officers spent the interwar period exploring a variety of options for how to coordinate and employ their forces, leading to new and innovative techniques.

Nelson: Who was Admiral Frank Friday Fletcher? What were his battle instructions? And why are they an important milestone in naval history?

Hone: Frank Friday Fletcher led the intervention at Veracruz, Mexico, in April 1914 and was awarded the Medal of Honor for his conduct. In September 1914, he became commander of the Atlantic Fleet, which contained the Navy’s most modern ships. The Atlantic Fleet had been regularly conducting exercises to work out how best to operate in battle, and Fletcher continued that practice. By May 1916, he and his staff had gained enough experience to issue a set of Battle Instructions. 

Admiral Frank Friday Fletcher.

Fletcher’s Instructions marked a departure from previous approaches. He assumed battle was fundamentally uncertain and that centralized control would likely be impossible; this led him to emphasize two things. The first was the use of a plan that would outline objectives for subordinates. Fletcher wanted to encourage their individual initiative and creativity without overly constraining them. Second, Fletcher stressed the coordinated use of all weapons. Previous battle plans had emphasized battleship gunnery. Fletcher recognized that other weapons were coming into their own, particularly destroyer torpedoes. He planned to use his destroyer squadrons very aggressively. These two concepts—the use of a plan and coordinated employment of all arms—remained central to Navy tactical doctrine through World War II.  

Nelson: I enjoyed your comment about “type commanders.” You note in your book that during World War II that minor actions were neglected.  This mattered. And type commanders were born in light of these shortcomings. What were these “minor actions” and how did the type commanders address them?

Hone: The Navy’s primary focus in the interwar period (1919-1939) was a trans-Pacific campaign. It was expected to culminate in a “major action”—a large fleet battle—somewhere in the central Pacific. Accordingly, most of the fleet-level tactical doctrine focused on “major action.” Tactics for “minor actions”—engagements between smaller task forces—were left to subordinate commanders. It was assumed that these lower-level commanders would have time to develop doctrines for their forces, and, during peacetime, this assumption was largely correct. 

However, there were shortcomings. This led to the introduction of the type commands in 1930.

Type commands became responsible for identifying and capturing new tactical approaches for each various type—destroyers, cruisers, battleships, etc.—and there is evidence that new approaches were more rapidly developed after that date. The real problem, though, was the assumption that subordinate commands would be able to develop specific doctrines for their forces. 

In 1942, that process fell apart during the battles off Guadalcanal. Ships and commanders moved about too rapidly to develop cohesion. “Scratch teams” were formed and they often performed poorly, as you might expect. The Pacific Fleet addressed the problem by applying some of the same techniques used for “major tactics” to “minor tactics” and leveraging the type commands to rapidly share and disseminate lessons. 

Nelson: During World War II, how did the Fleet quickly inform commanders with updated doctrine? This is a problem throughout history, is it not? We make some assessments on what will or will not work in war, and inevitably we will be surprised. What would you recommend to a staff today on how to prepare for such things?

Hone: I love this question because when I first started my research decades ago, I thought that manuals—published doctrinal materials—would be the key to understanding tactical doctrine. I learned very quickly that’s not the case. Doctrine is a set of assumptions and mental models. The documentation provides a backdrop, but what really matters is how individuals think about problems and work together. During World War II, the Navy effectively used personal connections, like in-person conversations and conferences, to rapidly share and disseminate new ideas. There were formal means to do this (like Joseph C. Wylie being brought back from the South Pacific to help develop the CIC) but informal mechanisms were at least as important. Published doctrine tended to lag behind the information shared through these informal networks.

USS SAN FRANCISCO (CA-38) At the Mare Island Navy Yard, 20 May 1942. (Photo via Naval History and Heritage Command)

If I were making recommendations, I’d stress the importance of informal mechanisms. Staffs can easily create mountains of briefings and other documentation. What’s more difficult is creating an environment where subordinates can readily exchange information, learn together, and build on the knowledge of their colleagues. I think a staff should actively work on enabling that. It’s not just about creating space and time; it’s about introducing the appropriate constraints to enable creativity to flourish. Then, once that is in place, the staff needs to keep tabs on what’s happening. New, more effective ideas will arise. When they do, the staff needs to act quickly to exploit them and make them available to the entire command. 

Nelson: How does the size of a navy – the number of ships and sailors – affect innovation? Quick growth, during World War II, for example, and steep reductions – ship numbers from the 80s to today for instance, do these affect innovation in different ways? How?

Hone: I think both offer serious challenges. The rapid growth in World War II made it very difficult to maintain the effective culture the Navy had nurtured during the early twentieth century. Rapid “scaling” (as we call it in the software world) tends to increase centralization, reduce flexibility, and inhibit innovation. That happened to the Navy as it grew during the war. 

The challenge I see with steep reductions is overburdening. Organizations often reduce their size without an equivalent reduction in their commitments. This leads to overwork: people become spread too thin; maintenance gets delayed; and equipment is overutilized. Individuals may still be able to sustain the pace of operations, but they frequently lose the ability to experiment with new ideas. Innovation slows as a result. When commitments are reduced along with reductions in size—as with the Navy after World War I—this can be avoided. 

Nelson: Trent, to close, if you had ten minutes with the Chief of Naval Operations and he asked you what he needed to do to create a learning organization – what would you say?

Hone: I had about thirty seconds with Admiral Richardson last year when he presented me with the second-place award for his Naval History Essay Contest, and in those thirty seconds, I encouraged him to read my book. If I had ten minutes, I’d urge him to introduce a set of integrated feedback loops that couple regular experimentation regarding the nature of future war (tactics, technology, etc.) and OPNAV’s programming process. The goals would be twofold. First, officers need to be encouraged to regularly experiment to vary their tactical approaches to discover new, more effective techniques. They need to become accustomed to adjusting to unanticipated circumstances and leveraging the creativity of their commands. Second, the lessons from their experimentation need to revise and guide the Navy’s program so that force structure and procurement reflect—and ultimately anticipate—the new learning. 

We’re all familiar with the interwar Fleet Problems. What made them really powerful—what allowed them to transform the Navy—was the way they were integrated into the Navy’s planning and procurement processes. The second CNO, Admiral Robert E. Coontz, was primarily responsible for that. He created the feedback loops that allowed the Navy to not just experiment with new tactical doctrines, but to evolve force structure and war plans in light of emerging lessons. If Admiral Richardson wants “high-velocity learning,” if he wants to fully leverage the skills of the Navy’s officers, he needs to devise a set of similar mechanisms. Given the organizational changes since Coontz left office in 1923, a new set of structures and interfaces would have to be introduced. I have faith Admiral Richardson could do that, if he sets his mind to it. 

Trent Hone is an award-winning naval historian and a Managing Consultant with Excella in Arlington, VA. He is an expert on U.S. Navy tactics and doctrine. His article, “U.S. Navy Surface Battle Doctrine and Victory in the Pacific” was awarded the U.S. Naval War College’s Edward S. Miller Prize and the Naval History and Heritage Command’s Ernest M. Eller Prize. His essay, “Guadalcanal Proved Experimentation Works” earned second place in the 2017 Chief of Naval Operations Naval History Essay Contest. He regularly writes and speaks about organizational learning, doctrine, strategy, and how the three interrelate. His latest book, Learning War: The Evolution of Fighting Doctrine in the U.S. Navy, 1898–1945, was published by the U.S. Naval Institute in June 2018.

Christopher Nelson is a U.S. Naval Officer stationed at the U.S. Pacific Fleet Headquarters. He is a graduate of the U.S. Naval War College and the Maritime Advanced Warfighting School. He is a regular contributor to CIMSEC. The questions and views here are his own.

Featured Image: USS Indiana (BB-58) fires a salvo from her forward 16″/45 guns at the Kamaishi Plant of the Japan Iron Company, 250 miles north of Tokyo. 

The Surface Navy: Still in Search of Tactics

By Captain Christopher H. Johnson

A month before deployment, the captain of an Oliver Hazard Perry (FFG-7)-class frigate sits quietly in his cabin. With the long process of pre-deployment inspections over and the threatening waters of the Persian Gulf a few short weeks ahead, now, more than ever before, he considers his three line department heads in the context of their impending role as Tactical Action Officers (TAOs) for the ship when it arrives in the Northern Persian Gulf. To this point, these young officers have been measured by their ability to juggle priorities, pass inspections, sustain planned maintenance at acceptable accomplishment levels, keep the squadron staff happy, and perform a number of other administrative tasks. Now they must become tacticians, and a fleeting sense of despair crosses the captain’s mind.

He recalls when he was a lieutenant junior grade serving on a destroyer in the Gulf of Tonkin, and he remembers the officers who taught him. There were operators who could sense what was happening around them with a gut instinct that distinguished them as mariners and naval officers. For a moment, he thinks about his TAOs and realizes that they are different. Yes, the world was simpler when the most complicated weapon on board was a 5-inch/38-caliber gun, but despite new weapons of enormous capability and complexity, today’s officer is better at paperwork than he is at tactics and operations.

The captain also recalls a discouraging afternoon three months ago when the operations officer and three petty officers brought to his cabin every tactical memorandum, tactical note, and Naval Warfare Publication on the ship, as references for new battle orders. Surely, within the tactics library of his ship, there would be the pearls of wisdom he needed for operations in the Persian Gulf.

Instead, he found an endless succession of publications that often dealt with obscure tactical problems and were generally out-of-date, long-winded, rarely insightful, and almost always too complex. As the petty officers packed up the publications and departed, the captain wondered why, after all this effort in tactics, there was so much paper with so little knowledge to show for it.

Now, the same question haunts him again. “I must find a way to make these department heads into tacticians,” he says aloud. “But what are tactics, and how do I prepare a tactician?” His thoughts are interrupted by a knock on his door. “Sorry to bother you, Captain,” booms the executive officer, “but we’ve got to talk about Seaman Jackson and his family problems.”

This captain’s plight is not unusual, but it is dismaying. Where have tactics gone in the modern surface Navy? Perhaps officers are too focused on being managers and administrators, and maybe the emphasis on engineering has diverted them from tactical thinking. Maybe we have accepted the contention that, in an era of overwhelming technical complexity, everything must be reduced to a lifeless, static procedure to be understood. Whatever the cause, the loss of tactics – and the subsequent appearance of hundreds of publications which masquerade as tactics – is a problem that reaches the very heart of our profession. Tactics must be resurrected.

Brilliant success on the battlefield is the object of command as practiced by Spruance, Nimitz, and other great naval tacticians of the past. Such success is not simply the result of perfect methodology, but rather it is rooted in a hierarchy of preparation and thought. First, success requires knowledge of the technical environment in which naval operations take place. Second, it requires specific procedures to guide the operation of combat systems. Third, and most important, it requires tactics.

Tactics build on knowledge and procedure, but go far beyond either. Contrary to the common definition, tactics are not like check-off lists, diagrams, or procedural doctrine. Tactics are the educated process of thought by which a battlefield commander adapts procedure, knowledge, and insight to the situation at hand and molds a winning plan. Tactics, therefore, are characterized by responsive, analytical, and individualized solutions to real-life circumstances. Tactical ideas or procedures may be found in books, publications, or manuals, but tactics rely on ingenuity, instinct, and innovation. Tactics are never a single answer to a generic tactical problem; but a continuous effort to find the right way to undermine, exploit, and beat the enemy.

In the tactician’s mind, the heart of this tactics thought process is his continuous, individual, and deeply personal struggle with an assortment of intangible measurements, including his vision of the mission at hand, its bounds, rules of engagement, sequences, priorities, and urgencies; analysis of the critical capabilities and limitations of own force; experience, courage, and determination; his commitment to the safety of the ship and personnel; an evaluation of the enemy’s frame of mind, liabilities, strength, and mission; and an appreciation of the opportunities provided by geography, environment, or political conditions.

The process has an immediate and an ultimate product. The immediate object of tactics is a real-time vision, or sense of the tactical balance sheet. What are the key opportunities and critical liabilities inherent in the situation? Where are we strong, and where is the enemy weak? What actions will confuse the enemy? How can friendly forces further undermine enemy strength? How can the enemy’s confidence be shaken?

This analysis leads to the ultimate object of tactics: a course of action, springing from inspiration and evaluation of all factors, which will win with minimal cost. To win while taking few losses defines brilliant action and is the indisputable purpose of tactics, inherent in all the greatest naval victories in history. Our country wants us to act boldly and bring our sailors home safely. Sadly, the tactics underpinning this goal have come to be procedures for pitting one weapon against another, rather than a thought process for winning.

It is useful at this point to contrast the tactician with today’s officer who is more accustomed to the role of technician. Technicians live in a world of black and white, focusing exclusively on mechanics and measurements; they are often caught up in an engineering-oriented ethic which asserts that there is a single, discrete solution for every situation. To the technician, combat is a toe-to-toe struggle where the most perfectly designed and operated system wins. Conversely, the tactician sees this technical struggle as essential but subordinate to other vital issues. To him, the engagement is a series of chess moves where the best thinker, the most accomplished facilitator of quick, decisive, and perfectly timed action will win. To the technician, the victory at Midway was fortune; to the tactician, Midway was brilliant tactical instinct reaping its rightful reward.

The tactician also is distinguished from the technician by the breadth of innovative weapons that he brings to bear on the tactical problem. Modern technician-tacticians think in terms of missiles, guns, torpedoes, and mines. These are valid pieces of the tactical problem, but the real tactician also thinks in terms of influences and effects far beyond ordnance. The tactician must consider the aspects of positioning and timing, secrecy, surprise, deception and confusion, demonstration and intimidation, and command and control.

Tacticians strive to anticipate; to be constantly ahead of the enemy; to occupy the high ground; to use land or water conditions to advantage; and never to allow the enemy an open, unobscured, or unambiguous shot. They seek ways to strike first and to preempt the enemy at every juncture. They use weapons envelopes to advantage; they position friendly forces so they can always concentrate fire and support one another while forcing the enemy to scatter his attack. Consider some of the following facets of tactics:

There is nothing as fundamental to warfare as secrecy. The unalerted enemy is an ill-prepared enemy. Without warning, he cannot ready, deploy, instruct, maneuver, position, or effectively command his forces.

Surprise is another quintessential ingredient. The Trojan War, Washington’s crossing of the Delaware, Pearl Harbor, Midway, Grenada, Libya, and Desert Storm were all overwhelming victories because of surprise, a navy’s greatest force multiplier. Not technologically demanding, not requiring budget in the Future Years Defense Plan, and not necessitating field changes, this aspect of tactics consistently achieves victory with minimum loss.

For deception and confusion, the tactician uses the natural cloak of the sea to misdirect, blind, disrupt, or coax an adversary into apathy. The opportunities are endless, limited only by imagination. Merchant shipping lanes, land, emission control, turn-count masking, zig-zag patterns, and mock radio communications all offer opportunities to keep the enemy off-guard, to delay or unravel his tactical plan.

For years, U.S. aircraft carriers always intercepted foreign aircraft at long ranges from the carrier. Such intercepts conveyed the unmistakable message that aircraft could not approach in wartime and hope to survive. It is a superpower’s privilege to sap an enemy’s will and confidence by repeatedly demonstrating how surely and decisively he can be detected and destroyed. A true tactician showcases his abilities in peacetime as a continual, effectual reminder of his inherent superiority.

Perfectly anticipated, precisely controlled action is another mark of the tactician. He collects the right pieces of information to predict the enemy’s next move, and he consistently develops the ability to act more quickly and with more precision than his opponent.

Commanding officers and their key subordinates must embrace these aspects of tactics. Regrettably, the technician has generally eclipsed the tactician, especially in the case of TAOs, which exist on the crease of two powerful interpretations of their role. On one hand, it is fashionable to view the TAO as an automaton whose role is to react to threats with machine-like, button-pushing precision. On the other hand, the TAO’s real purpose is to be the intelligent being who measures the evolving situation and takes every conceivable step to win and keep the ship safe.

If the TAO’s purpose is simply to direct scripted action, then the technician will suffice; if the TAO is there to guide action intelligently and to find resourceful ways to win, however, he must be a tactician first and foremost. With the technician, the CO enters the combat information center (CIC) and sees a TAO bent over the scope, immersed in the mechanics. With the tactician, the CO should see an officer rising above the details with every option in mind, ready to act in ways that are both sure and insightfully adapted to the situation.

Is it possible that modern technology has made tactics irrelevant? Are today’s operations so linked to technical issues or foreordained by combat system mechanics that there is no place for tactics? No, the opposite is true. The advent of modern technology makes greater, not lesser, demands for superb tacticians.

Consider a single navy ship on a critical mission that will take it through a strait guarded by an adversary. On the west side of the strait at least one conventional submarine is on patrol; on the east shore are truck-mounted, anti-ship cruise missiles. In these days of modern weapons, this scenario may seem like a simple matchup of combat systems. Torpedoes, helicopters, and sonars against the submarine; missiles, guns, and electronic warfare against the cruise missiles. The prudent CO will be assured that these weapons are ready and that the procedures for using them are optimized, in place, and practiced.

The tactician, of course, will go one enormous step farther. He will employ tactics. He will measure the situation carefully, looking for opportunities to exploit. Should he transmit on electronic sensors or remain passive? Should he challenge the enemy or avoid him? In what ways should he confuse, delay, deceive, or surprise the enemy? What pieces of tactical information does he require to anticipate the enemy’s moves, and exactly how will he control his ship’s weapons to assure lightning-quick yet accurate responses?

On the west side of the strait, this tactician will probably “attack” the submarine by using merchant shipping lanes, darkness, and darken ship to hide his approach. He will use speed and maneuver to disrupt any track a submarine might gain. He will take his ship through shallow water to confound and outmaneuver the submarine. He will cover his close-in weapon system mount with gray herculite, remove white windscreens, and paint out distinctive white hull numbers to take away any visual cue of his identity. Finally, he will use helicopters to search for periscopes and masts and drive the submarine to depth.

On the other side of the strait, he might avoid the enemy’s attempts to find him by mixing with merchants or by land shadowing; he could shut down his electronic emissions to prevent identification and classification; he might use oil platforms, or other natural obstructions, as shields against an attack; conceivably communications jamming or deception might be used to misdirect or confuse the enemy’s targeting reports.

In this example the tactician dramatically alters the battle equation. More than simply preparing his ship to repel any attack, through tactics he shields his ship from even becoming a target. He achieves the successful transit without confrontation, without having to pit one weapon against another. He has in essence opened up a panorama of tactical options that improves the probability of success and significantly reduces the levels of risk.

Tactics impel commanders not to be slaves to preconceived or formalized procedures. With tactics, the logistics or amphibious ship is not inherently defenseless in these straits, nor should the Aegis cruiser feel compelled by its mystique or its combat system to transit the straits openly, daring the enemy to react.

In this hypothetical situation, as in virtually all offensive and defensive tactical scenarios, the tactician opens a larger sphere of thought and action – and he guarantees success more assuredly than either the warrior or the technician.

Tactics are more vital now to the U.S. Navy than at any time in the past 20 years. Operations in the littoral areas of the world will put navy ships at great risk. At the edge of the sea, detection of modern antiship cruise missiles, mines, and conventional submarines will be difficult, and reaction times will be compressed. Defense in depth, the doctrine of the past, will be impossible so close to shore, and the dwindling number of carriers will reduce the combat power that has so frequently been just over the horizon. Survival will rest increasingly, therefore, on ingenuity, secrecy, deception, speed, and positioning.

Tactics must return to the forefront as a critical element of our profession. Tactics are our highest calling, and ought to be the focus of preparation for our officers, but today they are not. Tactical savvy is no longer our strong point; we have largely become a Navy of technicians and managers instead of tacticians. Reviving tactical proficiency does not require more money, more people, or a new doctrine command. It requires a dedicated, well-organized, and redirected return to the basics of knowledge, procedure, and tactics.

While naval tactics organizations have long pursued tactical knowledge and procedures, their search has been flawed in many significant ways. Efforts routinely confuse information for knowledge and persistently fail to extract from our tactical and technical experience the penetrating insights that support tactical decision making. To a great extent, our tactical procedures, as embodied in current tactical memorandums, tactical notes, and doctrines, lack coherence and essence. They are like having 50 street maps for various American cities without a map of the interstate system to describe how to get from one to another.

They are often unexecutable in a practical scenario and are frequently too complex to be internalized and fully understood by the lieutenant TAOs who must execute them. They fill a vault with their volume yet provide so little satisfaction to the captain. Despite decades of commitment and work, much remains to be done and undone in the area of communicating knowledge and designing procedure.

These well-intentioned efforts, though, are flawed not by lack of dedication but rather by lack of definition and expectation. We are a Navy largely focused on maintenance and are too comfortable with technical details, parameters, and procedures. Accordingly, we are generally satisfied with descriptions of how a combat system operates technically instead of insisting to know how a system performs tactically.

We understand, for example, how various modes of the SPS-49 affect the moving target indicator circuits or make the antenna scan faster, but we do not see the necessity of knowing explicitly how these modes change the radar’s performance against an incoming missile. We know in detail how much power the radar should have without a clear notion of how much power is enough to see targets of interest at suitable ranges. We have failed to extract the concise and meaningful insights required by tacticians to make correct decisions on the battlefield.

In the area of tactical procedures, the story is similar. Efforts at developing tactical procedures, apparently unaware of the tacticians ultimate role in defining tactics, often overstep the logical bounds of procedure, resulting in procedures that are too long, too intricate, and too numerous to be absorbed and understood by operators in the fleet. Moreover, the procedures fall out of date quickly as conditions, assumptions, and intelligence estimates change.

Finally, development and support of the tactics thinking process are even more adrift. As a rule we do not understand the nature of tactics; we do not perceive the essence. We neither nurture this tactical care in our careers nor explain or support it in “tactics” publications. Seniors do not groom it in juniors and frequently fail to employ sound tactics themselves.

The resurrection of tactics, today buried in procedure and cloaked by fundamental misunderstandings of their essential nature – now requires an extraordinary effort. It is essential that the surface community find the few real tacticians in its ranks – not the ones who claim to be tacticians because of their total recall of threat matrices or their superb dexterity on combat system consoles – but the innovative deep thinkers of our time.

These tacticians must be brought together and given a mandate to redesign the entire structure of our tactics effort. They must identify the essential pieces of tactical knowledge which truly support tactical decision making, and they must design a compact and useful system for conveying that information to the fleet. They must sift through the vaults of current tactical publications and identify the quintessential procedures that are the bedrock of effective tactical action. Then, they must distill them into knowable, concise, and simple guidance.

Finally, the core of these tacticians must form a tactics institute for the surface Navy. The institute must become a think-tank charged with exploring the science of tactical operations. They must investigate the envelope of tactical thought to include advancing new concepts of data fusion, analysis, command and control, maneuvering, targeting, positioning, deception, surprise, secrecy, mutual support, and teamwork. Through this institute the surface Navy can begin to ensure that the art of tactics formulation is nurtured in its officers, that suitable curricula for officers in the surface warfare training continuum is developed and supported, and that the commanding officer’s role as a bone fide tactician is established and solidified within the fabric of surface warfare. If we truly want to preserve tactics and tacticians from extinction, we must take radical steps and take them quickly.

As the frigate pulls away from the pier, the captain waves to his wife and family. The deployment has begun, but he agonizes because he is no closer to building tacticians than he was three weeks ago. He sees before him young officers who have been “methodologized,” consumed by the mechanical and procedural tasks which are properly the domain of senior enlisted men. He tries to make them think on their own, to make decisions, to have a vision, but it is slow progress.

He wonders, “Have we gone too far? Can we turn back the tide of administrators and managers and revive tacticians?”

His thoughts are interrupted by a knock on the door. “Trouble, Captain,” says the XO. “We forgot to send in our monthly retention report.”

This article originally featured in the September 1993 issue of USNI Proceedings, read it in its original form here. Reprinted from U.S. Naval Institute Proceedings magazine with permission; Copyright © U.S. Naval Institute/www.usni.org.

Captain Johnson is the program manager for the Advanced Research Project Agency’s Maritime Systems Technology Office. His sea duty includes tours as executive officer USS Ramsey (FFG-2) and commanding officer USS Vandegrift (FFG-48) where he served as antiair warfare coordinator for the Persian Gulf during the Iraqi invasion of Kuwait. His last shore assignment was Director, Prospective Commanding Officer Course at the Surface Warfare School, Newport, Rhode Island.

Featured Image: PACIFIC OCEAN (June 25, 2018) The guided-missile destroyer USS Dewey (DDG 105) transits the Pacific Ocean while underway conducting operations in the U.S. 3rd Fleet area of operations. (U.S. Navy photo by Mass Communication Specialist 2nd Class Devin M. Langer/Released)

The American Wolf Packs: A Case Study in Wartime Adaptation

This article originally featured on Joint Force Quarterly and is republished with permission. Read it in its original form here.

By Dr. F.G. Hoffman

To paraphrase an often ridiculed comment made by former Secretary of Defense Donald Rumsfeld, you go to war with the joint force you have, not necessarily the joint force you need. While some critics found the quip off base, this is actually a well-grounded historical reality. As one scholar has stressed, “War invariably throws up challenges that require states and their militaries to adapt. Indeed, it is virtually impossible for states and militaries to anticipate all of the problems they will face in war, however much they try to do so.”1 To succeed, most military organizations have to adapt in some way, whether in terms of doctrine, structure, weapons, or tasks.

USS Steelhead (SS-280) refitted with 5.25-inch deck gun, April 10, 1945 (retouched by wartime censors) (U.S. Navy)USS Steelhead (SS-280) refitted with 5.25-inch deck gun, April 10, 1945 (retouched by wartime censors) (U.S. Navy)

The Joint Staff’s assessment of the last decade of war recognizes this and suggests that U.S. forces can improve upon their capacity to adapt.2 In particular, that assessment calls for a reinvigoration of lessons learned and shared best practices. But there is much more to truly learning lessons than documenting and sharing experiences immediately after a conflict. If we require an adaptive joint force for the next war, we need a common understanding of what generates rapid learning and adaptability.

The naval Services recently recognized the importance of adaptation. The latest maritime strategy, signed by the leadership of the U.S. Marine Corps, Navy, and Coast Guard, defines the need to create “a true learning competency,” including “realistic simulation and live, virtual, and constructive scenarios before our people deploy.”3 History teaches that learning does not stop once the fleet deploys and that a true learning competency is based not only on games, drills, and simulations but also on a culture that accepts learning and adaptation as part of war.

This lesson is ably demonstrated by the Navy’s refinement of wolf pack tactics during the Pacific campaign of World War II. The tragic story of defects in U.S. torpedoes is well known, but the Navy’s reluctant adoption of the German U-boat tactics against convoys is not often studied.4 There are lessons in this case study for our joint warfighting community.

The success of the U.S. submarine force in the Pacific is a familiar story. The Sailors of the submarine fleet comprised just 2 percent of the total of U.S. naval manpower, but their boats accounted for 55 percent of all Japanese shipping losses in the war. The 1,300 ships lost included 20 major naval combatants (8 carriers, 1 battleship, and 11 cruisers). Japanese shipping lost 5.5 million tons of cargo, with U.S. submarines accounting for almost 5 million tons.5 This exceeded the total sunk by the Navy’s surface vessels, its carriers, and the U.S. Army Air Corps bombers combined. By August 1944, the Japanese merchant marine was in tatters and unable to support the needs of the civilian economy.6 The submarine campaign (aided by other joint means) thoroughly crippled the Japanese economy.7

This critical contribution was not foreseen during the vaunted war games held in the Naval War College’s Sims Hall or during the annual fleet exercises in the decades preceding the war. Perhaps the Navy hoped to ambush some Japanese navy ships, but the damage to Japanese sea lines of communication was barely studied and never gamed, much less practiced. A blockade employing surface and submarine forces was supposed to be the culminating phase of War Plan Orange, the strategic plan for the Pacific, but it was never expected to be the opening component of U.S. strategy. Submarines were to be used as scouts to identify the enemy’s battle fleet so the modern dreadnoughts and carrier task forces could attack. Alfred Thayer Mahan had eschewed war against commerce, or guerre de course, in his lectures, and his ghost haunted the Navy’s plans for “decisive battles.”8

The postwar assessment from inside the submarine community was telling: “Neither by training nor indoctrination was the U.S. Submarine Force readied for unrestricted warfare.”9 Rather than supporting a campaign of cataclysmic salvos by battleships or opposing battle lines of carrier groups, theirs was a war of attrition enabled by continuous learning and adaptation to create the competencies needed for ultimate success. This learning was not confined to material fixes and technical improvements. The story of the torpedo deficiencies that plagued the fleet in the first 18 months of the Pacific war has been told repeatedly, but the development of the Navy’s own wolf pack tactics is not as familiar a tale. Yet this became one of the key adaptations that enabled the Silent Service to wreak such havoc upon the Japanese war effort. Ironically, a Navy that dismissed commerce raiding, and invested little intellectual effort in studying it, proved ruthlessly effective at pursuing it.10

Learning Culture

One of the Navy’s secret weapons in the interwar era was its learning culture, part of which was Newport’s rigorous education program coupled with war games and simulations. The interaction between the Naval War College and the fleet served to cycle innovative ideas among theorists, strategists, and operators. A tight process of research, strategic concepts, operational simulations, and exercises linked innovative ideas with the realities of naval warfare. The Navy’s Fleet Exercises (FLEXs) were a combination of training and experimentation in innovative tactics and technologies.11 Framed against a clear and explicit operational problem, these FLEXs were conducted under unscripted conditions with opposing sides. Rules were established for evaluating performance and effectiveness, and umpires were assigned to regulate the contest and gauge success at these once-a-year evolutions.

Torpedoed Japanese destroyer IJN Yamakaze photographed through periscope of USS Nautilus, June 25, 1942 (U.S. Navy)Torpedoed Japanese destroyer IJN Yamakaze photographed through periscope of USS Nautilus, June 25, 1942 (U.S. Navy)

Conceptually framed by war games, these exercises became the “enforcers of strategic realism.”12 They provided the Navy’s operational leaders with a realistic laboratory to test steel ships at sea instead of cardboard markers on the floor at Sims Hall. Unlike so many “live” exercises today, these were remarkably free-play, unscripted battle experiments. The fleet’s performance was rigorously explored, critiqued, and ultimately refined by the men who would actually implement War Plan Orange.13 Both the games and exercises “provided a medium that facilitated the transmission of lessons learned, nurtured organizational memory and reinforced the Navy’s organizational ethos.”14 Brutally candid postexercise critiques occurred in open forums in which junior and senior officers examined moves and countermoves. These reflected the Navy’s culture of tackling operational problems in an intellectual, honest, and transparent manner. The Navy benefited from the low-cost “failures” from these exercises.15

Limitations of Peacetime

The exercises, however, had peacetime artificialities that reduced realism and retarded the development of the submarine. These severely limited Navy submarine offensive operations in the early part of World War II.16 With extensive naval aviation participation, the exercises convinced the fleet that submarines were easily found from the air. Thus, the importance of avoiding detection, either from the air or in approaches, became paramount. In the run-up to the war, the Asiatic Squadron commander threatened the relief of submarine commanders if their periscopes were even sighted in exercises or drills.17 This belief in the need for extreme stealth led to the development of and reliance on submerged attack techniques that required commanders to identify and attack targets from under water based entirely on sound bearings. Given the quality of sound detection and sonar technologies of the time, this was a precariously limited tactic of dubious effectiveness.

Technological limitations restricted the Navy’s appreciation for what the submarine could do. The Navy’s operational plans were dominated by high-speed carrier groups and battleships operating at no less than 17 to 20 knots for extended periods, but the Navy’s interwar boats could not keep pace. They were capable of 12 knots on the surface and half that when submerged. They would be far in the wake of the fleet during extended operations. This inadvertently promoted plans to use submarines for more independent operations, which eventually became the mode employed against Japanese commercial shipping in the opening years of the war.

Though they were a highly valuable source of insights at the fleet and campaign levels, the FLEXs had not enforced operational or tactical realism for the submarine crews at the tactical/procedural level. In fact, a generation of crews never heard a live torpedo detonated, proving a perfect match for a generation of torpedoes that were never tested.18 Nor did the Navy practice night attacks in peacetime, although it was quite evident well before Pearl Harbor that German night surface attacks were effective.19 Worse, operating at night was deemed unsafe, and thus night training was overlooked before the war.20 The submarine community’s official history found that the “lack of night experience saddled the American submariners entering the war with a heavy cargo of unsolved combat problems.”21 Once the war began, however, the old tactics had to be quickly discarded, and new attack techniques had to be learned in contact.

Overall, while invaluable for exploring naval aviation’s growing capability, the exercises induced conservative tactics and risk avoidance in the submarine world that were at odds with what the Navy would eventually need in the Pacific. As one Sailor-scholar observed:

Submarines were to be confined to service as scouts and “ambushers.” They were placed under restrictive operating conditions when exercising with surface ships. Years of neglect led to the erosion of tactical expertise and the “calculated recklessness” needed in a successful submarine commander. In its place emerged a pandemic of excessive cautiousness, which spread from the operational realm into the psychology of the submarine community.22

Unrestricted Warfare

Ultimately, as conflict began to look likely, with a correlation of forces not in America’s favor, students and strategists at Newport began to study the use of the submarine’s offensive striking power by attacking Japan’s merchant marine.23 During the spring semester of 1939, strategists argued for the establishment of “war zones” around the fleet upon commencement of hostilities. These areas would be a type of diplomatic exclusion zone, ostensibly to support fleet defense during war. However, the proponents’ intent was to conduct unrestricted warfare aimed at Japan’s long and vulnerable shipping lines.24

Yet there was a gap between what submarines could do and what the emergent plans to conduct unrestricted warfare were calling for. Well before Pearl Harbor, the Navy’s senior leaders understood that unrestricted warfare was a strategic necessity. However, the implications of this change were not acted upon at lower levels in the Navy in the brief era before Pearl Harbor. Doctrine, training, and ample working torpedoes were all lacking. This created the conditions for operational adaptation under fire later.

The Campaign

Due to an insufficient number of boats, limited doctrine, and faulty torpedoes, the submarine force could not claim great success. By the end of 1942, the Pacific Fleet had sent out 350 patrols. Postwar analyses credit these patrols with 180 ships sunk, with a total of 725,000 tons of cargo.25 Although this sounds impressive, over the course of the year, the Navy had sunk the same amount as the German U-boats had in just 2 months in the North Atlantic. This level of achievement was against a Japanese navy that had limited antisubmarine warfare (ASW) expertise and little in the way of radar. The damage inflicted had no impact on Japan’s import of critical resources and commodities, and the campaign could not be seen as a success. The war’s senior submariner, Vice Admiral Charles Lockwood, admitted that the submarine force was operating below its potential contribution.26

Tasked with the ruthless elimination of Japanese shipping, the Pacific Fleet was not producing results fast enough. Some of this shortfall was the result of faulty weapons, and some was attributed to the cautious doctrine of the interwar era. Chief of Naval Operations Admiral Ernest King directed a new approach. He wrote to Admiral Chester Nimitz at Pearl Harbor on April 1, 1943, noting that “effectiveness of operations and availability of submarines indicate desirability, even necessity, to form a tactical group of 4 to 6 submarines trained and indoctrinated in coordinated action for operations such as now set up in Solomons, to be stationed singly or in groups in enemy ship approaches to critical areas.”27 Nimitz immediately directed the implementation of King’s suggestion.28 Interestingly, despite his experience combating U-boats in the Atlantic and protecting the vital sea lines of communication to Europe, King was still oriented toward the employment of submarines against Japanese naval combatants. But in line with the pre–Pearl Harbor vision of unrestricted warfare, the U.S. submarine force was following a strategy of attrition against Tokyo’s merchant shipping, and the Navy submarine force continued to emphasize individual patrols and independent command. They had not been successful in dealing with Japanese warships in critical battles such as Midway. King apparently believed that if they could be properly “trained and indoctrinated in coordinated action,” this shortcoming might be rectified.

At the same time, King was fully engaged with responding to German Kriegsmarine wolf pack tactics, or Rudeltaktik. He was painfully aware how effective they were and was being strongly encouraged by both President Franklin D. Roosevelt and Prime Minister Winston Churchill to adopt defensive measures since the U-boats critically impaired Great Britain’s war effort.29 Moreover, King was aware that the U.S. Navy was not generating the same aggregate tonnage results as the German navy, and he may have concluded that emulating the Germans could produce better results.30 Lockwood, the commander of Submarine Force Pacific (COMSUBPAC), was certainly well aware of the comparisons; in mid-1942, he wrote that “Germans getting 3 ships a day, Pac not getting one ship.”31 Furthermore, his predecessor as COMSUBPAC issued a five-page summary of German wolf pack tactics via a widely distributed bulletin in January 1943.32

Comparisons between theaters may have driven King to propose the shift, but he may have also detected trends in Japanese ASW that would eventually weaken U.S. submarine effectiveness if changes were not put in place. The operational and tactical context facing the submarine force was increasing in complexity. By 1943, Japanese convoys were becoming larger, more organized, and better protected. The escort command was employing more airplanes and newer techniques for detection and attack.

As Lockwood noted in his memoir, collective action was not unknown to the submarine force. Before the war, experiments had attempted simultaneous attacks by several submarines, but communications between boats were not good enough to ensure safety in peacetime operations. These tactics were cursorily explored late in 1941 but were abandoned due to fears of blue-on-blue incidents and limited communications capabilities.33

Now, however, conditions were different, radar had been perfected, high-frequency radio phones were installed, and communications were vastly improved.34 Coordination could be achieved, but the American submariners had little practice at it. The submarine force would have to investigate new tactics on the fly in the midst of the war. (Somewhat ironically, King called for emulating German submarine tactics just as that force was passing the apex of its operational effectiveness. May 1943 was considered the blackest month for the U-boats in the cruel Battle of the Atlantic.35)

King’s message eliminated debate, but the Pacific submarine fleet took its time to interpret fully the doctrinal and tactical implications of the new approach. As a result, the U.S. Navy did not employ the same approach as the Germans. U-boat wolf packs in the Kriegsmarine were ad hoc and fluid. When Admiral Karl Dönitz received intelligence about the location and character of a convoy, he would direct a number of boats to converge on an area where he expected the convoy to be. He would thus direct the assembly of the wolf pack and coordinate its attack from long distance. There was no on-scene commander or collective attack.36 The U-boats were simply sharks, swarming and attacking at will, or swarming to designated areas when directed. The Atlantic convoys were rather large (30 or more ships), encompassing a relatively wide area. A convergence could bring together as many as a dozen boats swarming around a big convoy but without any on-scene battle management.37 A single U-boat would be easily driven off, but a pack would not be. They would stalk the merchant shipping and pick off the slowest quarry every time.

King’s intervention about collective action proved timely. The Japanese navy did eventually enhance its ASW efforts, employing land-based surveillance, better radars, and more coordination. As the U.S. boats were drawing closer to Japan’s home islands, their targets were hugging closer to shallow waters and staying within air coverage. This raised the risk that American submarines would be identified and attacked.

Concerted action by the submarines could offset these changes in the operating context. Singular attacks would draw all the attention of an escort, ensuring that the U.S. boats were driven deep and away from their wounded targets. Coordination by multiple boats would allow continuous pressure on a Japanese shipping convoy and increase the strangulation that Lockwood was aiming to achieve. Multiple threats would distract the convoy’s protective screen and generate more opportunities out of each convoy that was found.

The U.S. Navy did not embrace German wolf pack doctrine or terminology; the accepted term for the tactic was coordinated attack group (CAG). An innovative submariner, Captain Charles “Swede” Momsen, developed the tactics and commanded the initial U.S. wolf pack in the early fall of 1943.38 American CAGs would initially have a senior commander on scene, but it would not be one of the boat’s skippers, as Lockwood desired to have his older division commanders get wartime experience on boats.39

The investigative phase was exhaustive and deliberate over several months. Experienced submarine commanders, not staff officers, developed the required tactics and communication techniques. In an echo of prewar Newport, discussions evolved into small war games on the floor of a converted hotel, which conveniently had a chessboard floor of black and white tiles. The officers who would conduct these patrols developed their own doctrine and tactics.40 The staff and prospective boat captains tested various ways both to scout for targets and then to assemble into a fighting force once a convoy was detected. War games, drills, and ultimately at-sea trials were conducted to refine a formal doctrine. Momsen drilled his captains in tactics, planning to have three boats attack successively—one boat making the first attack on a convoy, then acting as a trailer while the other two attacked alternately on either flank. He also developed a simple code for use on the new “Talk Between Ships” system so that boats could communicate with each other without being detected or intercepted by the Japanese.

The American approach rejected the rigid, centralized theater command and ad hoc tactical structure of the Germans.41 Consistent with its culture, the U.S. Navy took the opposite approach. CAGs comprised three to four boats under a common tactical commander who was present on scene. Unlike the Germans, these attack groups trained and deployed together as a distinctive element. They patrolled in a designated area under a senior commander and followed a generic attack plan. Other than intelligence regarding potential target convoys, orders came from the senior tactical commander on scene and not from the fleet commander. This tactical doctrine called for successive rather than swarming attacks.42 Subsequently scholars have been critical of these deliberate and sequential attack tactics, which negated surprise and simplified the job of Japanese escorts.43

Strangely, there seems to have been little urgency behind COMSUBPAC’s doctrinal and organizational adaptation. This top-down direction from afar (from Admiral King) appears to have been resisted until met with bottom-up evidence derived from experienced skippers. In the records of this period, Lockwood appears to be guilty of delaying tactics, but captains John “Babe” Brown and Swede Momsen convinced him to have “a change of heart.”44

Lockwood and his team at Submarine Force Pacific did not merely take King’s directive and implement it. He and the commander of U.S. submarines based in Australia, Rear Admiral Ralph Christie, were not in favor of the change in tactics. In his memoirs, Lockwood noted in a single sentence that he was directed to conduct wolf pack tactics by King. He did apply groups of four to six boats in his packs. And while he did develop the doctrine King tasked them to create, he did not apply it as King desired, against military shipping or approaches to critical operational areas. Instead, Lockwood deployed the CAGs to his ruthless campaign of attrition against Japanese commerce. The developmental process was entirely consistent with bottom-up adaptation. Lockwood was permitted to develop the command and control process, tactics, and training program on his own. Centralized command from Pearl Harbor was rejected, which reflected both the traditional Navy culture of command responsibility and autonomy and Lockwood’s appreciation for how Allied direction finding and signals intelligence in the Atlantic were fed by Dönitz’s centralized control and extensive communications.

Even after his change of heart, Lockwood and the submarine force took their time to work out the required doctrine and tactics in an intensive investigatory phase. The first attack group, comprised of the Cero (SS-225), Shad (SS-235), and Grayback (SS-208), was not formed until the summer of 1943. Momsen, who had never been on a combat patrol, was the commodore and rode in Cero. The pack finished its preparations and deployed from Pearl Harbor in late September on its combat patrol from Midway on October 1, 1943, exactly 6 months to the day from King’s message. This was hardly rapid adaptation, given the lessons from both the German success story in the Atlantic and the lack of success in the Pacific.

The initial cruise was deemed a success. Momsen’s CAG arrived in the East China Sea on October 6, 1943. It made a single collective attack on a convoy and was credited with sinking five Japanese ships for 88,000 tons and damaging eight more with a gross tonnage of 63,000 tons. While this met the measures of success that Lockwood wanted, the commanders involved were less than enthusiastic. The comments from the participating captains were generally mixed, with many indicating they would prefer to hunt alone rather than as a member of a group. They believed that the problems of communication were technologically unsolvable and that the risk of fratricide was unavoidable. Moreover, commanders preferred operating and attacking alone—consistent with the Navy’s traditional culture and the community’s enduring preference for independent action (and the rewards that came with it). Momsen, perhaps reflecting an appreciation of the complementing role high-level intelligence could play, recommended centralized command from Pearl Harbor rather than an on-the-scene commander, something Lockwood immediately overruled.45 But various packs were planned and began training. Ingrained conservatism and fear of firing on a friendly vessel framed the emerging tactics. These in practice emphasized “cooperative search” over collective attack.46

Figure 1.

The need to explore innovative tactics was directed from the top, but the Navy leadership was patient in letting local leaders figure out the “how.” The validity of coordinated action grew on commanders such as Lockwood. Whatever reservations they might have held, the American wolf packs continued during the remainder of the year and were a common tactic during 1944. Unlike Dönitz’s Operation Paukenschlag(Drumbeat) in the Atlantic in early 1943, Lockwood’s force began to win the war of attrition in the Pacific. The success was likely due to the combination of finally having defect-free torpedoes and employing new search tactics. But as Lockwood noted in a tactical bulletin, for the first time, tonnage totals between the German effort and that of the American submarine force “now compare favorably.”47

One dramatic case gives an example of how effective CAGs could be. In late July 1944, Commander Lawson “Red” Ramage commanded the USS Parche, part of a wolf pack labeled “Park’s Pirates” after Captain Lew Parks, also aboard the Parche. The Pirates included the USS Steelhead, skippered by Lieutenant Commander Dave Whechel, and the USS Hammerhead, whose skipper was Commander Jack Martin. After a patch of bad weather and poor radio reporting, the Pirates found their quarry. Although frustrated by miscommunications, Martin identified a large Japanese convoy on the evening of July 30. Although it was a long shot, Parks ordered Ramage to give chase, and for 8 hours the Parche chased down the fleeing convoy.

What happened next was a maritime melee. Ramage surfaced inside the convoy in the dark and began a methodical attack, slicing in and around the larger tankers and setting up shots that ranged from only 500 to 800 yards. Ramage’s boat passed within 50 feet of one Japanese corvette on an opposite tack that could not depress its guns enough to strike it.48 The Parche was almost rammed once and was subjected to fire from numerous vessels as it raised havoc with the 17 merchant ships and 6 escorts of Convoy MI-11.

Within 34 minutes, Ramage fired 19 torpedoes and got at least 14 hits. Lockwood credited Parche with 4 ships sunk and 34,000 tons, while the Steelhead got credit for 2 ships of 14,000 tons. Ramage’s epic night surface attack earned him the Medal of Honor.49 His daring rampage was a perfect example of a loosely coordinated attack relying on individual initiative (not unlike a classic U-boat commander’s approach in its execution) rather than formal tactics or a set piece approach that failed to overwhelm the escorts.50

After mid-1944, there were no major adaptations in submarine warfare during the remainder of the Pacific campaign. Ships, doctrine, training, and weapons were highly effective. In a sense, the U.S. submarine war did not truly begin until the CAGs went to sea in late 1943. Until then, it “had been a learning period, a time of testing, of weeding out, of fixing defects in weapons, strategy, and tactics, of waiting for sufficient numbers of submarines and workable torpedoes.”51 Yet within a few months, Japan’s economic lifeline was in tatters.

Exploiting an increased number of boats and the shorter patrol distances afforded by advanced bases in Guam and Saipan, U.S. patrol numbers increased by 50 percent to 520 patrols in 1944. These patrols fired over 6,000 torpedoes, which had become both functional and plentiful. They sank over 600 ships for nearly 3 million tons of shipping. They reduced Japan’s critical imports by 36 percent and cut the merchant fleet in half (from 4.1 million to 2 million tons). While Japanese oil tanker production increased, oil imports dropped severely (see figure).52

Lockwood took wolf packs to a new level in 1945. Now a firmly convinced advocate, he carefully planned an operation with nine boats, operating in three wolf packs, that would traverse the heavily mined entrances of the Sea of Japan.53 The development of an early version of mine-detecting FM sonar allowed boats to detect mines at 700 yards and bypass them. Submarines could now enter mined waters such as the Straits of Tsushima surreptitiously and operate in areas the Japanese mistakenly believed were secure, cutting off the crucial foodstuffs and coal shipments transiting from Korea to Japan. Lockwood’s staff meticulously planned this operation, partially motivated by his desire to avenge the loss of the heroic Commander Dudley Morton and the USS Wahoo in the northern Sea of Japan in fall 1943. Each of the U.S. boats was fitted with FM sonar, and the crews received detailed training in its use. Once they had made the passage and were at their assigned stations in the Sea of Japan, the submarines, working in groups of three, were scheduled to begin a timed attack throughout the area of operations at sunset on June 9. This collective action group was unique in that, instead of gaining an advantage by concentrating their combat power on a single target or convoy, the Hellcats concentrated as a group for their entrance through the narrow Tsushima and then disaggregated. Their simultaneous but distributed attack was designed to shock the Japanese and overwhelm their ability to respond.

In Operation Barney, nine boats led by Captain Earl Hydeman successfully surprised the Japanese and sank 27 vessels in their backyard.54 But it cost Lockwood one of his own boats, as the USS Bonefishunder Lieutenant Commander Lawrence Edge was lost with all hands.55

Without King’s top-down intervention, the adaptation to the use of CAGs may not have been initiated. The success of its adoption, however, was a function of letting local commanders develop their own doctrine. By the end of the war, Lockwood was more enthusiastic about the prospects of the American wolf packs. A total of 65 different wolf packs deployed from Hawaii, and additional groups patrolled out of Australia as well.56 Ironically, they never focused on King’s original intent of serving as ambushers against naval combatants. Instead, the packs remained true to Lockwood’s guerre de course against Japan’s economy.

Cross-Domain Synergies

The historical requirement to adapt in the future may be complicated by the evolving character of modern conflict and the expectation that the joint force will need to gain and exploit cross-domain synergies. The Chairman of the Joint Chiefs of Staff Capstone Concept for Joint Operations (CCJO) is predicated upon creating cross-domain synergies to overcome operational challenges. Another element is to seize, retain, and exploit the initiative in time and across domains.57 Some of this synergy will no doubt be gained in peacetime through concerted efforts to improve interoperability. But if cross-domain synergy is to “become a core operating concept,” as suggested by former Chairman General Martin Dempsey (Ret.) in the CCJO, then we need to also expect to seek out new synergies in wartime.58 Here again, the submarine case study—with its numerous technological adaptations (surface and air search radars, sonars, and improved torpedoes) and cooperation with signals intelligence and the Army Air Corps—is evidence that trans-domain learning is both necessary and feasible, even in combat conditions.

This raises a set of critical questions about joint adaptation in tomorrow’s wars. In future conflicts, how prepared will the joint community be to establish test units and create synergistic combinations on the fly? How prepared are we to actively adapt “under fire” as a joint warfighting community? Do we have the right learning mechanisms to create, harvest, and exploit lessons horizontally across the joint force during combat operations? Such horizontal learning has been crucial in successful examples of adaptation in the past.59 Based on this case study, and several others conducted in a formal case study of U.S. military operations, the following recommendations are offered.

Leadership Development. Senior officers should understand how enhanced operational performance is tied to collaborative and open command climates in which junior commanders can be creative, and plans and tactics can be challenged or altered. The importance of mission command should not excuse commanders from oversight or learning, from providing support, or from recognizing good or bad practices for absorption into praxis by other units. Professional military education (PME) programs should develop and promote leaders who remain flexible, question existing paradigms, and can work within teams of diverse backgrounds to generate collaboration and greater creativity. Case studies in military adaptation should be part of PME strategic leadership syllabi.

Cultural Flexibility over Doctrinal Compliance. Joint force commanders should instill cultures and command climates that embrace collaborative and creative problem-solving and display a tolerance for free or critical thinking. Cultures that are controlling or doctrinally dogmatic or that reinforce conformity should not be expected to be adaptive. Commanders should learn how to create climates in which ideas and the advocates of new ideas are stimulated rather than simply tolerated. If institutions are to be successful over the long haul or adaptive in adverse circumstances, promoting imaginative thinking and adaptation is a must.

Learning Mechanisms. Commanders should be prepared to use operations assessments to allow themselves to interpret the many signals and forms of feedback that occur in combat situations. If needed, they may elect to create special action teams or exploit formalized learning teams to identify, capture, and harvest examples of successful adaptation. These teams or units might have to be created to experiment with new tactics or technologies. Commanders should codify a standard process to collect lessons from current operations for rapid horizontal sharing. They have to be prepared to translate insights laterally into modified praxis to operational forces and not just institutionalize these lessons for future campaigns via postconflict changes in doctrine, organization, or education.

Chief Torpedo man Donald E. Walters receives Bronze Star for service aboard USS Parche (SS-384) (U.S. Navy/Darryl L. Baker)Chief Torpedo man Donald E. Walters receives Bronze Star for service aboard USS Parche (SS-384) (U.S. Navy/Darryl L. Baker)

Dissemination. Commanders should invest time in ensuring that lessons and best practices are shared widely and horizontally in real time to enhance performance and are not just loaded into formal information systems. The Israel Defense Forces are exploring practices that make commanders more conscious about recognizing changes in the operating environment from either their own forces or the opponent.60 There may be something to practicing learning in this way and making it the responsibility of a commander instead of a special staff officer.


As Ovid suggested long ago, one can learn from one’s enemies. The U.S. Navy certainly did. The Service did not just emulate the Kriegsmarine; it improved upon its doctrine with tailored tactics and better command and control capabilities. To do so, Navy submarine leaders had to hold some of their own mental models in suspended animation and experiment in theater with alternative concepts. Lessons were not simply harvested from existing patrols and combat experience and plugged into a Joint Universal Lessons Learned System, as is done today. The submarine force had to carve out the resources, staff, and time to investigate new methods in a holistic way from concept to war games to training against live ships.

Because the eventual role of the Silent Service was not anticipated with great foresight, the Americans had to learn while fighting. They accomplished this with great effectiveness, learning and adapting their tactics, training, and techniques. But the ultimate victory was not due entirely to the strategic planning of War Plan Orange. Some success must be credited to the adaptation of the intrepid submarine community.

Ultimately, the U.S. Navy’s superior organizational learning capacity, while at times painfully slow, was brought to bear. The Navy dominated the seas by the end of World War II, and there is much credit to assign to the strategies developed and tested at the Naval War College and the Fleet Exercises of the interwar era. However, a nod must also be given to the Navy’s learning culture of the submarine force during the war. The Service’s wartime “organizational learning dominance” was as critical as the foresight in the interwar period.61 To meet future demands successfully, the ability of our joint force to rapidly create new knowledge and disseminate changes in tactics, doctrine, and hardware will face the same test. 

Dr. F.G. Hoffman is a Senior Research Fellow in the Center for Strategic Research, Institute for National Strategic Studies, at the National Defense University. The author would like to thank Dr. T.X. Hammes, Dr. Williamson Murray, and Colonel Pat Garrett, USMC (Ret.), for input on this article.


Theo Farrell, Military Adaptation in Afghanistan, ed. Theo Farrell, Frans Osinga, and James Russell (Stanford: Stanford University Press, 2012), 18.

Joint and Coalition Operational Analysis, Decade of War: Enduring Lessons from the Past Decade of Operations, vol. 1 (Suffolk, VA: The Joint Staff, June 15, 2012).

A Cooperative Strategy for 21st Century Seapower (Washington, DC: Department of the Navy, March 2015), 31.

For a good overview, see Anthony Newpower, Iron Men and Tin Fish: The Race to Build a Better Torpedo During World War II (Westport, CT: Praeger, 2006).

Theodore Roscoe, United States Submarine Operations in World War II (Annapolis, MD: U.S. Naval Institute, 1949), 479.

Wilfred Jay Holmes, Undersea Victory: The Influence of Submarine Operations on the War in the Pacific (Garden City, NY: Doubleday, 1966), 351.

James M. Scott, “America’s Undersea War on Shipping,” Naval History, December 2014, 18–26.

Ian W. Toll, Pacific Crucible: War at Sea in the Pacific, 1941–1942 (New York: Norton, 2012), xxxiv.

Roscoe, 18.

10 Joel Ira Holwitt, “Unrestricted Submarine Victory: The U.S. Submarine Campaign against Japan,” in Commerce Raiding: Historical Case Studies, 1755–2009, ed. Bruce A. Elleman and S.C.M. Paine (Newport, RI: Naval War College Press, October 2013).

11 Albert A. Nofi, To Train the Fleet for War: The U.S. Navy Fleet Problems, 1923–1940 (Newport, RI: Naval War College Press, 2010).

12 Michael Vlahos, “Wargaming, an Enforcer of Strategic Realism,” Naval War College Review (March–April 1986), 7.

13 Nofi, 271.

14 Craig C. Felker, Testing American Sea Power: U.S. Navy Strategic Exercises, 1923–1940 (College Station: Texas A&M University Press, 2007), 6.

15 Stephen Peter Rosen, Winning the Next War: Innovation and the Modern Military (Ithaca, NY: Cornell University Press, 1994), 75.

16 Nofi, 307.

17 Holmes, 47.

18 Clay Blair, Silent Victory: The U.S. Submarine War Against Japan (New York: Lippincott, 1975), 41; Ronald H. Spector, Eagle Against the SunThe American War with Japan (New York: Free Press, 1985), 484.

19 Charles A. Lockwood, Sink ’Em All: Submarine Warfare in the Pacific (New York: Dutton, 1951), 52.

20 I.J. Galantin, Take Her Deep! A Submarine Against Japan in World War II (Annapolis, MD: Naval Institute Press, 2007), 18.

21 Roscoe, 57.

22 Felker, 62.

23 See J.E. Talbott, “Weapons Development, War Planning, and Policy: The U.S. Navy and the Submarine, 1917–1941,” Naval War College Review (May–June 1984), 53–71; Spector, 54–68, 478–480.

24 Joel Ira Holwitt, “Execute Against Japan”: Freedom-of-the-Seas, the U.S. Navy, Fleet Submarines, and the U.S. Decision to Conduct Unrestricted Warfare, 1919–1941 (College Station: Texas A&M University Press, 2009), 479.

25 Blair, Silent Victory, 334–345.

26 Lockwood, Sink ’Em All, 27.

27 Steven Trent Smith, Wolf Pack: The American Submarine Strategy That Helped Defeat Japan (Hoboken, NJ: John Wiley, 2003), 50; Lockwood, Sink ’Em All, 87.

28 Smith, 51.

29 Ibid.

30 Galantin, 126.

31 Library of Congress, Lockwood Papers, box 12, folder 63, letter, Lockwood to Admiral Leary, July 11, 1942.

32 National Archives and Records Administration (NARA), RG 313/A16 3 (1), Commander, Submarine Forces Pacific, Tactical Bulletin #1-43, January 2, 1943.

33 Roscoe, 240.

34 Charles A. Lockwood and Hans Christian Adamson, Hellcats of the Sea (New York: Bantam, 1988), 88.

35 Peter Padfield, War Beneath the Sea: Submarine Conflict During World War II (New York: Wiley & Sons, 1995), 308–336; Michael Gannon, Black May: The Epic Story of the Allies’ Defeat of the German U-boats in May 1943 (New York: HarperCollins, 1998).

36 Blair, Silent Victory, 360.

37 Clay Blair, The Hunters, 1939–1942 (New York: Random House, 1998); Michael Gannon, Operation DrumbeatThe Dramatic True Story of Germany’s First U-Boat Attacks Along the American Coast in World War II (New York: Harper & Row, 1990), 89–90.

38 Blair, Silent Victory, 511–516; Roscoe, 240.

39 Library of Congress, Lockwood Papers, box 13, folder 69, letter, Lockwood to Nimitz, May 4, 1943.

40 Galantin, 124–129.

41 Padfield, 85–130.

42 Galantin, 129.

43 Padfield, 404–405.

44 Blair, Silent Victory, 479–480.

45 Roscoe, 241.

46 Ibid., 341.

47 NARA, RG 38, Naval Command Files, box 357, Commander, Submarine Forces Pacific, Tactical Bulletin #6-43, November 22, 1943.

48 Stephen L. Moore, Battle Surface: Lawson “Red” Ramage and the War Patrols of the USS Parche (Annapolis, MD: Naval Institute Press, 2011), 116.

49 Ibid., 110–116.

50 Padfield, 433. On the engagement, see Moore, 101–118. See also War Patrol Report #2, August 1944, available at <http://issuu.com/hnsa/docs/ss-384_parche>.

51 Blair, Silent Victory, 524.

52 Ibid., 791–793; Roscoe, 432–433.

53 The operation is covered in detail in Peter Sasgen, Hellcats: The Epic Story of World War II’s Most Daring Submarine Raid (New York: Caliber, 2010).

54 Holmes, 459–461.

55 NARA, RG 38, Naval Command Files, box 358, “Operation Barney” in Submarine Bulletin II, no. 3 (September 1945), 10–16.

56 See the list at <www.valoratsea.com/wolfpacks.htm>.

57 “Chairman Releases Plan to Build Joint Force 2020,” new release, September 28, 2012, available at <www.defense.gov/news/newsarticle.aspx?id=118043>.

58 Cross-domain synergy is a key concept in joint concepts such as the Joint Operational Access Concept and the Chairman’s Concept for Joint Operations. See Capstone Concept for Joint Operations, Joint Force 2020 (Washington, DC: The Joint Staff, September 10, 2012), 13.

59 Robert T. Foley, “A Case Study in Horizontal Military Innovation: The German Army, 1916–1918,” Journal of Strategic Studies 35, no. 6 (December 2012), 799–827.

60 Raphael D. Marcus, “Military Innovation and Tactical Adaptation in the Israel-Hizbollah Conflict: The Institutionalization of Lesson-Learning in the IDF,” Journal of Strategic Studies 38, no. 4 (2014), 1–29.

61 R. Evan Ellis, “Organizational Learning Dominance,” Comparative Strategy 18, no. 2 (Summer 1999), 191–202.

Featured Image: USS Cuttlefish submerging. (Official USN photo # 80-G-K-3348)

Multidomain Battle: Time for a Campaign of Joint Experimentation

The following originally appeared on Joint Force Quarterly and is republished with permission. Read it in its original form here.

By Kevin M. Woods and Thomas C. Greenwood

The term multidomain has reached beyond mainstream military parlance to dominate defense-related discussions, concept papers, and op-eds. While the idea of operating across warfighting domains is hardly original, the rapid growth of capabilities tied to the newly minted space and cyber domains is forcing a re-examination of all previous military concepts and doctrine. This article explores the debate around multidomain battle (MDB). Developing a new warfighting concept (as opposed to a slogan or bumper sticker) is difficult because new concepts need to demonstrate that they are sufficiently better than the status quo at addressing the challenges and opportunities in order to justify the disruptive effects of the change. This, as it should be, is a high bar.

SOFWERX hosts Cyber Capability Expo at its newest facility in Tampa, Florida, to identify cyber technologies to meet current and future Special Operations Forces requirements, October 19, 2017 (U.S. Air Force/Barry Loo)

The desks of the Pentagon are littered with “transformative” joint warfighting concepts that have appeared with great fanfare only to fall into obscurity. Despite serving as a vehicle to explore ideas, in the end, concepts like Rapid Decisive Operations and Air-Sea Battle failed to move beyond the nascent stage. Some of this can be attributed to a natural resistance to top-down joint concepts, the difficulty of exploring future concepts while maintaining readiness, the lack of coherent institutional processes for examining concepts across organizational boundaries, and, ultimately, the lack of patience for what can be an intellectual slog. As a result, many such efforts were never sufficiently examined so as to generate compelling evidence to drive more than cosmetic changes across the force.

This article advocates two approaches to exploring MDB. The first is to link the MDB concept to the existing body of available evidence. The second is to generate new evidence through experimentation. These approaches are offered not because Service concept developers have not already begun this process—as evidenced by the MDB draft concepts and plans for U.S. Army MDB experimentation in 2018 and 2019. Rather, this article argues that in addition to the bottom-up development of what could arguably be deemed a joint concept, there should also be a parallel effort to explore the top-down or explicit joint, theater-level implications of MDB.

The term multidomain itself is most often used as a modifier for a particular application of military force, such as (multidomain) battles, (multidomain) operations, or (cross or multidomain) fires; however, more substantially, MDB promises more fluid, adaptive, and effective operations simultaneously across five domains (land, sea, air, space, and cyber). Although operations are conducted in and occasionally across these five domains, the promise of a concept that makes domain integration the norm and not the exception is a tall order. Extraordinary claims require extraordinary evidence.

The logic of MDB’s underlying tenets is widely accepted, but that is not the same as demonstrating the concept’s viability. Will the application of a multidomain approach enable the Department of Defense (DOD) to overcome current warfighting challenges? Will it allow the Services to seize new opportunities? Or, instead, will MDB distract the Services from restoring atrophied conventional warfighting capabilities? Perhaps more importantly, can MDB serve as a unifying concept that DOD business processes can be organized around for the development of future concepts and capabilities?

MDB is a future concept (perhaps near-future, but future nonetheless). As such, it “must be stated explicitly in order to be understood, debated and tested to influence the development process.”1 The maturation of a concept is a critical first step in the birth of any capability. Concepts are narrative descriptions of suppositions formulated from historical and contemporary experiences; however, as debatable propositions, they must be validated before they transition from concept to capability. This requires settling the debatable elements. This article thus argues that concepts on the scale of MDB require a campaign of experimentation that provides compelling evidence for the concept by fleshing out its operational and institutional contexts.2

The State of the Debate

Proponents of the emerging MDB concept make the case that the joint force must adapt to the times, or, as one author put it, “multi-domain battle . . . doctrine is being developed to address the interconnected, Omni domain battlespace of the 21st Century.”3 One of MDB’s strongest proponents, Admiral Harry Harris, commander of U.S. Pacific Command, argues that “MDB conceptualizes bringing jointness further down to the tactical level [by] allowing smaller echelons to communicate and coordinate directly while fighting in a decentralized manner.”4 Regardless of the operating theater and specific mission, tactical-level MDB operations, noted U.S. Army Pacific Commander General Robert Brown, will drive the Services to “change their distinct Service cultures to a culture of inclusion and openness, focusing on a purple (or joint) first mentality.”5 Rhetorically, at least, the emerging MDB concept is progressing from the often stated but little realized goal of Service deconfliction to increasing interdependency and, in the optimistic version of MDB, seamlessly integrated operations across domains.6

MDB critics dismiss its significance by arguing that it is old wine in a new bottle.7 Even proponents agree that the “idea and desire for cross-domain effects is not new” but contend the traditional Service-domain alignments are inadequate for coping with the new security environment.8 A more fundamental challenge is made by those arguing that the categorization of future war by domain—especially but not limited to the cyber domain—is neither logical nor practical. As one observer notes, “the word [domain] contains some built-in assumptions regarding how we view warfare that can limit our thinking . . . [and] could actually pose an intractable conceptual threat to an integrated joint force.”9

Joining the critics are the cynics, some of whom see MDB’s real purpose as programmatic: a ploy to restore or preserve force structure by returning land power to the tip of the spear in joint operations.10 Others see the concept as requiring deep institutional reforms that are simply unattainable.11 As one pessimist argued, “without consistently organizing, training, and equipping as a joint team, the Services will be ill-prepared to provide multi-domain capable forces to combatant commanders, continuing history’s trend of falling short of the vision of jointness.”12 The institutional questions loom large here. At one end of the spectrum there are calls to form separate Services for the space and cyber domains.13 At the other end, one MDB proponent provides fodder for the cynics by arguing that the only way to implement MDB is to create a single force and eliminate the independent Services.14

Running parallel to the ongoing MDB debate are distinct theater versions of the concept. Because practice trumps theory in the application of military force, how the MDB concept evolves will be strongly influenced by how the operating theaters find a way to employ its promise.

In the Pacific, where much of the initial energy behind the cross-domain idea began, MDB has been described as:

ground-based batteries of anti-aircraft, anti-missile, and anti-ship weapons, supported by long-range sensors and jammers, that can strike targets well out to sea. Islands defended by such Army batteries (or Marine Corps outposts) could serve as unsinkable anvils, with the Navy and the Air Force as the highly mobile hammers.15

In support of developing MDB, the Army has recently established a Multi-Domain Task Force in U.S. Army Pacific to accelerate the process of overcoming the tactical and technical challenges associated with reincarnating the Army’s capability to “sink ships.”16 This bottom-up approach to building a joint capability, as one commentator noted, has the potential to simultaneously work toward joint interoperability, interdependence, and integration. But this may fall short of answering how the Services can organize, train, and equip themselves to sustain the readiness required to operate as an MDB capable force.17

Meanwhile in Europe, the Army is offering MDB as a conceptual solution to a different, but in many ways familiar, problem set. The Russian army is no longer the colossus of the Cold War era, but it still presents the challenge of mass. Whereas the Russia’s army does not boast a raw-troop-strength advantage over the North Atlantic Treaty Organization (NATO), it is threatening a multidomain equivalence in long-range missiles, rockets, drones, sophisticated cyber attacks, jamming, and an integrated information campaign.18 The solution, argues the commander of the U.S. Army’s Training and Doctrine Command, is to take the multidomain fight to the adversary:

AirLand Battle started developing the concept of “extended battlefield.” This concept noted that different commanders had different views of the battlefield in geographical terms. [MDB] continues the concept of extended battlefield but now with a focus on the extension across domains and time. . . . [MDB] endeavors to integrate capabilities in such a way that to counteract one, the enemy must become more vulnerable to another, creating and exploiting temporary windows of advantage.19

This NATO-centric version of the MDB development process explicitly argues that, just as the earlier Soviet threat drove large-scale change in the U.S. military’s warfighting doctrines, the new Russian threat will drive long-overdue updates to Army force structure and critical warfighting capabilities, especially in the areas of long-range fires and cyber/electronic warfare.20

It is clear, then, that there are multiple lenses through which one can view the emerging MDB concept. Each perspective brings a unique set of operational and institutional contexts to the process of concept development. Having a unique perspective can be a healthy part of a robust debate, but progress requires an agreed-upon set of facts, or, in the case of an emerging concept, a common basis of evidence. The concept development challenge is to generate credible evidence that is relevant to decisionmakers from across the tactical-operational and conceptual-institutional divides.

The Emerging MDB Concept

According to a new Army–Marine Corps white paper, the MDB concept “describes how U.S. and partner forces organize and employ capabilities to project and apply power across domains, environments, and function over time and physical space to contest adversaries in relative ‘peace’ and, when required, defeat them in ‘war.’”21 The white paper posits three key tenets or “interrelated components of the solution,” as they are so labeled in the document.

First, MDB requires appropriate force posture for the “calibration of forward presence, expeditionary forces, and integration of partner capabilities to deter the adversary and, when necessary, defeat the enemy’s fait accompli campaign.” The latter is defined as an enemy campaign that seeks to rapidly achieve military and political objectives before an allied response can be generated. Next, MDB will be executed by resilient forces that “can operate semi-independently in the expanded operational area while projecting power into or accessing all domains.” Headquarters elements will use a mission command philosophy to integrate operations with advanced capabilities. Finally, converging joint force capabilities will “detect and create physical, virtual, and cognitive windows of advantage” during the three phases of an MDB campaign: competition, defeat the enemy in armed conflict, and return to competition. The white paper concludes by offering that the MDB concept allows U.S. forces to outmaneuver adversaries physically, virtually, and cognitively, applying combined arms in and across all domains. It provides a flexible means to present multiple dilemmas to an enemy by converging capabilities from multiple domains to create windows of advantage enabling friendly forces to seize, retain, and exploit the initiative to defeat enemies and achieve campaign objectives. Employing the ideas in this concept, the Joint Force can credibly deter adversary aggression, defeat actions short of armed conflict, deny the enemy freedom of action, overcome enemy defenses, control terrain, compel outcomes, and consolidate gains for sustainable results.

While these three tenets establish a useful framework for institutional considerations of the concept, they do not capture some of the explicit and tacit implications of MDB’s potential utility in a theater or joint campaign. To that end, this article offers the following four attributes, derived from the current MDB concept, as potentially useful in developing a joint campaign of experimentation to better understand the concept and to develop evidence for or against its military utility in the joint force.

First, despite the battle suffix, MDB may have more to do with campaigns than tactical actions. The battle aspects required to create windows of advantage are a necessary precondition to creating decisive overmatch.22 However, various descriptions point to an operational-level concept designed to maneuver friendly forces—and direct their kinetic and nonkinetic fires or effects—simultaneously across five domains.

Second, overmatch in one domain may trigger cross-domain multiplier effects that theater commanders can leverage to bypass, unhinge, and defeat an enemy. This, of course, works in both directions, which is why failing to adequately defend the force across multiple domains may have an outsize impact on war termination.23

Third, cyber and space domains may become tomorrow’s most valued battlespace given U.S. force dependence on the electromagnetic spectrum and satellite-enabled intelligence and communications. The continued development of sophisticated cyber weapons and employment means—as well as the direct and indirect weaponization of space—could exacerbate this trend.

Fourth, MDB implies the need to reexamine our approach to joint command and control. The authorities needed by geographic combatant commanders charged with planning, coordinating, integrating, deploying, and employing forces (and their effects) simultaneously across five domains will increasingly challenge the very concept of boundaries and the traditional relationships used to conduct joint campaigns.

The MDB concept remains more aspirational than practical at this point. To overcome the cognitive challenges and bureaucratic inertia described earlier, the concept needs to demonstrate that it is both more than the sum of its parts and sufficiently better than the status quo.

Operational Antecedents: Two Case Studies

Historical case studies aid the concept development process by contextualizing the problem. As critics and proponents alike have noted, “cross-domain” or combined arms operations stretch back into antiquity. The following case studies offer two examples of multidomain operations. Like any case study, some imagination is required to place the perceptions of the past into a future context. These cases provide some insights for how cross-domain capabilities, applied primarily at the tactical level, can have outsize operational implications.

Guadalcanal. The conceptual assumption in MDB is that the joint force commander must leverage the interdependencies occurring between diverse operational activities simultaneously across multiple domains. It is not enough just to manage, coordinate, deconflict, and integrate. In his 1987 article “Thinking About Warfare,” Lieutenant General Phillip D. Shutler, USMC (Ret.), used the 1942 South Pacific campaign to highlight the three strategic pathways (primarily air, sea, and undersea) that U.S. forces had to successfully transit during World War II before they could project combat power overseas. Although he labeled the strategic pathways regimes instead of domains, the underlying concept remains the same.

Shutler observed that once enemy airfield construction on Guadalcanal was completed, Japanese land-based aircraft were capable of attacking U.S. planes stationed 500 miles to the southeast on Espiritu Santo—threatening the supply lines connecting the United States with Australia and New Zealand. Accordingly, the Marines were ordered to seize the airfield on Guadalcanal to deny its use to the Japanese. In other words, U.S. land forces, in effect, were directed to create an antiair warfare shield at Guadalcanal to protect Espiritu Santo. But as the operational campaign progressed, the Marines’ (and later the Army’s) mission shifted from antiair warfare to enabling U.S. land-based aircraft to support subsequent island-hopping battles to the north and the eventual reduction of the Japanese strongpoint on Rabaul.

Initial success, however, required the United States to prevent Japanese ground forces from reinforcing Guadalcanal. A successful landing would have turned the battle into yet another symmetrical and protracted, single-domain, attritional fight between opposing land forces—both of whom sought to control the airfield. As Shutler noted, accomplishing this required U.S. submarines, surface ships, and naval aviation to establish maritime and aviation “shields” (that is, anti-submarine, anti-surface, antiair defenses) that the Japanese had to penetrate before their ground reinforcements could reach Guadalcanal.24

During the critical phases of the campaign, Japanese forces were unable to effectively penetrate the “multidomain” defensive shields, and the Marines were able to preserve their tactical overmatch ashore on Guadalcanal (approximately 11,000 Marines against 2,000 entrenched Japanese, many of whom were civilian laborers). The tipping point occurred on November 14, 1942, when U.S. naval forces attacked and sank seven Japanese troop transports that were carrying approximately 7,000 embarked Japanese troops trying to reinforce Guadalcanal.25 Although the Japanese did partially penetrate the U.S. shields during the campaign, they were unable to do so with sufficient combat power to alter the battle’s outcome.

Once U.S. air operations began at Guadalcanal’s Henderson Field, a multiplier effect occurred because the Japanese fleet was largely restricted to conducting night operations. This was due in part to additive U.S. airpower projected from ashore and concomitant flexibility gained from an untethered U.S. fleet that could inflict serious losses on Japanese shipping during daylight hours. This reduced Japanese flexibility and freedom of maneuver with implications well beyond the tactical area of operations and marked the start of the U.S. island-hopping campaign.

Like many similar operations in the Pacific theater, Guadalcanal had only marginal tactical utility as an island except for its value to the air domain. The airfield was the operational lynchpin that was denied to the enemy by adroit integration of multidomain activities on the land, sea, and in the air. This further enabled U.S. land-based airpower to support the drive from the Solomon Islands northward into the Central Pacific and eventually to the Japanese homeland.26

Falkland Islands. Almost 40 years after Guadalcanal, we can observe the same multiplier effect in a more modern campaign—the 1982 Battle of the Falklands—that revolved around a centuries-old territorial dispute between the United Kingdom and Argentina over the Falkland (Malvinas) Islands.27 Like the U.S. fleet in the Solomon’s Campaign, the United Kingdom established maritime and antiair shields around the Falklands in order to isolate the objective area, protect Royal Navy/Marines amphibious operations, and deny Buenos Aires the ability to reinforce its forces.

Multidomain actions in the Falklands campaign were numerous, and the multiplier effects these actions had on the campaign’s outcome were significant. The sinking of the 13,500-ton Argentine cruiser General Belgrano (armed with 15 6-inch guns and 8 5-inch guns) by three conventional torpedoes fired from the British nuclear submarine Conqueror took the lives of 323 Argentine sailors (slightly more than half of their total casualties suffered during the war). But more importantly, this action had a cross-domain effect that forced the Argentine surface navy to remain inside its territorial waters for the duration of the campaign.28 Additionally, the sinking of the Belgrano dramatically relieved naval surface pressure on Great Britain’s fleet operating in the Falkland littorals, which in turn allowed Royal Navy vessels on picket duty more time to visually detect Argentine aircraft being launched from the mainland and alert the British Task Force.29

The multiplier effect continued when British special operations forces, supported by naval gunfire, conducted an amphibious raid on Pebble Island to further reduce the Argentine air threat. The raid destroyed 11 forward-based Argentine aircraft. While Argentine helicopters and light aircraft were subsequently dispersed around the islands, the raid forced Argentina to withdraw most of its high-performance aircraft 400 miles back to the mainland.30 Thus, Argentine aircraft were required to fight at their maximum operating radius, which greatly reduced their time on station (Argentina had only limited aerial refueling capability). This was a major advantage for Great Britain’s amphibious fleet and embarked ground forces, who were worried they would not have air superiority during the amphibious landing.

Dismissing the Falklands as nothing more than a creative use of limited assets under extreme conditions risks overlooking key multidomain insights that contributed to operational success. If the notion of achieving dominance in one or more warfighting domains is a thing of the past, then learning to leverage a broader but perhaps relatively less robust toolkit is necessary. To modify a quotation often attributed to Winston Churchill, “Gentlemen we are out of overwhelming resources; Now we must think.”31

It might be easy to dismiss military case studies of the previous century as irrelevant to the challenges faced when looking forward into the current one. But it is worth considering how these multiple domains were integrated in the first place. The process (including technical, conceptual, and instructional efforts) of integrating new-fangled flying machines into the traditional warfighting domains of the land and sea began decades before a mature concept. It was not a straight line or a preordained outcome. The associated technologies and tactical concepts were leavened by decades of peacetime “experimentation” and wartime adaptation. The resulting capabilities for presenting an adversary with multiple, simultaneous dilemmas across domains changed the way the United States fights at both the tactical and operational levels of war.

Developing Evidence

The second source of evidence with which to examine the viability of the MDB concept is to look at it from operational perspectives and across a range of contexts. To do this, DOD should subject the MDB concept and its supporting tenets to a rigorous campaign of joint experimentation—even as the specific capabilities are still being developed. Joint experimentation in this context is an inclusive phrase meant to indicate the exploration of ideas, assumptions, and crucial elements of nascent MDB capabilities. To be clear, joint experimentation covers a wide range of activities (from structured seminars, virtual and constructive environments, to field events) and should be seen as complementary or undertaken in parallel with the development of specific capabilities or tactical employment concepts.

We employ the term campaign in association with joint experimentation to indicate that no single event can generate the quality or variety of necessary data. Moreover, only an experimentation campaign utilizing iterative activities with learning feedback loops (including workshops, wargames, constructive and virtual simulation, and live field events) can generate sufficient evidence to genuinely assess what it will take to realize, adapt, or abandon the MDB idea.

In terms of military experimentation, no single method has ever worked. The complex nature of military problems, and especially ones with interactions across five domains, argues for diverse forms of “discovery experimentation” to introduce novel systems, concepts, organizational structures, and technologies into settings where their use can be observed and Red Teamed.32 The results of such a comprehensive assessment will help identify MDB similarities and differences between the theaters, and will inform future doctrine, organization, training, materiel, leadership and education, personnel, facilities, and policy initiatives that must be addressed before MDB can become a deployable set of capabilities.

Airman aboard KC-135 Stratotanker participates in Red Flag 16-3, one of four Red Flag exercises that focuses on multidomain operations in air, space, and cyberspace, at Nellis Air Force Base, Nevada, July 18, 2016 (U.S. Air Force/David Salanitri)

One of the most complex challenges in debates about future joint concepts is not the concept per se; it is the nature of jointness as practiced in a post–U.S. Joint Forces Command (USJFCOM) environment. Without digressing too far into the history of USJFCOM’s role in joint concept development and experimentation, it is worth contrasting the contexts. Formed in 1999, USJFCOM developed a generally top-down approach to joint concept development and experimentation. While this approach had some advantages, it often resulted in excessively large experiments, with the Services playing a limited or marginally productive role. When USJFCOM was disestablished in 2011, joint concept development reverted to the Joint Staff J7, whose time and resources for experimentation was more limited.33 More recently, Service or multi-Service–led efforts to develop and experiment with new joint concepts are increasing. This can be seen as a bottom-up, collaborative effort. While this approach has many practical advantages over the top-down approach, it is not without challenges—a key one being that the longer joint stakeholders (that is, combatant commands and prospective joint force commanders) remain spectators to the Service-dominated joint experimentation process, the less likely MDB’s theater-wide and strategic-level implications will be subjected to a full examination by the customer.

Under Joint Staff policy for concept development, experimentation begins after concept development. This may be adequate for narrow concepts or mission/domain capabilities where one Service has the lead. But this approach seems ill-suited for complex and multifaceted warfighting concepts such as MDB. As the two case studies indicate, cross-domain overmatch and multiplier effects are often discovered and subsequently leveraged in the course of operations. Early discovery experimentation with some level of joint analysis and sponsorship is essential. Not only will such early experiments increase the capacity to do joint experimentation, but they can also help co-develop Service concepts within a joint context.

As noted at the outset of this article, the MDB debate at this stage is a useful set of thought experiments, but it is not producing tangible evidence. Such evidence would shift the debate from a primarily subjective one to a more balanced and objective conversation. However, the recent history of joint concept development and the very nature of institutional jointness as practiced in DOD are not encouraging. According to the Joint Staff, joint concepts are assessed “using various analytical methods; the joint concept community evaluates both developing and approved concepts to determine whether they are feasible and promote informed decisions on developing new joint capabilities.”34

One potentially more lucrative approach would be to embark on a series of parallel joint discovery experiments designed to identify the specific characteristics, demands, and challenges associated with assessing the feasibility of MDB transcending theater-specific applications to serve as a more universal warfighting concept. Such a joint discovery experiment has historically been at the heart of military experimentation.35

The objective of discovery experiments is to learn, so it is useful to begin with a set of well-defined conceptual and operational conditions. One does not seek a well-defined “concept,” rather a statement of the military problem and a clear understanding of the initial military context. The discovery experimentation approach, supported by an initial data collection plan, is designed to tinker with the variables, modify the conditions, and challenge the assumptions and constraints in a way that dynamically helps refine a nascent concept and identify the kinds of capabilities worth considering. This notion of progressive learning through experimentation generates feedback that enables concept framing, definition, and refinement to occur dynamically.

The ability to use experimentation to explore the utility of emerging technologies and concepts is a force multiplier. Technology cannot be optimized until its impact on warfighting concepts and doctrine is fully appreciated. According to the National Academy of Sciences in a study done for the Navy:

By simulating future systems, [military commanders] can also learn how those systems will work in simulated combat environments and how to use forces equipped with such proposed systems. By such means they can explore new ideas and concepts for the use of variously composed and equipped forces against diverse anticipated threats, and they can learn how to integrate such forces on a large scale in the joint and combined force environment.36

One major challenge in calling for more joint experimentation is the large gap between the operating environment envisioned in the MDB concept and the availability of validated models and simulations. Earlier efforts to support joint analyses (both constructive and human-in-the-loop) with custom designed joint models “amounted to a costly failure with little or no resulting joint analysis capability gain for the Department.”37 Nevertheless, progress in MDB will require some capability to integrate space, cyber, and electromagnetic effects into models designed to explore the interaction of new capabilities and human decisionmaking. Any effort to explore MDB in a joint context must include an effort to integrate existing Service modeling and simulation tools (in the same bottom-up approach discussed here). This will help the Services to operate across new domains in support of specific joint priorities instead of attempting to create a standalone, top-down modeling and simulation solution.

Discovery experimentation is not a free-for-all, but a deliberately crafted and planned approach for addressing an issue long before it becomes a pressing problem. It allows operators to interact with new or potential concepts and capabilities to explore their military utility—something that is not often supported through traditional studies or hypothesis-based experiments. It requires careful attention to the specification and collection of data that will provide solid evidence for the conclusions reached by conducting experiments. If all these constraints are observed, discovery experimentation could be a valuable tool and a useful “way of weeding out ideas that simply do not work, forcing the community to ask rigorous questions about the benefits being sought and the dynamics involved in implementing the idea, or specifying the limiting conditions.”38

It is time to subject the MDB concept to discovery experimentation. To modify slightly Sir Michael Howard’s admonition about future doctrine, it is the “task of military science in the age of peace to prevent new capabilities from being too badly wrong” when the next war starts.39 

Dr. Kevin M. Woods is Deputy Director of the Joint Advanced Warfighting Division at the Institute for Defense Analyses (IDA). Colonel Thomas C. Greenwood, USMC (Ret.), is a Researcher at IDA.


1. John F. Schmitt, A Practical Guide for Developing and Writing Military Concepts, Defense Adaptive Red Team Working Paper #02-4 (McLean, VA: Hicks & Associates, December 2002), 4, available at <www.au.af.mil/au/awc/awcgate/writing/dart_paper_writing_mil_concepts.pdf>.

2. An experiment campaign consists of “a set of experiments, complementary analyses, and synthesis activities . . . conceived, orchestrated, and harvested” in order to better understand the complex issues associated with a warfighting concept. See David S. Alberts and Richard E. Hayes, Campaigns of Experimentation: Pathways to Transformation (Washington, DC: Department of Defense, 2005), 4.

3. Amos C. Fox, “Multi-Domain Battle: A Perspective on the Salient Features of an Emerging Operational Doctrine,” Small Wars Journal, May 21, 2017.

4. Senate Armed Services Committee, Statement of Admiral Harry B. Harris, Jr., USN, Commander, U.S. Pacific Command, on U.S. Pacific Command Posture, April 27, 2017, 19.

5. Robert B. Brown, “The Indo-Asia Pacific and the Multi-Domain Battle Concept,” March 20, 2017, available at <www.army.mil/article/184551/the_indo_asia_ pacific_and_the_multi_domain_battle_concept>.

6. For example, see Joint Staff–issued concept papers Capstone Concept for Joint Operations (CCJO) (Washington, DC: The Joint Staff, 2012), Joint Operational Access Concept (Washington, DC: The Joint Staff, 2012), and Joint Concept for Rapid Aggregation(Washington, DC: The Joint Staff, 2015).

7. Richard Hart Sinnreich, “Multi-Domain Battle: Old Wine in a New Bottle,” The Lawton Constitution, October 30, 2016.

8. Brown.

9. Erik Heftye, “Multi-Domain Confusion: All Domains Are Not Created Equal,” Real Clear Defense, May 26, 2017, available at <www.realcleardefense.com/articles/2017/05/26/multi-domain_confusion_all_domains_are_not_created_equal_111463.html>. For an early related argument, see Martin C. Libicki, “Cyberspace Is Not a Warfighting Domain,” I/S: A Journal of Law and Policy for the Information Society 8, no. 2 (2012).

10. Mike Pietrucha, “No End in Sight to the Army’s Dependence on Airpower,” War on the Rocks, December 13, 2016, available at <https://warontherocks.com/2016/12/no-end-in-sight-to-the-armys-dependence-on-airpower/>.

11. A.J. Shattuck, “The Pipe Dream of (Effective) Multi-Domain Battle,” Modern War Institute at West Point, March 28, 2017, available at <https://mwi.usma.edu/pipe-dream-effective-multi-domain-battle/>.

12. Mike Benitez, “Multi-Domain Battle: Does It End the Never-Ending Quest for Joint Readiness?” Over the Horizon, May 2, 2017, available at <https://overthehorizonmdos.com/2017/05/02/mdb-joint-readiness/>.

13. See James Stavridis and David Weinstein, “Time for a U.S. Cyber Force,” U.S. Naval Institute Proceedings 140, no. 1 (January 2014). The House Armed Services Committee mark of the 2018 National Defense Authorization Act calls for the creation of a separate Space Corps.

14. Michael C. Davies, “Multi-domain Battle and the Masks of War,” Small Wars Journal, May 11, 2017, available at <http://smallwarsjournal.com/blog/multi-domain-battle-and-the-masks-of-war-why-it’s-time-to-eliminate-the-independent-services>.

15. Sydney J. Freedberg, Jr., “Army Must Be Ready for Multi-Domain Battle in Pacific ‘Tomorrow,’” Breaking Defense, January 31, 2017, available at <https://breakingdefense.com/2017/01/army-must-ready-for-multi-domain-battle-in-pacific-tomorrow/>.

16. Megan Eckstein, “Army Set to Sink Ship in 2018 as PACOM Operationalizes Multi-Domain Battle Concept,” USNI News, May 30, 2017. The Army had a standing mission to “sink ships” in the form of the Coast Artillery Corps from 1901 to 1950.

17. Benitez.

18. Sydney J. Freedberg, Jr., “Army’s Multi-Domain Battle Gains Traction Across Services: The Face of Future War,” Breaking Defense, March 13, 2017, available at <https://breakingdefense.com/2017/03/armys-multi-domain-battle-gains-traction-across-services/>.

19. David G. Perkins, “Multi-Domain Battle: Joint Combined Arms Concept for the 21st Century,” Association of the United States Army, November 2016, available at <www.ausa.org/articles/multi-domain-battle-joint-combined-arms-concept-21st-century>. The notion of extended battle dates to General Don Starry and the development of the AirLand Battle Concept in the early 1980s. See Don Starry, “Extending the Battlefield,” Military Review 61, no. 3 (March 1981), 31–50.

20. J.P. Clark, “In Defense of a Big Idea for Joint Warfighting” War on the Rocks, December 22, 2016, available at <https://warontherocks.com/2016/12/in-defense-of-a-big-idea-for-joint-warfighting/>. Kevin Benson, “Extending the Second Offset and Multi-Domain Battle,” Real Clear Defense, November 29, 2016, available at <www.realcleardefense.com/articles/2016/11/30/extending_the_second_offset _and_multi-domain_battle_110411.html>.

21. U.S. Army–Marine Corps White Paper, “Multi-Doman Battle: Evolution of Combined Arms for the 21st Century,” September 30, 2017, available at <www.tradoc.army.mil/multidomainbattle/docs/DRAFT_MDBconcept.pdf>. The Air Force is developing a related Multi-Domain Operations concept that combines Air Force theater contributions into a unified air-space-cyberspace capability set in support of the joint force. See “Multi-Domain Command and Control: The Air Force Perspective with Brigadier General B. Chance Saltzman” (Part 1 of 2), Over the Horizon, April 3, 2017, available at <https://overthehorizonmdos.com/2017/04/03/multi-domain-command-and-control-the-air-force-perspective-with-brigadier-general-b-chance-saltzman-part-1-of-2/>. Saltzman makes the distinction with traditional combined arms by arguing, “[combined arms] is using the assets you have, in some cases from different functions or different domains. Whether it’s artillery, armor, infantry, aviation, those are the traditional arms we’re talking because a lot of times we talk about combined arms in terms of the Army sense of things.”

22. Overmatch is defined as “the application of capabilities or unique tactics either directly or indirectly, with the intent to prevent or mitigate opposing forces from using their current or projected equipment or tactics.” See U.S. Army–Marine Corps White Paper, 13, 17, 55, 61, 73.

23. In the context of a specific campaign, all domains are not of equal value. Even opponents in the same battle may, for a host of reasons, not share the same view of a domain’s value.

24. Phillip D. Shutler, “Thinking About Warfare,” Marine Corps Gazette, November 1987, 20, 23–25.

25. J.J. Edson, “The Asymmetrical Ace,” Marine Corps Gazette, April 1988, 51.

26. Guadalcanal was a pivotal battle in the larger Solomon’s campaign but a closely contested fight to the bitter end. The United States suffered a terrible naval defeat in the Battle of Savo Island, August 8–9, 1942, which reduced Allied heavy cruiser strength in the Pacific by more than 33 percent and compelled Navy transport and supply ships to depart the objective area prematurely. Command relationships between senior Marine Corps and Navy commanders were also overly complex, which led to unnecessary friction. For a more detailed account, see Jeter A. Isley and Philip A. Crowl, The U.S. Marines and Amphibious War: Its Theory and Its Practice in the Pacific (Princeton: Princeton University Press, 1951), 130, 153–162.

27. The proximate cause, however, was a textbook case of two serious and mutually reinforcing misjudgments. These misjudgments, as one scholar put it, stemmed from “the belief in London that Argentina would not invade the Falkland Islands and the expectation in Buenos Aires that Britain would accommodate itself to a military takeover of the islands.” See Richard Ned Nebow, “Miscalculation in the South Atlantic: The Origins of the Falkland War,” Journal of Strategic Studies 6, no. 1 (1983), 5.

28. Sandy Woodward, One Hundred Days: The Memoirs of the Falklands Battle Group Commander (Annapolis, MD: U.S. Naval Institute Press, 1992), 246.

29. In an effort to isolate the islands and limit the scope of the campaign, Great Britain declared a 200-mile radius Total Exclusion Zone around the Falkland Islands. This declaration had the tacit effect of making the Argentinian home waters a bastion for the Argentine navy.

30. Sir Lawrence Freedman, The Official History of the Falklands, Volume II: War and Diplomacy (New York: Routledge, 2005), 431. Freedman wrote, “This was a remarkably successful raid, depriving the garrison of a number of aircraft and undermining morale, by demonstrating the capacity of special forces to mount operations on the Islands against units that were detached from the main forces.” That said, Argentine aircraft remaining in the Falklands after the raid were assessed to be three Shyvan light transports, two navy Tracker early warning aircraft, nine Pucara counterinsurgency aircraft, four Chinooks, three Puma, and one Agusta 109. Although none of these aircraft threatened the overall outcome of the campaign, they remained a major concern throughout it.

31. The most common original Churchill version is “Gentlemen, we have run out of money: Now we must think.” Some evidence suggests Churchill borrowed the phrase from famed physicist Sir Ernest Rutherford.

32. The other two major types of experiments are hypothesis tests and demonstrations. Both could play a role in narrow aspects of the campaign but could not serve as a description of the overall experimentation effort.

33. Joint operating concepts (JOCs) “broadly describe how the joint force may execute military operations within a specific mission area in accordance with defense strategic guidance and the CCJO. Collectively, JOCs describe joint capabilities required to operate across the range of military operations and encourage further examination through wargaming, joint training, and a variety of studies, experimentation, and analyses.” See Chairman of the Joint Chiefs of Staff Instruction 3010.02E, Guidance for Developing and Implementing Joint Concepts (Washington, DC: The Joint Staff, August 17, 2016), A-10.

34. Ibid., A-1.

35. Examples include the Navy’s Fleet Problem series in the 1920s and 1930s that in.tegrated fledgling naval airpower into fleet operations, Brigadier General Billy Mitchell’s Project B experiments on the use of airpower against shipping, or the Marine Corps’ Fleet Landing Exercises in the 1930s leading to the validation of Major Earl Hancock “Pete” Ellis’s amphibious concepts. See Williamson Murray, Experimentation in the Period Between the Two World Wars: Lessons for the Twenty-First Century (Alexandria, VA: Institute for Defense Analyses, November 2000).

36. National Research Council, The Role of Experimentation in Building Future Naval Forces (Washington, DC: National Academies Press, 2004), available at <www.nap.edu/catalog/11125/the-role-of-experimentation-in-building-future-naval-forces>.

37. The failure of the Joint Warfare System, Joint Simulation System, and Joint Modeling and Simulation System programs stemmed from not only the efforts’ complex and high-risk technical natures but also some of the same integration and development issues that challenge the development of joint capabilities. For a summary of the issues and lessons, see Robert Lutz et al., Factors Influencing Modeling and Simulation to Inform OSD Acquisition Decisions (Alexandria, VA: Institute for Defense Analyses and Johns Hopkins University, April 2017).

38. The authors are indebted to our colleague Dr. Sue Numrich for input on discovery experimentation. See also David S. Alberts, ed., Code of Best Practice: Experimentation (Washington, DC: Department of Defense, July 2002), 21.

39. Michael Howard, “Military Science in an Age of Peace,” RUSI Journal 119, no. 1 (1974), 2.

Featured Image: Reconnaissance Marines with the 24th Marine Expeditionary Unit’s Maritime Raid Force, sourced from Force Reconnaissance Company, 2nd Reconnaissance Battalion, and embarked on the amphibious assault ship USS Iwo Jima (LHD 7), jump from a CH-53E Super Stallion during helocast training in the Gulf of Aden, May 28, 2015. The Super Stallion belongs to Marine Medium Tiltrotor Squadron 365 (Reinforced), 24th MEU. The 24th MEU is embarked on the Iwo Jima Amphibious Ready Group and deployed to maintain regional security in the U.S. 5th Fleet area of operations. (U.S. Marine Corps photo by Cpl. Joey Mendez/Released)