Tag Archives: featured

An Interview with Vice Admiral Tom Rowden on the Future of the Surface Navy

By Dmitry Filipoff

Vice Admiral Tom Rowden, Commander, Naval Surface Forces, spoke with CIMSEC about the future of surface warfare and how the surface fleet is supporting the Chief of Naval Operations’ Design for Maintaining Maritime Superiority. In particular, he discussed the ongoing development of the distributed lethality concept, how the surface warfare enterprise is evolving, and what the recently commissioned USS Zumwalt means for the future of the surface navy. This interview has been edited for length and clarity.

You are leading an effort to turn the surface navy into a more distributed force. What efforts have to be synchronized across the surface warfare enterprise to foment this transformation?

As we focus on distributed lethality I think the Distributed Lethality Task Force (DLTF) has done a phenomenal job of directing us in four areas. The first is tactics, and those tactics are focused on winning and sustaining sea control. The second is talent, and I think that is all about attracting and retaining our very best and raising the quality of performance across the force. The third is training. That’s really advanced tactical training and the development of this warrior ethos through a number of centers of excellence that we have in integrated air and missile defense, antisurface warfare, antisubmarine warfare, and antimine warfare. Finally, there’s tools, which entails offensive lethality across the board in the ships that we operate and defensive resiliency in those same ships. Tactics, talent, training, and tools, that’s really what we are focused on.

This year, three destroyers deployed as a Pacific Surface Action Group as a part of the distributed lethality concept’s development. What was learned from this deployment and what further plans do you have for refining and testing the concept?

The deployment is ongoing and we are still assessing the lessons learned. We certainly are in the process of learning about operations in the western pacific and what it means for distributed lethality and sea control. The thing I keep in mind is that when you have the opportunity to combine the lethality of three ships operating in a surface action group, the whole becomes much greater than the sum of the parts. As we look to send a PACSAG across the ocean, how do we think differently about the command and control of those ships and the utilization of their capabilities? What do we project for future surface action groups?

One of the things we are looking into is what we refer to as an upgunned ESG, which is taking a surface action group and putting it under the tactical control of an Expeditionary Strike Group that is operating forward, perhaps one with joint strike fighters. How does that tool look in the commander’s toolbox and how can we utilize that? There are a lot of opportunities to learn from the PACSAG. But as we deploy our forces, can we think differently about our independent deployers and moving them into surface action groups, providing them with a command element, and then issuing specific tasking or things to learn about how to operate those ships in a group. I think this holds great promise for the future.

What institutions are playing a key role in the development of distributed lethality and how are they contributing?

There’s a lot going on across the force. It comes back to Tactics, Talent, Training, and Tools. The Naval Surface and Mine Warfare Development Center (SMWDC) plays a big role in a lot of things we are working on. They are singled up on not only our tactics, but our training and talent as well with some influence in our tools piece, but really those three areas. On the training side of the house, I would also say the numbered fleets and certainly the Afloat Training Groups are helping with their ability to get the ships trained up.

Other folks that are contributing significantly to the development of our tactics are the numbered fleets with the large exercises we are executing such as RIMPAC. On the talent side of the house, in addition to SMWDC and the warfare tactics instructors they are developing, we are working closely with PERS41 in order to make sure from a leadership perspective that we are taking care of and properly progressing the young men and women that are coming into the surface force.

VIRGINIA BEACH, Va. (May 26, 2016) Lt. Cmdr. Dirk Sonnenberg, a graduate of Naval Surface and Mine Warfighting Development Center’s (SMWDC) Amphibious Warfare Tactics Instructor (WTI) course and winner of the course’s Iwo Jima Leadership Award, showcases the patch he and his classmates received upon graduating from the 14-week course. SMWDC is increasing the tactical proficiency of the surface warfare community by selecting elite surface warfare officers to become specialized warfighters called Warfare Tactics Instructors (WTI). (U.S. Navy photo by Mass Communication Specialist 2nd Class Jamie V.
VIRGINIA BEACH, Va. (May 26, 2016) Lt. Cmdr. Dirk Sonnenberg, a graduate of Naval Surface and Mine Warfighting Development Center’s (SMWDC) Amphibious Warfare Tactics Instructor (WTI) course and winner of the course’s Iwo Jima Leadership Award, showcases the patch he and his classmates received upon graduating from the 14-week course. (U.S. Navy photo by Mass Communication Specialist 2nd Class Jamie V)

Finally, the OPNAV staff N96 and the requirements and resource folks working for RADM Boxall, Naval Research Labs, NAVSEA, and NAVAIR are contributing greatly to the “tools” concept.

With respect to the analysis we are executing, there are several significant organizations within the Naval Postgraduate School and the Naval War College that are helping us.

How do communities outside of the surface warfare enterprise such as submarines, aviation, information warfare, and others fit into distributed lethality?

The term was kind of born with the surface force and in some of the conversations we were having back in Washington D.C. when I was working the resource side for the CNO. The concepts applied not only to other communities but across the naval force and the joint force.

Truth be told we are already moving in this direction. The retirement of the SSGNs led the submariners to develop the Virginia payload module, and I think it is going to be a significant asset as we bring it online. The networking capabilities of the F35 creates airborne distributed target networks, and with the F35B coming to our bigdeck amphibs, that’s a tremendous asset we can leverage for sea control and also bring the Marine Corps in on executing the sea control mission.

We certainly are hearing more and more about operating in a more distributed manner with it being referred to as “distributed maritime operations,” which I think is an offshoot of the concept and organizing principle of distributed lethality. I think it stretches across the fleet and the joint force as well.

CIMSEC has launched several topic weeks on distributed lethality, and two in partnership with the Distributed Lethality Task Force. How have these writings contributed to the concept’s development?

We really appreciate all of CIMSEC’s efforts to raise awareness on distributed lethality and to encourage a broad spectrum of people to think about how best to improve our Navy. I think that’s critically important. It is also important to think about how we advance the distributed lethality concept from the conceptual phase into the operational phase. I think the intellectual opportunities CIMSEC provides for a larger group of thinkers is vital, and especially for our junior officers. The JOs I get to interact with on the waterfront– what a talented and excited group of young folks. Any opportunity that we can take to leverage their thoughts, enthusiasm, and professionalism seriously raises the level of discourse and can only add to the discussion.

SAN DIEGO (Feb. 9, 2015) - Ens. Lauren Hood, Operations Intelligence Division Officer for the amphibious assault ship USS Boxer (LHD 4) is awarded her Surface Warfare Officer pin by Vice Adm. Thomas S. Rowden, Commander, Naval Surface Forces, in Boxer's wardroom. Boxer is currently undergoing a planned maintenance availability in San Diego. (U.S. Navy photo by Mass Communication Specialist 2nd Class Briana Taylor/Released)
SAN DIEGO (Feb. 9, 2015) – Ens. Lauren Hood, Operations Intelligence Division Officer for the amphibious assault ship USS Boxer (LHD 4) is awarded her Surface Warfare Officer pin by Vice Adm. Thomas S. Rowden, Commander, Naval Surface Forces, in Boxer’s wardroom. (U.S. Navy photo by Mass Communication Specialist 2nd Class Briana Taylor/Released)

Where we are deriving a ton of benefit is from thinking about some of the enablers for distributed lethality. Command and Control, electronic warfare, cryptologic operations, and unmanned vehicle integration are things that are not necessarily touched by surface warfare, but we have the opportunity to reach across a broader spectrum and bring them in. I think that’s vital, and I appreciate CIMSEC’s efforts there.

Distributed lethality is not just about offensive weapons. It is about presenting an adversary with a difficult set of operational problems. Our robust C2, the facets of electronic maneuver warfare, distributed agile logistics, all of that is necessary. All of that has been featured in your forums, and that’s really important for us.

Glad to hear it, sir, thank you. Many have raised the point that more authority should be delegated to more junior commanders in order to truly enable distributed lethality. What is your vision for the command and control of a distributed force?

I envision a scalable C2 structure, and starting with a theoretical limit of perfect sensing and perfect networking. A fleet maritime operations center is capable of centralized planning and decentralized executing of fleet operations, which certainly we’ve seen before. On the other end of the scale, I see distributed operations in a mission command, comms-denied environment. One in which our commanding officers have already practiced, and where they feel confident in the employment of their weapons systems in the pursuit of the last order they received from their commander, all the while exercising the initiative required to exploit the tactical advantage wherever it is presented. That’s really what it is all about.

A week and a half ago you spoke at the USS Zumwalt commissioning ceremony, and in your remarks you stated “She builds upon more than two centuries of fighting spirit and innovation.” What will be your immediate priorities for the Zumwalt when she arrives in San Diego, and what does the Zumwalt tell us about the future of the surface navy?

I often think about what an exciting time it is not only to be a part of our Navy, but especially a part of our surface navy. We’ve got new ships, new classes of ships, and new concepts. We are working hard to recruit and retain the most talented men and women this nation has to offer, and we are working hard to improve our tactics, our training, and our procedures.

With that as a backdrop, we are really looking forward to getting her out here. We’ve got to get her through post delivery availability, through combat systems activation and testing, and to an initial operational capability. The priority is to do everything I can to give Captain Kirk the time to train his crew across the broad spectrum with which we will be able to apply this ship.

For the future of our Navy, I think Zumwalt points to some very meaningful directions. The first I think of is stealth. We specifically designed that ship to significantly reduce its radar cross-section. How can we utilize that in future operations, how we can think differently about the utility of the ship in those operations, and how might we take that knowledge and leverage that into future ship classes that we build?

On size, she is certainly larger than a DDG, but with that increased size comes increased opportunity. Just look at the vertical launch system alone. She has the ability to take much larger missiles into her MK57 VLS than we have in the MK41 VLS. Her computing power, firepower, that huge flight deck, the new undersea warfare systems, we are going to leverage all of that. The power that ship generates — 78 megawatts of power — is more power than we have generated on any other surface ship. How do we utilize and leverage that power for future weapons systems, perhaps directed energy or railguns?

download-5
Norfolk Naval Station, VA. (Sept. 16, 2016) The land attack capabilities for Zumwalt comes from the ship’s two 155m m Advanced Gun System that can toss the lethal Long Range Land Attack Projectile nearly 60 miles at a rate of 10 per minute. (Mark D. Faram/Navy Times staff)

From the computing perspective we are looking to understand the ship’s total computing environment and how that impacts our ability to fight the ship. On the survivability piece, she has something called integrated fight-through power, which allows the ship to stay up and operational even if she sustains battle damage.

Those are some of the things that we have put on the ship, and we are gonna get her out, get her operating, get her in the hands of the sailors and Captain Kirk, and have them come back and tell us how we can leverage all of these capabilities to the maximum benefit of the fleet going forward.

Any closing thoughts?

 I see excitement in the fleet on a daily basis. I have the great privilege of being able to go out and spend time on our ships and spend time with our sailors. I was recently on the Makin Island for the penning of the new Chief Petty Officers. There’s a lot of excitement, professionalism, and enthusiasm out there. Not that we haven’t had all of those in the past, but I’ve got to tell you, when I go on board the ships today it is palpable.

I think it is a great time to be serving our country and a great time to be serving on our surface ships. I could not be prouder of all the young men and women that are serving on our ships and all the great folks on the acquisition side, requirements side, and support side that are making these ships great. We will continue to do the best we can for them, and I know they will continue to do their best for us back here at home.

Vice Admiral Thomas S. Rowden is Commander, Naval Surface Forces. A native of Washington, D.C., and a 1982 graduate of the United States Naval Academy, VADM Rowden has served in a diverse range of sea and shore assignments.

Dmitry Filipoff is CIMSEC’s Director of Online Content. Contact him at Nextwar@cimsec.org.

Featured Image: (November 6, 2014) Vice Adm. Thomas S. Rowden, commander, Naval Surface Forces and Naval Surface Force, U.S. Pacific Fleet, speaks to the crew on board amphibious assault ship USS America (LHA 6) during an all-hands call. (U.S. Navy photo by Mass Communication Specialist 1st Class Demetrius Kennon/Released)

Naval Strategy Returns to Lead the POM

By Steve Wills

Introduction

Newly appointed U.S. Navy Secretary John F. Lehman Jr. gave a signature speech at the Naval War College in Newport, RI in 1981. In his remarks Lehman hailed, “the return of naval strategy” to the forefront of the Navy’s planning.Such a message was again issued last week by Chief of Naval Operations Admiral John Richardson. While the CNO’s 18 October naval message (R 182128Z OCT 16) did not have Secretary Lehman’s dramatic turn of phrases, it is no less important and in fact is the most significant change in the role of U.S. naval strategic thinking since late 1991. The CNO’s message implements a major change in the planning and execution of the annual Navy budget statement known as the Program Objective Memorandum (POM.) For the first time since July 1991, the Navy Staff (OPNAV) Operations, Plans and Strategy (N3/N5) office will have the first input to the Navy POM building process. While this may not seem significant at first glance, it is a major course correction in Navy thinking. It could signal a return to the halcyon days of the 1980s when the Navy’s Maritime Strategy served as the service’s global blueprint for operational naval war against the Soviet Union, informing Navy programs, budgets, exercises, war games, education, training, and real world operations.

POM and Strategy Evolution Through the Cold War

The POM was created in 1970 by President Richard Nixon’s Defense Secretary Melvin Laird. It was designed as a response to what was seen as overbearing domination of service programming by the Office of the Secretary of Defense (OSD) in the Kennedy and Johnson administrations under Defense Secretary Robert S. McNamara.The POM was prepared by service rather than Defense Department analysts and was seen as a better way to allow the services to plan for their own futures. The Navy POM was controlled largely by the CNO’s OP 090 programming and budget directorate with the powerful systems analysis divison OP 96 in the lead for the development of Navy programs and associated budgets.

The system remained in place across the 1970s as a trio of influential CNOs brought about the conditions for what Navy strategist Captain Peter Swartz and naval historian John Hattendorf have called, “A renaissance in naval strategic thinking,” that occurred in the 1980s.3 Admirals Elmo Zumwalt Jr, James Holloway III, and Thomas Hayward all explored ideas for global naval strategy against a growing and more capable Soviet fleet. Admiral Zumwalt conducted a major reorganization of the Navy Staff (OPNAV) and worked to create an affordable yet capable fleet to confront its Soviet counterpart. Admiral Holloway explored differing fleet sizes and offensive concepts. Admiral Hayward had conducted significant research into a new offensive naval strategy while serving as the Pacific Fleet Commander. He further tried to reintroduce a strategic culture through the creation of a Naval War College-based, CNO strategy “think tank” called the CNO Strategic Studies Group (SSG) to create operational solutions to naval strategic problems.4 All three of these extraordinary CNOs worked to restore the Navy from its post-Vietnam War doldrums. They laid the groundwork for success in the 1980s, but faced severe policy and budget restraints and did not have optimum mechanisms to translate their naval strategy concepts into solutions acceptable to civilian leaders.

In August 1982, with a new presidential administration in power and a new CNO at the helm of the Navy, Deputy CNO Admiral Small sent an influential message to both the Navy’s strategy (OP 06) and Director of Naval  Warfare (OP 095) offices with a powerful instruction. To this end, Admiral Small (and presumably CNO Admiral James Watkins) adjusted the Navy POM process to give the Strategy branch the first “cut” on the POM building process as opposed to the OP 96 systems analysis branch. Small had been exploring this change for some months. In March 1982, he sent a memo to OP 06 Vice Admiral Sylvester “Bob” Foley in which he stated, “A review of maritime strategy may well change many of the assumptions currently explicit in our systems requirements. I guess the responsibility for this type of thinking lies somewhere between (or among) OP-06 and OP-095, but seems dormant.”The Director of Naval Warfare (OP 095) Rear Admiral W.R. Smedberg IV suggested that, “OP-06 take the lead in this action” and that the strategic setting and operational concept should be spelled out more explicitly as the backdrop of our POM development.” The Navy Programming and Budgeting Director (OP 090) Vice Admiral Carl Trost and the systems analyst division head Rear Admiral Jack Baldwin agreed with Small’s statements. Small submitted an August 1982 memo to, in his words, “Get the whole OPNAV staff moving in that direction (of strategic thinking in POM development).”6 In a 1998 letter, Small recounted that he, “had been increasingly perturbed by a lack of any relationship of POM development to any kind of maritime strategy, not only from an affordability standpoint, but the concomitant failure to challenge the assumptions made by program and platform sponsors.”7

Small’s memo set in motion a historic series of events. If strategy were to play a part in the 1983 POM process, a strategy briefing would need to be prepared in support of the Navy POM input. The OPNAV Strategic Concepts branch head (OP 603) Captain Elizabeth Wylie was ordered to prepare such a strategy appraisal. She selected Lieutenant Commander Stanley Weeks, who was assisted by Commander William Spencer Johnson from OP 605, in preparing this input. Weeks and Johnson’s document became the first iteration of the 1980s Maritime Strategy, which grew in sophistication and influence throughout the early and mid 1980s.

Strategy Adrift in the Post Cold War Era

A Maritime Strategy appraisal (CPAM) remained the first input to the POM process through 1991, but by then the global strategic system had been turned upside down. The passage of the Goldwater Nichols Act of 1986, the collapse of the Warsaw Pact, the end of the Cold War, Desert Storm operational practices, and the looming fall of the Soviet Union itself had precipitated significant changes. The Goldwater Nichols legislation had given the Chairman of the Joint Chiefs of Staff rather than the CNO control of the size and strategy of the fleet, although these powers would not be fully invoked until the accession of General Colin Powell to the chairmanship of the Joint Chiefs in 1989. The collapse of the Soviet opponent further weakened the need for the Maritime Strategy. By the spring of 1990, incoming CNO Admiral Frank Kelso was forced to concede that there was no need for a Maritime strategy in the absence of a great maritime enemy like the Soviet Union. He officially declared the 1980s Maritime strategy as “on the shelf” until again needed during his June 1990 Senate confirmation hearing as CNO.8

Between 1990 and 1991, the Maritime Strategy was replaced by the White Paper Revision, later known as “From the Sea,” as the opening assessment for the POM process. Admiral Kelso later suggested that “From the Sea” would play a similar role to that of the 1980’s Maritime Strategy in getting the Joint Staff, Congress and the Office of the Secretary of Defense to support, “The Navy’s job in the years ahead of us.”9

The new strategy was used in a method similar to its predecessor at the start of its existence. Many of its components were incorporated into a Total Force Assessment (TFA) brief scheduled for the CNO Executive Board (CEB) as a kickoff to the POM cycle by Captain Dick Diamond (OP 603 Branch Chief) to Admiral Kelso on 18 July 1991. Diamond’s brief was undercut at the last minute by an additional slide produced by RADM Dave Oliver’s OP 81 (systems analysis) office entitled, “The Coming USN Budget Train Wreck” that Oliver insisted be inserted into Diamond’s brief. Diamond recalled that Admiral Kelso did not like the littoral warfare focus of Diamond’s presentation and exploded when the OP 81 slide suggesting the Navy would shrink to less than 300 ships by 2010 was displayed.10 Admiral Kelso called Diamond into his office the next day and reversed course, stating that, “the brief was essentially correct and what you recommended is the right path ahead for the Navy…so I am going to do it.”11

Reorganizing OPNAV

The new strategy appeared to have CNO support as a POM influencer, but this condition was only temporary. Over the summer of 1992, Admiral Kelso responded with the most significant reorganization of the OPNAV staff since Admiral Zumwalt’s two decades earlier.12 In a 1994 USNI Proceedings article, Admiral William Owen, Kelso’s lead for the reorganization effort, suggested the reason for Kelso’s massive staff restructure was to implement this new strategy.13 Admiral Kelso stated in his Reminiscences of 2009 that the strategy was merely a rally point behind which Owens as the new N8 would organize programs and their funding.14

The OPNAV staff would now be organized by “N” codes along the Army-centric lines of the Joint Staff. The OP 08 programming office under the leadership of Admiral Owens was re-branded as the N8 and all Navy programmatic activity was effectively centralized under his control. Its primary management tool, the Joint Mission Assessment, was an analysis-driven document, developed by OPNAV flag officers and coordinated by the N81 (formerly OP 81) analysis office. The three star platform “barons” were downgraded to two stars and subordinated to N8.

The OP 603 office had previously conducted its strategy appraisal of the POM as part of the CNO Executive Board Review (CEB) prior to the other POM appraisals. The CEB was disestablished as part of the October 1992 OPNAV reorganization. The list of POM development assessments conducted before the 1992 reorganization includes a “White Paper Revision,” also known as “From the Sea,” described as a successor to the Maritime Strategy. Subsequent lists of POM development assessments make no mention of a strategy assessment.

The apparent demise of a direct service strategy input to the POM in 1992 was paralleled by a rise in the influence of systems and campaign analysis in POM development and management. In 1994, when recruited by CNO Admiral Mike Boorda to work in N81 analysis branch, veteran Navy operations analyst Bruce Powers said Boorda desired, “To revitalize N81 and turn it back into what OP 96 had been earlier.”15

The new analysis branch (formerly OP 81) N8 in time became even more powerful than the old OP 96 office over the next decade. In 2000, Admiral Vern Clark, a 1970s-era alumnus of the OP 96 office, succeeded Admiral Jay Johnson as CNO.16 Clark was a former Joint Staff Operations officer (J3), its director, and the first business school graduate to be appointed CNO. Clark believed that strategy properly belonged to OSD and the Joint system. His own job as a service chief was to manage the organization, training, and equipment provision to the service. Clark desired a “readiness-based” Navy; especially after the 9/11 terrorist attacks.17

Strategy Struggles

The N3/N5 (Deputy CNO for Plans, Policy and Operations) office attempted to get back into the business of influencing the POM in the 1990s and in the 2000s. In 1994, N3/N5 RADM Phillip Dur and his N51 Captain Joe Sestak attempted to improve the 1992 “From the Sea” White Paper with a successor document entitled “Forward From the Sea.” While it had some initial success, it did not achieve any influence in POM development since it was still focused on “blue water” programs and did not “Script a convincing story about how a littoral strategy works.”18 It was further criticized as just a repeat of the Navy’s Cold War presence operations and provoked backlash from the Army and Air Force due to its, “Parochial focus on uniqueness of naval forward presence.”19 “Only “boots on the ground,” combined with robust land-based (as opposed to carrier-based,” aviation could actually influence others.20 Although useful for two years in shaping the Navy POM, it did not achieve lasting influence.21 Further attempts by the N3/N5 office to influence the POM including a Navy Operational Concept, and the Navy Strategic Planning Guidance for POMs 02 and 03 were short-lived and failed to develop lasting influence on the budget cycle. They were greatly overshadowed by Department of Defense strategic initiatives such as the First Quadrennial Review (QDR) and increasing attempts at joint operations.22

In 2002, Admiral Clark told Vice Admiral Kevin Green, the incoming N3/N5 that the Navy did not need a “strategy,” as it already had one and it was called the POM.23 Admiral Clark assigned control of the Navy’s 30-year shipbuilding plan to N81 in 2000.24 The N81 office was also instrumental in developing the Global Concept of Operations (CONOPS) for Admiral Clark’s “Sea Power 21” concept.25

The decade of the 2000s was more successful in terms of re-asserting the influence of strategy on the OPNAV staff. Admiral Mike Mullen became CNO in 2005. Vice Admiral John Morgan was N3/N5 from 2004-2008 and had more success than Vice Admiral Green in pushing strategy documents to a wider audience, but was still outpaced by N81 in terms of POM influence. The Navy Operating Concept for Joint Operations, written by N513 (the strategy office of N3/N5) by contrast was little cited in either POM documents or within the press.

Succeeding strategy documents were also ineffective. The Navy Strategic Plan in support of POM 08 (2006) was signed out six months too late to be of significant influence on its intended POM cycle.26 The Strategic Plan for POM 10 (2007) had some influence in the development of the 2007 Cooperative Strategy for 21st Century Seapower. It was deliberately targeted at Navy Department programmers supporting POM development.27 It had extensive support from N81 including influential officers such as Commander Bryan Clark and Captain John Yurchak to ensure it “fit with the OPNAV POM process.”28 However, this document was Secret only and did not get wide distribution as a result. Unfortunately, the POM 10 Strategic planning effort was lost to a degree in the turmoil of the end of the Bush administration during which operations in Iraq and Afghanistan dominated Defense Department thinking.29 It reflected current and near-term Navy programming already in place rather than attempted to influence future efforts. It did not include the Marine Corps, and had no mechanism to secure OPNAV support, as did the N8 /N81 POM development process.30

Admiral Morgan’s greatest triumph was perhaps the 2007 Cooperative Strategy for 21st Century Seapower. It was championed by CNO Admiral Mullen and drafted by N3/N5 staff member Commander Bryan McGrath, and writers from the other sea services. The 2007 Cooperative Strategy was designed as a tri-service effort in support of POM 12.31 The document had widespread influence in the wider U.S. and international naval community, but again failed to have a significant impact on its intended POM target. Despite its influence, the 2007 document had no direct connection with POM development, unlike the pre-1992 Maritime Strategy CPAM inputs to the POM process.32 The distinct lack of a formal relationship between strategy and the programming process allowed Navy programmers to ignore strategic input from 1992 through the beginning of the second decade of the 21st century.

By contrast, the N81 analysis branch’s formal connection to the programming process has allowed it wide influence.33 Since 2000, the 30-year shipbuilding plan has in effect served as the Navy’s de facto strategy document. Its key supporting element is the Naval Force Structure Assessment (FSA). The FSA is described in OPNAV Instruction 3050.27 (12 February 2015), as a tool that, “determines long-term Navy force structure objectives to support a global posture of distributed mission-tailored ships, aircraft, and units capable of regionally concentrated combat operations and peacetime theater security cooperation efforts.”34 The 2012 FSA was used to, “determine a post-2020 requirement for 306 ships in the battle force and emphasized forward presence while re-examining resourcing requirements for operational plans and defense planning scenarios.”35

Back to the Future

It now appears that Admiral Richardson intends to reverse the last 25 years of total N8-dominated POM development. The POM will now be a three-phase process with the Deputy Chief of Naval Operations (DCNO) for Operations, Plans and Strategy (N3/N5) as the supported commander for the first phase; the N9 Warfare Systems office in charge of the second requirements integration phase, and the N8  leading the third resource integration phase effort. POMs will begin three months earlier than usual in order to ensure “strategic deliberation.” There will be no separate Resource Program Sponsor Proposals (RPSPs) in this new, more transparent POM environment. In addition, billets from the CNO’s own OPNAV “think tank,” office of 00K and the N81 Quadrennial Defense Review Division have been moved to the N50 divison (under N3/N5) to create a powerful new Strategy division capable of managing the first phase of the new POM process. The formal connection of the N50 office to the programming process appears to ensure that the influence of the inputs it creates will not be lost in bureaucratic channels as in the last 25 or so years. The final goal in the words of the message is, “a strategy-based, fiscally balanced, and defendable Navy Program for submission to OSD, which appropriately implements OSD fiscal and programming guidance, addresses SECNAV and CNO priorities, and achieves the best balance of strategic guidance as provided in the CNO guidance.”

Conclusion

Admiral Richardson’s new POM process is a bridge from the days of the 1980s Maritime Strategy across a quarter century of force structure management, and pseudo-strategy to a new era of great power competition. This process is perhaps the beginning a new global maritime strategy with which the Navy can confront the collective and growing maritime power of the Chairman’s “4+1” combination of potential threats (Russia, China, Iran, North Korea, and terrorism.) Admiral Richardson’s change to the Navy’s POM process is perhaps again the beginning of another golden age of American naval strategy.

Steve Wills is a retired surface warfare officer and a PhD candidate in military history at Ohio University. His focus areas are modern U.S. naval and military reorganization efforts and British naval strategy and policy from 1889-1941. 

1. Peter M. Swartz with Karin Duggan, U.S. Navy Capstone Strategies and Concepts, 1981-1990, Strategy, Policy, Concept and Vision Documents, Alexandria, VA, The CNA Corporation, December, 2011, p. 21.

2. Richard A. Hunt, Melvin Laird and the Foundations of the Post-Vietnam Military, 1969-1973,  Washington D.C, The Office of the Secretary of Defense,  Historical Office, The Secretaries of Defense Historical Series, Volume VII, Erin R. Mahan, General Editor,, pp. 16, 17.

3. John B. Hattendorf and Peter M. Swartz, U.S. Naval Strategy in the 1980’s. Selected Documents, Newport R.I, The United States Naval War College, The Newport Papers #33, 2008, p. 4.

4. John Hanley, “Creating the 1980’s Maritime Strategy and Implications for Today,“, Newport, R.I., The United States Naval War College Review, Spring, 2014, Volume 67, No 2, p. 15.

5. John B. Hattendorf, The Evolution of the U.S. Navy’s Maritime Strategy, 1977-1986, Newport, R.I, The United States Naval War College Press, The Newport Papers #19, 2003,  pp. 66-68.

6. Ibid.

7. Fax letter from Admiral William Small USN (ret) to Captain Peter M. Swartz, USN (ret), 02 October 1998, Arlington, VA, The Personal and Professional Papers of Captain Peter M. Swartz, USN (ret), used with permission.

8. “The Nomination of Admiral Frank B. Kelso, Jr USN, to be Chief of Naval Operations,” Hearing before the Committee of the Armed Services, The United States Senate, Second Session of the One Hundred First Congress, 14 June, 1990, pp. 326, 327.

9. Frank B. Kelso II and Paul Stilwell, The Reminiscences of Admiral Frank B. Kelso II U.S. navy (Retired), Annapolis, Md, The United States Naval Institute Press, 2009, p. 687.

10. Email from Captain Richard Diamond, USN (ret) to Dr. John Hattendorf, Naval War College, subject “Paper Review Status” (unpublished narrative of the events leading up to the September 1992 publication of “From the Sea”), 09 September 2006, Filed jointly inThe United States Naval War College, The Naval Historical Collection, The papers of Dr. John Hattendorf, and in the Professional papers of Captain Peter M. Swartz, USN (ret), 1991 “The Way Ahead” file, used with special permission of Dr. John Hattendorf, Captain Swartz and Captain Richard Diamond, USN (ret).

11. Ibid.

12. William A. Owens, High Seas, The Naval Passage to an Uncharted World, Annapolis, MD, The United States Naval Institute Press, 1995, p. 5.

13. William Owens, “The Quest for Consensus,” Annapolis, MD, The United States Naval Institute Proceedings, Vol 120/5/1095, May 1994, pp. 69, 70.

14. Frank B. Kelso II and Paul Stilwell, The Reminiscences of Admiral Frank B. Kelso II U.S. navy (Retired), p. 688.

15. Bob Sheldon and Michael Garrambone, “Military Operations Research Society (MORS) Oral History Project Interview with Mr. Bruce F. Powers,” Military Operations Research, V21 N#2,  2016, doi 10.5711/10825983212107, p. 118.

16. Wayne P. Hughes, Jr., (2002) Navy Operations Research. Operations Research 50(1):103-111. http://dx.doi.org/10.1287/opre.50.1.103.17786,  p. 107.

17. Ronald Ratclift, “CNO and OPNAV Reorganization,” In  David A. Williams (ed.), Case Studies in Policy Making and Implementation. 6th ed,  Newport, RI, The United States  Naval War College Press, 2002 , p.p. 326-328.

18. Edward Rhodes, “…From the Sea and Back Again, Naval Power in the Second American Century,” Newport, RI, The United States Naval War College Review, Vol LXX, No.2, Sequence 366, Spring 1999, p. 32.

19. Peter M. Swartz with Karin Duggan, U.S. Navy Capstone Strategies and Documents, 1991-2000, Alexandria, VA, The CNA Corporation, D0026416.A2/Final, March 2012, p. 93.

20. Ibid.

21. Ibid, p. 95.

22. Ibid, p. 102.

23. Peter Haynes, Toward a New Maritime Strategy, American Naval Thinking in the Post Cold War Era, Annapolis, MD, The United States Naval Institute Press, 2015,  pp. 227, 228.

24. Ronald O’Rourke, “Navy Force Structure and Shipbuilding Plans: Background and Issues for Congress,” Washington D.C., The Congressional Research Service (CRS), 7-5700, 12 June 2015, p. 8.

25. Peter M. Swartz with Karin Duggan, U.S. Navy Capstone Strategies and Documents, 200-2010, Strategy, Policy, Concept and Vision Documents, Alexandria, VA, The CNA Corporation, D0026241.A2/Final, p. 27.

26. Ibid, p. 101.

27. Ibid, p. 127.

28. Ibid, p. 136.

29. Ibid, p. 129

30. Ibid, p. 138

31. Ibid, p. 166.

32. Ibid, p. 189.

33. James A. Russel, James J. Wirtz, Donald Abenheim, Thomas Durrell-Young, and Diana Wueger, “Navy Strategy Development in the 21st Century,” Monterey, CA, The United States Navy Postgraduate School, The Naval Research Program, #FY14-N3/N5-001, June 2015, p. 4, electronic resource, https://www.hsdl.org/?view&did=768350, last assessed 25 October 2016.

34. “OPNAV Instruction 3050.27, Force Structure Assessments,” Washington D.C., The Office of the Chief of Naval Operations, 12 February 2015, p. 1, electronic resource, https://doni.daps.dla.mil/Directives/03000%20Naval%20Operations%20and%20Readiness/03-00%20General%20Operations%20and%20Readiness%20Support/3050.27.pdf, last assessed 5 October 2016.

35. “Report to Congress on the Annual Long Range Plan for Construction of Naval Vessels for Fiscal year 2016,” Washington D.C., The Office of the Chief of Naval Operations, The Deputy Chief of Naval Operations (Integration of Capabilities and Resources,) March 2015, p. 7. Electronic resources, https://news.usni.org/wp-content/uploads/2015/04/FY16-30-Year-Shipbuilding-Plan.pdf, last assessed 5 October 2016.

Featured Image: ARLINGTON, Va. (Jan. 12, 2016) Chief of Naval Operations (CNO) Adm. John Richardson delivers remarks during the 28th annual Surface Navy Association (SNA) National Symposium. (U.S. Navy photo by Mass Communication Specialist 1st Class Nathan Laird/Released)

Autonomous Warfare: An Operational Concept to Optimize Distributed Lethality

By LT Coleman Ward

Introduction

To better meet today’s force demands, [we must] explore alternate fleet designs, including kinetic and non-kinetic payloads and both manned and unmanned systems. This effort will include exploring new naval platforms and formations – again in a highly “informationalized” environment – to meet combatant commander needs.

– Admiral John Richardson in A Design for Maintaining Maritime Superiority

Today’s military operating environment is more complex than ever. While the principles of warfare have remained relatively unchanged throughout history, the development of advanced military capabilities and employment of unconventional styles of warfare increasingly challenge the way commanders are thinking about future conflict. Potential adversaries are further complicating the operating environment through various anti-access/area denial (A2/AD) mechanisms. While many countries are developing such capabilities, this article will focus primarily on the threat of the People’s Republic of China (PRC’s) maritime development. The PRC is rapidly improving its air, surface, and subsurface platform production as it continues its quest for exclusive control of untapped natural resources within the “nine-dash line” region.1 Additionally, the PRC is equipping these platforms with improved weapons that can reach further and cause more damage.2 As a result, the U.S. Navy will assume greater risk when operating in complex A2/AD environments such as the Western Pacific. To mitigate this risk, the U.S. Navy is developing innovative warfighting concepts that leverage technologies and assets available today. The incorporation of unmanned systems into maritime domain operations provides one example where the U.S. Navy is making significant progress. Another example is the inception of a new surface warfighting concept called Distributed Lethality.

In January 2015, Vice Admiral Thomas Rowden (Commander U.S. Naval Surface Forces) and other members of the surface warfare community’s higher leadership formally introduced the opening argument for how the Surface Navy plans to mitigate the A2/AD challenge in an article titled “Distributed Lethality.”3 In this inaugural piece, the authors argue, “Sea control is the necessary precondition for virtually everything else the Navy does, and its provision can no longer be assumed.”4 The “everything else” corresponds to promoting our national interests abroad, deterring aggression, and winning our nation’s wars.5 At its core, Distributed Lethality (DL) is about making a paradigm shift from a defensive mindset towards a more offensive one. To enable DL, the U.S. Navy will increase the destructive capability of its surface forces and employ them in a more distributed fashion across a given theater of operation. 

DL shows promise in executing the initiatives provided in the Chief of Naval Operations’ Design for Maintaining Maritime Superiority in the years to come.6 However, as the U.S. Navy continues to invest in promoting DL, there is a danger that improper fusion of this new operating construct with the foundational principles of war could lead to a suboptimal DL outcome.7 To optimize the combat potential inherent to DLin an A2/AD environment, the Navy must develop and apply the concept of “Autonomous Warfare.” Autonomous Warfare addresses both enabling decentralized, autonomous action at the tactical level through careful command and control (C2) selection at the operational level and further incorporating unmanned systems into the Navy’s maritime operating construct. A flexible C2 structure enabling autonomous action supported by squadrons of unmanned systems optimizes DL and ensures its forces will deliver the effects envisioned by this exciting new concept in the most challenging A2/AD environments. DL advocates put it best in saying that “we will have to become more comfortable with autonomous operations across vast distances.”8 This paper will first examine why DL is an appropriate strategy for countering A2/AD threats before developing the main argument for Autonomous Warfare. This paper concludes by examining how the combined effect of autonomous C2 and aggressive implementation of unmanned systems will achieve the desired results for Autonomous Warfare as it applies to DL, followed by a series of recommendations that will assist with implementing this new idea.

Why Distributed Lethality?

“Naval forces operate forward to shape the security environment, signal U.S. resolve, protect U.S. interests, and promote global prosperity by defending freedom of navigation in the maritime commons.”9 During war, one of the Navy’s principal functions is to gain and maintain sea control to facilitate air and ground operations ashore. An adversary’s ability to execute sea denial makes the endeavor of exercising sea control increasingly challenging.   A key driver behind DL is countering advances in A2/AD capability, a specific sea denial mechanism, which inhibits the Navy’s capacity to operate in a specific maritime area.10

A2/AD is a two-part apparatus. Anti-access attempts to preclude the entrance of naval forces into a particular theater of operation. For example, the threat and/or use of anti-ship cruise and ballistic missiles can hold surface vessels at risk from extended ranges.11 The PRC’s People’s Liberation Army Navy (PLAN) is one of the many navies that deploy various anti-ship cruise missiles (ASCMs), out of a global arsenal of over 100 varieties that can reach nearly 185 miles.12 Of its anti-ship ballistic missiles (ASBMs), the PRC’s renowned “carrier killer” (DF-21D), with a range of 1000 plus miles, is generating cause for concern from an anti-access perspective.13 Additionally, submarines operating undetected throughout a given area of operation (AO) can deter surface forces from entering that area without significant anti-submarine warfare (ASW) capability. On the other hand, area denial seeks to prevent an adversary’s ability to maneuver unimpeded once a vessel has gained access to an area.14 While employment of the aforementioned missiles poses a threat in a combined A2/AD capacity, the PRC’s shipbuilding trend is triggering additional alarms from an area denial perspective. A recent workshop facilitated by the Naval War College’s China Maritime Studies Institute (CMSI) highlighted that the PRC has surged its shipbuilding efforts more than ten times over from 2002 to 2012 and will likely become the “second largest Navy in the world by 2020” if production continues at this pace.15 Indeed, the PRC has generated and continues to produce significant capacity to practice A2/AD and maintains a formidable shipbuilding capability. These observations are just a few amongst a host of many that spark interest in shifting American surface forces toward a DL-focused mindset.

One might ask, “How does DL help mitigate these A2/AD concerns?” Ever since carrier operations proved their might in the Pacific theater during World War II, U.S. naval surface combatants have principally acted in defense of the aircraft carrier. Essentially, the surface force relies predominantly on the firepower wrought by the carrier air wing, while other surface ships remain relatively concentrated around the carrier and defend it against enemy threats from the air, surface, and sub-surface. A well-developed A2/AD operational concept married with a diverse and sophisticated array of systems is advantageous against this model for two reasons: that adversary could hold a limited number of high value units (the carriers) at risk with only a small number of ASBMs, while the imposing navy could only employ a fraction of its offensive capability due to a necessary focus on defensive measures. DL addresses both concerns by deploying progressively lethal “hunter-killer” surface action groups (SAGs – more recently referred to as Adaptive Force Packages) in a distributed fashion across an area of operation (AO). By doing so, the DL navy will provide a more challenging targeting problem while offering the commander additional offensive options.16 DL shifts the focus of the Navy’s offensive arsenal from its limited number of aircraft carriers to the surface navy as a whole.

Potential Shortcomings

DL addresses the challenges of operating in an A2/AD environment by dispersing offensively focused surface combatants across the theater. To be effective, however, the operational commander must assign an appropriate C2 structure for DL forces. The DL operating concept could rapidly dissolve through the development and implementation of complex command and control structures. Furthermore, inadequate use of unmanned systems presents an additional potential shortcoming to the effective application of DL. While the consequences of these shortcomings would not be cause for instantaneous failure, they could create adverse second and third order effects and result in deterioration of the DL concept.

Command and Control

Effective C2 is the cornerstone of the successful execution of any military operation. Service doctrine aids in establishing the proper balance between centralized and decentralized C2. The Naval Doctrine Publication 1 for Naval Warfare defines C2 as “the exercise of authority and direction by a properly designated commander over assigned and attached forces in the accomplishment of the mission.”17 Further, the Joint Publication for C2 and Joint Maritime Operations highlights that a clear understanding of commander’s intent should enable decentralized execution under the auspices of centralized planning.18 Instituting the appropriate C2 structure based on the mission at hand and composition of employed forces helps achieve maximum combat utility while minimizing the need to communicate. This is particularly important when the operational commander has cognizance over a large number of forces and/or when the enemy has degraded or denied the ability to communicate. As the absence of a notional C2 architecture for Adaptive Force Packages (AFPs) at the operational level represents a significant gap in the DL concept, this paper will provide a traditional Composite Warfare Commander (CWC) approach to commanding and controlling AFPs, followed by a potential solution through the lens of Autonomous Warfare.19 The intent is to show that thinking about AFPs as autonomous units will uncover innovative ways to assign C2 functions and responsibilities amongst DL forces.

Unmanned Systems

The proper employment of unmanned systems will prove equally critical in developing the design for Autonomous Warfare as it relates to DL.20 Increasing the offensive capability of smaller groups of warships is one of DL’s main functions (if not the main function). A key enabler to this is the ability to provide ISR-T in a manner that reduces risk to the organic vessels. The concern is that targeting requires the ability to detect, track, and classify enemy vehicles – which oftentimes requires emission of electronic signals that will alert the enemy. Unmanned systems have the ability to provide ISR-T while reducing the risk for organic vessels to reveal their location. Autonomous Warfare will leverage the use of unmanned systems in all three maritime domains (air, surface, and sub-surface). Anything less would unnecessarily limit the potential for delivering maximum offensive firepower while minimizing risk to the organic platforms. Furthermore, critics should note that the U.S. Navy’s adversaries are making similar advances in unmanned systems.21 The bottom line is that underutilization of unmanned systems will be detrimental to DL. The effectiveness of DL as an operational concept depends on the effective employment of unmanned systems.

Providing A Frame of Reference

The following hypothetical situation offers a frame of reference for the remainder of the Autonomous Warfare argument.22 The goal is to show that Autonomous Warfare will optimize DL employment in a scenario where multiple BLUE AFPs must operate in the same AO against multiple RED force SAGs and other RED forces.23

screenshot_12
Figure One: A notional scenario for DL24

The area depicted in Figure 1 represents the AO for the given scenario. Country GREY is an abandoned island and has an airfield that BLUE forces want to capture to facilitate follow-on operations against RED. The Joint Force Maritime Component Commander (JFMCC) receives the task of capturing the airfield. As such, he establishes two objectives for his forces: establish sea control on the eastern side of the island (indicated in yellow) to support an amphibious landing in preparation for seizing the airfield, and establish sea denial on the western side of the island (indicated in orange) to prevent RED from achieving the same.

BLUE’s Order of Battle (OOB) consists of one carrier strike group (CSG), one expeditionary strike group (ESG), and three AFPs. Each AFP is comprised of an ASW capable Littoral Combat Ship (LCS), a Flight III Arleigh Burke-class destroyer, and a Zumwalt-class destroyer. Together, each AFP is capable of the full range of offensive and defensive measures needed to defeat enemy targets in each of the three maritime domains.25 RED’s OOB consists of one CSG, three SAGs, and two diesel-electric submarines. RED has a more difficult targeting problem than if BLUE elected to concentrate its forces, since BLUE distributed them across the AO utilizing multiple AFPs capable of delivering offensive firepower in all three traditional warfare domains. How then should BLUE best establish its C2 structure? Will that C2 structure continue to function while operating under emissions control (EMCON) and in the event RED is able to degrade or deny BLUE communications? What roles should unmanned systems play in optimizing ISR-T while minimizing risk to the organic platforms? By developing and applying the concepts of Autonomous Warfare, BLUE will operate with a C2 construct that enables more autonomous action at the lower levels. Additionally, BLUE will leverage the use of unmanned systems, relieving the stress of ambiguity in a communications denied environment.

A Traditional Approach for Applying the CWC Concept to DL

One could argue that AFPs operating under the DL construct should follow a traditional CWC C2 structure, which provides a counter-argument for the Autonomous Warfare approach. The CWC concept attempts to achieve decentralized execution and is defensively oriented. The composite warfare commanders direct the various units of a task force on a warfare-specific basis.26 By delegating oversight of each warfare area to lower levels, the command structure avoids creating a choke point at the task force commander level (the CWC). This configuration is “structurally sound – if not brilliant” for its inherent capacity to simplify the offensive and defensive aspects of maritime warfare down to each warfare area.27 AFPs employed in the scenario described above would then operate under the cognizance of the different warfare commanders on a warfare-area basis. These AFPs are simply groups of disaggregated forces forming a distributed network that would otherwise maneuver as a concentrated assembly around the carrier.

Figure 2: Traditional CWC Operational C2 Structure for a DL Task Force
Figure 2: Traditional CWC Operational C2 Structure for a DL Task Force

Putting the given scenario into action and using the C2 structure depicted in Figure 2, to what degree are the APFs enabled to achieve the given objectives? BLUE AFPs are stationed as shown in Figure 1 and will attack any RED forces attempting to contest BLUE’s sea control in the yellow box. BLUE also has a continuously operating defensive combat air (DCA) patrol stationed west of the sea denial box to prevent any RED advancements towards island GREY. Just as BLUE forces get into position, RED attempts to form a blockade of the island by sending two SAGs, each escorted by a submarine, around the north and south ends of the island. The first indication of a RED attack comes from a synchronized ASCM salvo from unidentified targets (they were fired from RED’s submarines) followed by radar contact on the RED SAGs from BLUE UAVs providing ISR-T. BLUE’s distributed AFPs, fully enabled by commander’s intent, are capable of self-defense and defeating the RED forces.

Close coordination with the warfare commanders is not required. Each AFP commander understands that in order to maintain sea control to the east, he must dominate in the air, sub-surface, and on the surface. The CWC remains informed as the situation develops and the warfare commanders provide additional guidance for regrouping following the destruction of enemy threats. Thus, a traditional CWC approach to commanding and controlling AFPs provides the opportunity for centralized planning with decentralized execution with respect to DL. Further efforts to decouple the C2 of the AFPs from the task force as a whole could jeopardize unity of effort amidst a complex maritime contingency. AFPs should not be totally self-governing since “uncontrolled decentralized decision-making is just as likely to result in chaos on the battlefield” as no command and control at all.28

An Autonomous Warfare Approach for DL Command and Control

The traditional CWC approach for DL C2 works in this case only because the given scenario is relatively simple. Uncertainty and adversity (often times referred to as fog and friction) are problems that commanders will enduringly have to overcome in wartime. “A commander can no more know the position, condition, strength, and intentions of all enemy units than the scientist can pinpoint the exact location, speed, and direction of movement of subatomic particles.”29 The best he can do is generate an estimate of the situation based on the information available. In the previous scenario, RED’s COA was generic; BLUE should anticipate this type of COA to a degree, relative to RED’s overall plan of attack. Replaying the scenario with two slight yet profound modifications will show that we should not think of the traditional CWC C2 concept as a universal solution. An Autonomous Warfare approach will simplify managing the fog and friction of war from an operational C2 perspective and maximize AFP combat potential.

Assume the forces available and assigned objectives on each side are unchanged. In this case, RED brings to bear more of its A2/AD capabilities, including jamming BLUE’s communications network. Additionally, RED has sufficient ISR capabilities to determine the location and composition of BLUE’s AFPs. As a result, RED concentrates its forces to the north in an attempt to annihilate BLUE’s AFPs in series. The AFP to the north is now overwhelmingly outmatched. Similar to the previous scenario, BLUE’s first indication of a RED attack is a salvo of ASCMs fired from RED’s submarines. As a result, the LCS is damaged to the extent that it provides no warfare utility. Because communications are jammed, the remaining AFP forces cannot communicate with the CWC and his warfare commanders on the carrier to receive guidance on how to proceed. How does the affected AFP protect itself with the loss of its primary ASW platform? Does the traditional C2 structure allow the affected AFP to coordinate directly with the adjacent AFP for re-aggregation? Collectively, the remaining AFPs still offer the commander adequate capability to thwart the RED attack. This is not to say that Autonomous Warfare completely nullifies the principles of the CWC concept. Autonomous Warfare simply optimizes the principles behind the CWC concept for DL.30

The following is an analysis of how an Autonomous Warfare approach to C2 for AFPs optimizes the combat potential that DL offers – especially in an A2/AD environment. A notional Autonomous Warfare DL C2 structure is provided in Figure 3. Each AFP would have an assigned AFP commander and designated alternate. Tactical decision-making would occur at the AFP level. Communications requirements would be drastically reduced. The delegated C2 structure obviates the need for dislocated command and control – AFPs under the auspices of the CSG. Thus, the “search-to-kill decision cycle” is completely self-contained.31 This degree of autonomy avoids the particular disadvantages of centralized command indicated in the previous example. Autonomous Warfare enables the AFP commander to make best use of his available forces based on the tactical situation and in pursuit of the assigned objectives. Furthermore, Autonomous Warfare prioritizes local decision-making founded on training, trust, mission command, and initiative rather than top-down network-centric command and control.32

Figure 3: Autonomous Warfare C2 Structure for a DL Task Force.
Figure 3: Autonomous Warfare C2 Structure for a DL Task Force

There is an additional significant advantage to having a more autonomous C2 structure. Although the operational commander could assign each AFP a geographic area of responsibility, they could combine forces and disagreggate as necessary in the event of a loss or an encounter with concentrated enemy forces. In the second scenario above, two AFPs could coordinate directly with each other to counter the larger enemy compliment. They could avert the challenges and ambiguity of reaching back to the centralized commanders altogether as long as they maintained accountability for their assigned areas of responsibility. In the case where the LCS was eliminated, the AFP commanders should have the autonomy to adapt at the scene to accomplish the objective without seeking approval for a seemingly obvious response to adversity.

Another reason why a more flexible, autonomous C2 structure is imperative for DL forces is that there is no “one-size-fits-all” AFP.33 The operational commander may assign different combinations of platforms based on the assets available and the given objectives. The harsh reality of war is that ships sink. The doctrine in place must allow for rapid adaptation with minimal need to communicate to higher authority. The Current Tactical Orders and Doctrine for U.S. Pacific Fleet (PAC-10) during World War II captures this notion best: “The ultimate aim [of PAC-10 was] to obtain essential uniformity without unacceptable sacrifice of flexibility. It must be possible for forces composed of diverse types, and indoctrinated under different task force commanders, to join at sea on short notice for concerted action against the enemy without interchanging a mass of special instructions.”34

Optimizing DL with Unmanned Systems

The aggressive employment of unmanned systems is the second feature of Autonomous Warfare through which the U.S. Navy should optimize DL. “It is crucial that we have a strategic framework in which unmanned vehicles are not merely pieces of hardware or sensors sent off-board, but actual providers of information feeding a network that enhances situational awareness and facilitates precise force application.”35 While there are many applications for unmanned systems, Autonomous Warfare exploits the information gathering and dissemination aspects to increase the lethality of organic platforms. By enhancing the capacity to provide localized and stealthier ISR-T using unmanned systems, AFPs will assume less risk in doing the same and can focus more on delivering firepower.36 The examples provided below solidify this assertion.

Submarines provide a healthy balance of ISR and offensive capabilities to the operational commander. A submarine’s ability to remain undetected is its foundational characteristic that gives friendly forces the advantage while “complicating the calculus” for the enemy.37 There is a significant tradeoff between stealth and mission accomplishment that occurs when a submarine operates in close proximity to its adversaries or communicates information to off-hull entities. By making use of UUVs, AFPs can still rely on stealthy underwater ISR-T while allowing the organic submarine to focus on delivering ordinance. In the given scenario, a small fleet of UUVs could be stationed west of the island and provide advanced warning of the approaching enemy forces. If traditional manned submarines took on this responsibility, they would likely have to engage on their own as the risk of counter-detection might outweigh the benefits of communicating. AFPs themselves could remain stealthy and focus on efforts to defeat the enemy.

While UUVs provide additional support in the undersea domain, UAVs are potential force multipliers in the DL application for two additional reasons. A cadre of unmanned aircraft could provide valuable ISR-T and line-of-sight (LOS) communications to further enable AFP lethality.38 From an ISR-T perspective, AFPs could deploy UAVs to forward positions along an enemy threat axis to provide indications and warning (I&W) of an advancing enemy target or SAG. Their smaller payloads means they can stay on station longer than manned aircraft, and they eliminate the risk of loss to human life. Additionally, the benefits of providing LOS communications are numerous. LOS communication is particularly advantageous because it eliminates the need to transmit over-the-horizon, which becomes exceedingly risky from a counter-detection perspective as range increases.39 A UAV keeping station at some altitude above the surface could provide LOS communications capability among various vessels within the AFP that are not necessarily within LOS of each other. Further, a UAV at a high enough altitude may afford the opportunity for one AFP to communicate LOS with an adjacent one. The level of autonomy these AFPs can achieve, and therefore lethality, only improves as battlespace awareness becomes more prolific and communication techniques remain stealthy.

actuvdryrunbridge
Featured Image: The prototype of DARPA’s ACTUV, shown here on the day of its christening. (Photo: DARPA)

Just as UUVs and UAVs offer significant advantages to Autonomous Warfare, there is great value in the application for USVs in the surface domain. Take for instance the Defense Advanced Research Projects Agency’s (DARPA) anti-submarine warfare (ASW) Continuous Trail Unmanned Vessel (ACTUV). This stunning new technology has the capability of tracking the quietest diesel-electric submarines for extended periods.40 If this type of vessel was available to provide forward deployed ASW capabilities in the second scenario described above, the likelihood of RED submarines attacking BLUE would have diminished. While this particular USV would operate primarily for ASW purposes, it is completely feasible that the designers could equip the ACTUV with radar capabilities to provide additional ISR against air and surface threats. USVs simply provide an additional opportunity for operational commanders to provide ISR-T to weapons-bearing platforms.

The Combined Effect

The true value intrinsic to Autonomous Warfare stems from the combined effect of an appropriate C2 structure for DL that enables autonomous action and the force multiplier effect the operational commander realizes from unmanned systems. Distributed Lethality has serious potential for raising the status of our surface force as a formidable contender to one of deterrence. In an age where leaders measure warfighting capacity in technological advantage, it is refreshing to see an emerging concept that applies innovative thinking to warfighting techniques with the Navy we have today. A more autonomous C2 structure at the operational level will afford DL forces the flexibility to rapidly deliver offensive measures as contingencies develop. “By integrating unmanned systems in all domains, the U.S. Navy will increase its capability and capacity,” especially with respect to DL.41

Recommendations

It will take both time and effort to achieve an optimized Distributed Lethality construct through Autonomous Warfare. The following recommendations will assist in making this vision a reality:

1. There is risk that by disconnecting the AFPs from the CSG from a C2 perspective, the CSG becomes more vulnerable and unnecessarily sacrifices situational awareness. The Surface Warfare Directorate) N96 and the Distributed Lethality Task Force should further evaluate the tradeoffs associated with implementing a more autonomous C2 structure to DL at the operational level. Additionally, this paper proposes an operational C2 structure for DL. The conclusions derived from this paper should support further development of tactical level C2 for DL.

2. While many of the unmanned systems mentioned above are currently operational or under development, there is limited analysis of how to employ them in a Distributed Lethality environment. OPNAV N99 (Unmanned Warfare Systems), working in conjunction N96 and the DL Task Force, should consider incorporating unmanned systems within the DL concept as outlined above.

3. The U.S. Navy should conduct wargames and real world exercises to both validate the strengths of Autonomous Warfare and identify areas for improvement. Wargames will help refine Autonomous Warfare from a developmental approach. Naval exercises have two benefits: realistic testing provides proof of concept with the same force that will go to war. They also provide the opportunity to practice and inculcate new concepts.

4. Doctrine should begin to foster a culture of Autonomous Warfare throughout the U.S. Navy. The battlefield is becoming more volatile, uncertain, complex, and ambiguous. The more we enable our highly trained and experienced officers to think and act autonomously, the greater combat potential the Navy will realize. Submarines, by nature, operate this way on a continuous basis. Other warfare communities will benefit from having the ability to operate in a more autonomous manner. As Autonomous Warfare represents a paradigm shift from a “connected force” towards a more autonomous one, the U.S. Navy must understand and embrace Autonomous Warfare before implementing it.

Conclusion

Distributed Lethality’s impending contribution to the joint force depends on its ability to maintain flexibility. An autonomous C2 structure allows for localized assessment and force employment, rapid adaptation in the face of adversity, and the ability to combine forces and re-aggregate as the situation dictates. Aggressive employment of autonomous vehicles only enhances these principles. Unmanned systems operating across the maritime domains will provide valuable ISR-T and facilitate localized decision-making, while minimizing risk to the organic platforms. By providing a means of stealthy communication among ships within an AFP or even between adjacent ones, Autonomous Warfare fosters an environment of secure information sharing. Less need to reach back to a command node means that DL forces can spend more time taking the fight to the enemy and less time managing a complicated communications network.

Maritime warfare is a complex process. Characterized by uncertainty and ambiguity, no weapon, platform, or operating concept will eliminate the fog and friction of war. Commanders must mitigate these challenges by setting the conditions necessary for their subordinate leaders to prosper. Commanders at the tactical level earn the trust of their superiors before taking command. We should not compromise that trust by establishing rigid command and control structures that ultimately inhibit the subordinate’s ability to perform as trained. Applying the autonomous approach to C2 for distributed lethality will enable AFPs to operate in accordance with commander’s intent and is in keeping with the initiative to promote Mission Command throughout the U.S. Navy.

LT Coleman Ward is a Submarine Officer who is currently a student at the Naval War College. The preceding is his original work, and should not be construed for the opinions of views of the Department of Defense, the United States Navy, or the Naval War College.

Featured Image: The prototype of DARPA’s ACTUV, shown here on the day of its christening. Image Courtesy DARPA.

1. Timothy Walton and Bryan McGrath, “China’s Surface Fleet Trajectory: Implications for the U.S. Navy,” in China Maritime Study No. 11: China’s Near Seas Combat Capabilities, ed. Peter Dutton, Andrew Erickson, and Ryan Martinson, (U.S. Naval War College: China Maritime Studies Institute, February 2014), 119-121, accessed May 5, 2016, https://www.usnwc.edu/Research—Gaming/China-Maritime-Studies-Institute/Publications/documents/Web-CMS11-(1)-(1).aspx.; Peng Guangqian, Major General, People’s Liberation Army (Ret.), “China’s Maritime Rights and Interests,” in China Maritime Study No. 7: Military Activities in the EEZ, ed. Peter Dutton, (U.S. Naval War College: China Maritime Studies Institute, December 2010), 15-17, accessed May 12, 2106, https://www.usnwc.edu/Research—Gaming/China-Maritime-Studies-Institute/Publications/documents/China-Maritime-Study-7_Military-Activities-in-the-.pdf.

2. Walton and McGrath, “China’s Surface Fleet Trajectory: Implications for the U.S. Navy,” 119-121.

3. Thomas Rowden, Peter Gumataotao, and Peter Fanta, “Distributed Lethality,” U.S. Naval Institute, Proceedings Magazine 141, no. 1 (January 2015): 343, accessed March 11, 2016, http://www.usni.org/magazines/proceedings/2015-01/distributed-lethality.

4. Rowden et. al. “Distributed Lethality.”

5. James Bradford, America, Sea Power, and the World (West Sussex, UK: John Wiley and Sons, 2016), 339.

6. John Richardson, Admiral, Chief of Naval Operations, A Design for Maintaining Maritime Superiority (Washington, D.C.: Government Printing Office, January 2016), 6.

7. Matthew Hipple, “Distributed Lethality: Old Opportunities for New Operations,” Center for International Maritime Security, last modified February 23, 2016, accessed May 12, 2016, https://cimsec.org/distributed-lethality-old-opportunities-for-new-operations/22292.

8. Thomas Rowden et. al., “Distributed Lethality.”

9. U.S. Navy, U.S. Marine Corps, U.S. Coast Guard, A Cooperative Strategy for 21st Century Seapower (Washington, D.C.: Headquarters U.S. Navy, Marine Corps, and Coast Guard, March 2015), 9.

10. Thomas Rowden et. al, Distributed Lethality.

11. United States Navy, Naval Operations Concept 2010 (NOC): Implementing the Maritime Strategy (Washington D.C.: Government Printing Office, 2010), 54-55.

12. United States General Accounting Office, Comprehensive Strategy Needed to Improve Ship Cruise Missile Defense, GAO/NSIAD-00-149 (Washington, DC: General Accounting Office, July 2000), p. 5, accessed April 14, 2016, http://www.gao.gov/assets/230/229270.pdf.

13. Andrew Erickson and David Yang, “Using the Land to Control the Sea?,” Naval War College Review 62, no. 4, (Autumn 2009), 54.

14. United States Navy, Naval Operations Concept 2010: Implementing the Maritime Strategy, 54-56.

15. Andrew S. Erickson, Personal summary of discussion at “China’s Naval Shipbuilding: Progress and Challenges,” conference held by China Maritime Studies Institute at U.S. Naval War College, Newport, RI, 19-20 May 2015, accessed April 25, 2016, http://www.andrewerickson.com/2015/11/chinas-naval-shipbuilding-progress-and-challenges-cmsi-conference-event-write-up-summary-of-discussion/.

16. Thomas Rowden et. al., “Distributed Lethality.”

17. United States Navy. Naval Doctrine Publication (NDP) 1: Naval Warfare (Government Printing Office: Washington, D.C. March 2010), 35.

18. This is also referred to as “Mission Command” or “Command by Negation;” U.S. Office of the Chairman, Joint Chiefs of Staff, Joint Publication (JP) 3-32, Command and Control for Joint Maritime Operations (Washington D.C.: CJCS, August 7, 2013), I-2.

19. The Naval War College’s Gravely Group recently conducted a series of three DL Workshops with representation from offices across the Navy and interagency. One of the key findings was that “AFP SAG C2 architecture requires further development in view of information degraded or denied environments.” This paper proposes a notional operational level C2 structure – tactical level C2 is addressed in the recommendations section; William Bundy and Walter Bonilla. Distributed Lethality Concept Development Workshops I – III Executive Report. (U.S. Naval War College: The Gravely Group, December 29, 2015), 9.

20. This paper considers three types of maritime unmanned systems currently employed or under development: Unmanned Aerial Vehicles (UAVs), Unmanned Underwater Vehicles (UUVs), and Unmanned Surface Vessels (USVs).

21. See the below article featuring a newly developed Chinese drone similar to the U.S.’s Predator drone currently employed for operations in the Middle East; Kyle Mizokami, “For the First Time, Chinese UAVs are Flying and Fighting in the Middle East,” Popular Mechanics, last modified December 22, 2015, accessed May 10, 2016, http://www.popularmechanics.com/military/weapons/news/a18677/chinese-drones-are-flying-and-fighting-in-the-middle-east/.

22. This scenario does not represent a universal application for DL.

23. The Rowden “Distributed Lethality”article provides its own “Hunter-Killer Hypothetical” situation while supporting its main argument. However, the scenario is basic and does not afford the opportunity to explore how AFP C2 and unmanned systems would function in a complex maritime contingency.

24. Google Maps, “South Atlantic Ocean” map (and various others), Google (2016), accessed April 14, 2016, https://www.google.com/maps/@-50.3504488,-53.6341245,2775046m/data=!3m1!1e3?hl=en.

25. This is the same AFP force composition suggested in the Rowden Distributed Lethality article “Hunter-Killer Hypothetical” situation; Thomas Rowden et. al., “Distributed Lethality.”

26. For a full explanation of the CWC concept and roles and responsibilities of CWC warfare commanders, see: United States Navy, Navy Warfare Publication (NWP) 3-56: Composite Warfare Doctrine (Washington, D.C.: Government Printing Office, September 2010).

27. Larry LeGree, “Will Judgement be a Casualty of NCW?,” U.S. Naval Institute, Proceedings Magazine 130, no. 10 (October 2004): 220, accessed April 14, 2016, http://www.usni.org/magazines/proceedings/2004-10/will-judgment-be-casualty-ncw.

28. CNO’s Strategic Studies Group (XXII), Coherent Adaptive Force: Ensuring Sea Supremacy for SEA POWER 21, January 2004.

29. Michael Palmer, Command at Sea (Cambridge: Harvard University Press, 2005), 319.

30. Jimmy Drennan, “Distributed Lethality’s C2 Sea Change,” Center for International Maritime Security, last modified July 10, 2015, accessed April 14, 2016, https://cimsec.org/?s=Distributed+lethality+c2+sea+change.

31. Jeffrey Kline, “A Tactical Doctrine for Distributed Lethality,” Center for International Maritime Security, last modified February 22, 2016, accessed March 17, 2016, https://cimsec.org/tactical-doctrine-distributed-lethality/22286.

32. Palmer, Command at Sea, 322.

33. Jeffrey Kline, “A Tactical Doctrine for Distributed Lethality.”

34. Commander-in-Chief, U.S. Pacific Fleet, Current Tactical Orders and Doctrine, U.S. Pacific Fleet (PAC10), U.S. Navy, Pacific Fleet, June 1943, pg. v, section 111.

35. Paul Siegrist, “An Undersea ‘Killer App’,” U.S. Naval Institute: Proceedings Magazine 138, no. 7, (July 2012): 313, accessed April 30, 2016, http://www.usni.org/magazines/proceedings/2012-07/undersea-killer-app.

36. Thomas Rowden et. al., “Distributed Lethality.”

37. Ibid.

38. Robert Rubel, “Pigeon Holes or Paradigm Shift: How the Navy Can Get the Most of its Unmanned Vehicles,” U.S. Naval Institute News, last modified February 5, 2013, https://news.usni.org/2012/07/25/pigeon-holes-or-paradigm-shift-how-navy-can-get-most-its-unmanned-vehicles.

39. Jonathan Soloman, “Maritime Deception and Concealment: Concepts for Defeating Wide-Area Oceanic Surveillance-Reconnaissance-Strike Networks,” Naval War College Review 66, no. 4 (Autumn 2013): 89.

40. Scott Littlefield, “Anti-Submarine Warfare (ASW) Continuous Trail Unmanned Vessel (ACTUV),” Defense Advanced Research Projects Agency, accessed April 30, 2016, http://www.darpa.mil/program/anti-submarine-warfare-continuous-trail-unmanned-vessel.

41. Robert Girrier, Rear Admiral, Director, Unmanned Warfare Systems (OPNAV N99), “Unmanned Warfare Systems,” Lecture at U.S. Naval War College, May 11, 2016.

Featured Image: PHILIPPINE SEA (Oct. 4, 2016) The forward-deployed Arleigh Burke-class guided-missile destroyer USS McCampbell (DDG 85) patrols the waters while in the Philippine Sea. McCampbell is on patrol with Carrier Strike Group Five (CSG 5) in the Philippine Sea supporting security and stability in the Indo-Asia-Pacific region. (U.S. Navy photo by Petty Officer 2nd Class Christian Senyk/Released)

I Held an Amazon “Flipped” Meeting At My Squadron and Here’s What Happened

By Jared Wilhelm

The Innovation Imperative

Chief of Naval Operations Admiral John Richardson frequently talks about High Velocity Learning (HVL) and Innovation. You can tell his focus on this topic is working thanks to one clear litmus test: eye rolls and mocking from some of the Fleet’s junior officers. The CNO has spread the gospel so well on this topic that is has become a buzzword throughout wardrooms and squadrons around the world, and now “Innovation” has achieved just enough notoriety to be misunderstood.

The eye-rollers are often resistant to change, cling to the status quo, and most importantly have an ahistorical perception of innovation within the naval service. What they don’t quite comprehend is that innovation is nothing new. Commander BJ Armstrong enumerated the proof of our rich innovation history in consecutive years at the Defense Entrepreneurs Forum, first in 2013 with his lecture on Admiral William Sims that led to the book 21st Century Sims, and then followed by a look at Marine Corps’ forward-thinking embrace of the helicopter in the post-WWII era

We have innovated before, and we will innovate again. But the CNO makes the case that the quadrupling of worldwide maritime traffic in the last several decades, combined with the free and fast flow of technology and information, creates an innovation and learning imperative like we have never seen. Our maritime superiority, our relevance, and potentially even our Sailors’ survival all depend on it.

Just Do It

It can be a daunting task for an operational leader to lead innovation efforts in the context of the worldwide rise of near-peer adversaries and vague direction from the Pentagon to learn, rapidly iterate, and embrace risk.  Where can you even start?

Using the old mantra, “Think Globally but Act Locally,” I decided to tackle something that everyone in our squadron, officer and enlisted alike, always unite to grumble about: meetings. You know them–they pepper the plan of the week like the last pieces of candy in a box of chocolate that no one wants to eat; they draw scowls of dread when you see another two, three, or four in your future. They all start the same with a PowerPoint slide deck, introductions, rules of engagement for the presentation itself, proposed courses of action, “quad slides,” and graphs with labels so small you have no idea what is going on. 

tailhook-ppt
Figure 1: An actual PowerPoint slide from a Bureau of Naval Personnel briefing at Tailhook 2016 that a Captain attempted to explain to the crowd.

Several months ago I heard about a best practice from the civilian industry that caught my attention: the “flipped meeting” utilized at Amazon by billionaire innovator Jeff Bezos. Could the Amazon model work at a Naval Aviation squadron? Would the time continuum explode if officers filed in to the wardroom and didn’t see a standardized PowerPoint screen projected on the wall? I walked to OPS, asked for a meeting to be put on the schedule, and decided to find out.

I used the Navy’s HVL model based on Dr. Steve Spear’s “High Velocity Edge” framework to approach the flipped meeting:

1. Define the problem: Too many meetings in our squadron are dependent on low-learning-level presentations, and almost all exclusively use Power Point.

2. Postulate a solution – and what you think its effects will be: There are countless solutions in other organizations and the corporate world on how to increase learning and co-working levels in meetings. One specific solution is the Amazon flipped meeting, which I guessed would increase learning levels at my squadron.

3. Try out a solution: We did!

4. Do a gap analysis between what you saw happen and what you thought would happen.

5. Update your approach/solution and run it again.

One Specific Solution: The Origins and Upsides of a Bezos “Study Hall”

Fortune Magazine revealed the secrets of an Amazon executive team meeting in their 2012 profile of Jeff Bezos, the founder and CEO of the tech and retail giant.  Reporter Adam Lashinsky explains:

Before any discussion begins, members of the team—including Bezos—consume six-page printed memos in total silence for as long as 30 minutes….  They scribble notes in the margins while the authors of the memos wait for Bezos and his minions to finish reading…. Writing a memo is an even more important skill to master. “Full sentences are harder to write,” he says. “They have verbs. The paragraphs have topic sentences. There is no way to write a six-page, narratively structured memo and not have clear thinking.”

So instead of building PowerPoint slides and sweating font consistency, proper margins, bullet styles or punctuation uses, those privileged to brief Bezos focus on the ideas and content themselves. The genius of it is in the simplicity: the purpose of the meeting is to work together on the ideas or content, and the “flipped” meeting allows the ideas or content to be the focus, not the slide deck.

Blogger Walter Chen also identifies a second order effect of these type of meetings, one that Bezos surely intended: 

The real magic happens before the meeting ever starts.  It happens when the author is writing the memo. What makes this management trick work is how the medium of the written word forces the author of the memo to really think through what he or she wants to present.  In having to write it all down, authors are forced to think out tough questions and formulate clear, persuasive replies, reasoning through the structure and logic in the process.

Bezos calls the memos “narratives,” and in his opinion they have many advantages over PowerPoint, as he told Charlie Rose in 2012

The traditional kind of corporate meeting starts with a presentation. Somebody gets up in front of the room and presents with a PowerPoint presentation, some type of slide show. In our view you get very little information, you get bullet points. This is easy for the presenter, but difficult for the audience. And so instead, all of our meetings are structured around a 6 page narrative memo.

Some other advantages include:

1. Silence is golden. How many times have you presented an issue, only to see several egos in the audience try to take over or derail the brief based on their own interests? Everyone reads the narrative in silence and the discussion comes after in the Bezos “Study Hall” model. 

2. No read-ahead required. Bezos believes “the act of communal reading guarantees the group’s undivided attention.” Several times in my career, I have wondered if the person I was briefing had time to review the read-ahead, or if they were getting the message I was trying to convey during the PowerPoint. In a flipped meeting, the audience has no choice but to read the narrative (unless they want to daydream).

3. Eliminating premature questions saves everyone time. “If you have a traditional PowerPoint presentation, executives interrupt,” says Bezos.  “If you read the whole six page memo, on page two you have a question. By page four that question is answered.” 

4. Ideas and content trump presentation polish. Sometimes, the best ideas come from those who are nervous or just-plain-bad public speakers. Other times, polished presenters with million-dollar-smiles can sell bad or incomplete concepts because they can manipulate the audience into what they want to hear. With the Amazon narrative, the content speaks for itself.

5. The meeting leader is a coworker, not lecturer. The concept of a “flipped classroom” revolutionized education, and Bezos is trying to do the same for the business world. Normally a presenter lectures the audience. An Amazon lecturer is no longer verbally “pushing” communication to the audience; instead the content is “pushed” through the narrative, and then readers can “pull” knowledge from the presenter with informed questions. This creates high rates of learning compared to the traditional model.

It seems that a flipped meeting is effective based on Amazon’s stock price and global reach. But could such a meeting work outside the confines of Silicon Valley boardrooms? Would a bunch of flight-suit wearing naval aircrew be receptive to something so far from the norm?

That Awkward Silence

My unsuspecting teammates filtered in and took seats at the conference table. I hadn’t posted “Amazon-Style Flipped Meeting” on the flight schedule because I thought it might create some sort of bias or discourage full attendance. I simply listed the topic: “Squadron Innovation Culture Workshop.” This subject especially lent itself to a flipped meeting because it was difficult to summarize our squadron’s innovation culture in a deck of PowerPoint slides. 

The junior officers filled the dead space before the kick off with the usual banter and jokes. I noticed several check the clock and glance toward the powered-down and blank presentation screen as I passed out copies of the six-page narrative I’d spent the previous week perfecting. It was apparent that several were wondering why there was no laptop connected and no PowerPoint. 

The top of the hour arrived and people started leafing through the document. We were still missing two important players who I knew had planned on attending.  I decided to give them the usual five-minute grace period in a normal day filled with other tasks and meetings. One finally arrived, so I ventured out to the office of the last straggler, one of my fellow department heads. I told him we were about to start, but he was justifiably delayed in the midst of “putting out a fire” with an urgent travel issue requiring his attention. “I’ll be there in a few!”  I knew he probably thought he could catch up with the PowerPoint when he walked in. “We can wait a couple minutes more for you before we start off…” I offered.  “No, go ahead.  I’ll be down there soon.”

I returned to the assembled group and quickly explained the flipped meeting, the “study hall” reading and the 20 minutes of silence. Everyone nodded in agreement and began. The most awkward part for me was the wait. In this context, 20 minutes felt like an eternity. I already knew the narrative well as the organizer and author. I read through it again while I scanned the faces of my coworkers as they made notes or flipped pages. I found a couple of punctuation errors that I had missed. And then I waited.

The most interesting thing was the late arrival of the last participant 10 minutes into the study hall. He was a bit confused to walk into a room of us all sitting there silently with no PowerPoint in sight. He then tried to catch up on reading the narrative. In the future to help all attendees get the highest rates of learning, I think it would be best to notify everyone in advance it will be a flipped meeting and that study hall will start on time.

Next, I facilitated the discussion. At first people were hesitant to express their opinions, but after a few questions by some of the other forward-leaning members of our squadron, we were well on our way to a 40-minute co-working session. By the tail of the hour the discussion was going strong and we could have continued for another thirty minutes. We decided on a collective course of action to take on the meeting’s topic and agreed on another future meeting.

“PowerPoint Makes Us Stupid.” -Gen. James N. Mattis, USMC, 2010

The backlash against PowerPoint is well documented.  This repository of articles compiled by Small Wars Journal counts more than twenty leading media or blog examinations of the detrimental effects of its use. Many leaders like the now-retired General Mattis either loathe it or outright ban it; others see it as a necessary evil.

Reporter Elisabeth Bumiller’s piece about the U.S. military’s use of the program in the New York Times in 2010, titled “We Have Met the Enemy and He is PowerPoint,” seems to foreshadow the rise of Bezos’ corporate use of the flipped meeting: 

Commanders say that the slides impart less information than a five-page paper can hold, and that they relieve the briefer of the need to polish writing to convey an analytic, persuasive point. Imagine lawyers presenting arguments before the Supreme Court in slides instead of legal briefs.

The most compelling defenses I’ve heard for military innovation do not involve completely new ideas or inventions. Instead they focus on finding creative best practices in sometimes-unexpected places that could be applied to military problems. Maybe “flipped meetings” won’t catch on to replace old methods completely, but they could become one tool for leaders to use when an occasional respite is needed from the groundhog-day-monotony of PowerPoint briefings.

I would encourage other leaders to challenge the status quo in your unit’s meetings. These resources by Fred Zimmerman and Walter Chen can guide you to figure out how to best write your own flipped meeting narrative.

There are myriad other ways to shake up a meeting, like using the “design thinking” approach or an organizational retreat made famous in Patrick Lencioni’s The Five Dysfunctions of a Team. The solution you use will depend heavily on the topic and purpose of the meeting. For example, it is difficult and counterproductive to attempt to give chart-centric “course rules” brief using thousands of written words when visual aids are most appropriate. Even if your first instinct is to use PowerPoint because of the visual nature of the topic, there are several alternative programs like Prezi or Haiku Deck that could bring extra engagement to your audience. The most important concept to remember is that PowerPoint is just a tool, not something good or bad. We need to focus as leaders on using whatever the appropriate tool is for the specific job, not simply revert to the familiar tool just because it is habitual or easy.

Gap Analysis

So how did my flipped meeting experiment match up to what I thought would happen when I postulated the solution? I think it was worthwhile and I’m looking forward to doing it again. I wasn’t laughed out of the squadron or told by my bosses to go back to exclusively PowerPoint meetings. I saw the light in several of my coworkers’ eyes (despite some initial uncertainty) as they scribbled on parts of the narrative and debated sections they had pulled from it. We had an in-depth discussion about our innovation culture that could have been brought about with a PowerPoint brief instead of the “study hall,” but the discussion would have been less nuanced and with less time to collaborate. Usually presentations are designed for 45 minutes with 15 minutes of questions and discussion at the end. We invested 20 minutes up front during the flipped meeting to silently immerse in the topic, leaving us more than double the discussion and co-working time.

The flipped meeting can’t be considered a complete success, though, until we are achieving high learning rates from our gatherings on a consistent basis, no matter what tool is used to get there. If I started a conversation or sparked an idea in the wardroom, it was worth it. 

Every meeting I’ve gone to since, I enter the room and look at the briefer, the table and the wall. One of these days there will be no PowerPoint and a stack of six-page narratives waiting for me to pick up. Here’s to “study hall!”

Jared Wilhelm is a U.S. Navy officer and Maritime Patrol Instructor Pilot with experience in four operational theaters flying the P-3C Orion. He is a passionate writer focused on innovation and meaningful reform, all to help maintain the U.S. military’s superiority over adversaries in the short and long term. He served in Argentina as an Olmsted Scholar from 2014-2016 and won the U.S. Naval Institute’s 2015 General Prize Essay Contest. He is a Department of Defense Spanish linguist who holds masters degrees from the U.S. Naval Postgraduate School (Systems Engineering and Analysis) and the U.S. Naval War College (National Security and Strategic Studies), as well as a B.S. in Systems Engineering from the U.S. Naval Academy. The opinions expressed are his alone and do not reflect the official position of any other entity or organization.

Featured Image:  U.S. Navy photo by Mass Communication Specialist 3rd Class Jackie Hart.