Tag Archives: Innovation

Learning to Innovate

By Philip Cullom

Last month, Roger Misso published an article on this site entitled What Happens to Naval Innovation Deferred? and this post addresses a number of the points raised in that submission.

First, I would like to thank LT Misso for caring enough about our Navy to convey his thoughts and recommendations through his writing. Further, I would like to commend him for having the courage to stake an opinion and share his viewpoint.

I strongly agree with him regarding several items in his post:

-Sailors are the Navy’s asymmetric advantage.

-There is a groundswell of positive disruptive thought that exists around the Navy among Navy Sailors and civilians who all want the Navy to sustain its primacy.

-It is important for leadership to exemplify the phrase “we’ve got your back”…innovators need top-cover from the highest levels.

LT Misso is correct that:

-We are disestablishing CNO’s Rapid Innovation Cell (CRIC).

-The CNO’s Strategic Studies Group (SSG) is coming to a close.

There are reasons for each of these actions but please rest assured that it is not a rejection of the innovative efforts going on across the Navy.

Innovation has gotten a lot of press globally in the private sector as well as in military circles, and for very good reason. Technology is changing faster than ever before. Product development cycles are shortening in virtually every business. Competitiveness is often seen as being a function of capturing this innovation.

One caution is that we must be wary of “innovation” becoming a trendy buzzword or perceived panacea for the future as we ride the wave of its popularity. That could make it go the way of other transformative movements such as the Revolution in Military Affairs, Total Quality Leadership, etc.

We must remember that at the heart of the change we seek is disruptive thinking that continuously improves the naval capabilities we deliver for the joint force and nation.

This can only be achieved with a fresh approach to learning and a fundamental culture change to the cycle by which we learn.

This is why at the forefront of the lines of effort discussed in “A Design for Maintaining Maritime Superiority” is the imperative for High Velocity Learning – as this is the real engine for sustainable innovation. The intent for High Velocity Learning is to have many idea factories for a growing cadre of innovators and disruptive thinkers. If captured by all levels of our Navy, particularly the grassroots level, the engine for innovation will be enduring. To that end, we are breathing life into the idea of High Velocity Learning. 

Here are but a few of the actions, both grassroots and leadership sponsored, that are occurring across the Navy:

  • USS Benfold (DDG 65) started an innovation grassroots movement called Project ATHENA. The Commanding Officer challenged his crew to solve Navy issues on the deckplate level through the concept that often the people closest to the problem are often the people closest to the solution. That grew into a San Diego-wide effort that is catching on in other homeports too.
  • In March 2016, OPNAV hosted an Innovation Jam – part Shark Tank, part TED Talk – partnering with SPAWAR, ONR and PACFLT’s Bridge and connecting with Project ATHENA and the Hatch to collect grassroots ideas from the Fleet. This has provided funding and engineering support for three Sailor invented ideas to be prototyped for ultimate evaluation for fleetwide applicability. Other Innovation Jams in other Fleet concentration areas are planned. 
  • Admiral Swift’s adoption of a process within PACFLT to harness High Velocity Learning called “The Bridge” will ensure that your good ideas will go from being a “thought on the Mess Decks/Chiefs Mess/Wardroom” to reality…with the time measured in weeks and months, not years. The Bridge is a PACFLT initiative launched to discover, explore, and cultivate solutions to Fleet-centric challenges, needs, and priorities and connect the sources and sponsors best suited to prototype, develop, and create policy for fleetwide adoption.
  • SECNAV recently released an ALNAV standing up the Naval Innovation Advisory Council (NIAC) to consider, develop, and accelerate innovative concepts for presentation to the SECNAV and other DON senior leaders, with recommendations to synchronize senior leadership, influence the flow of resources, streamline policy, and/or remove roadblocks that hinder innovation.
  • As a correction, we are not standing back up Deep Blue, but rather reconstituting a capability on the OPNAV staff, in N50, to elevate the stature of Navy strategy and better synchronize our efforts. This will concentrate Navy strategic thought inside the life lines of the OPNAV Staff.
  • Other evolving initiatives which will be used to quickly foster and transition innovative efforts include the Rapid Prototyping, Experimentation and Demonstration (RPED) initiative and the Maritime Accelerated Capabilities Office (MACO). These address the speed with which new warfighting capabilities are delivered to the Fleet to better match the urgency of need. Those will be spelled out in greater detail as this process continues to mature.

To be clear, we need every Sailor, active and reserve, to willingly jump in to High Velocity Learning – to be bold, to proffer fearless ideas, and to be willing to dare and drive the Navy forward. As CNO says, “if you are waiting for your High Velocity Learning kit to come in the mail, you are going to be sorely disappointed…because that’s not how this is going to work.” This effort requires us all to play an active role.

160621-N-YO707-178 Washington, D.C. (June 21, 2016) U.S. Navy Vice Adm. Philip Cullom, deputy CNO for fleet readiness and logistics, speaks with Prof. Neil Gershenfeld, second from right, director of MIT's Center for Bits and Atoms during the Capitol Hill Maker Faire in Washington, D.C., June 21, 2016. The Faire showcased robotics, drones, 3D printing and printed art. (U.S. Navy photo by Mass Communication Specialist 2nd Class Cyrus Roson/ Released)
Washington, D.C. (June 21, 2016) U.S. Navy Vice Adm. Philip Cullom, deputy CNO for fleet readiness and logistics, speaks with Prof. Neil Gershenfeld, second from right, director of MIT’s Center for Bits and Atoms during the Capitol Hill Maker Faire in Washington, D.C., June 21, 2016. The Faire showcased robotics, drones, 3D printing and printed art. (U.S. Navy photo by Mass Communication Specialist 2nd Class Cyrus Roson/ Released)

Navy leadership will have your back and provide appropriate forums to bring your ideas – whether they be products, policies or a different way of thinking – forward for us to experiment with or prototype and then assess its ability to become a best practice for the whole Navy.

Our goal is to capture the innovative spirit endemic to the way the Navy works. The Navy has been on the leading edge of innovation for centuries and it is my job to keep us on that cutting edge because, as Roger stated, our people are our talent and our “asymmetric advantage today” well into the future. We have come a long way from the days of sail and steam to all electric warships with integrated power systems that will support energy weapons like LaWS and the electromagnetic railgun. More examples of innovation can be found in our history in carrier aviation to the cutting edge work we are doing now in additive manufacturing, which has been developed through a grassroots effort.

Thank you again to Roger and the many others who continue to push ideas (and when appropriate, concerns) forward. This is an effort we all must play an active role in advancing.

This article has been updated with the status of Deep Blue, and provides additional details on ongoing efforts regarding innovative thinking inside the Navy staff.

Vice Admiral Philip Cullom is a career Surface Warfare Officer with more than thirty years of naval service. He currently serves as the Deputy Chief of Naval Operations for Fleet Readiness and Logistics where he serves as the uniformed point person for naval innovation and creativity for the OPNAV and Secretariat staffs.

Featured Image: SAN DIEGO (March 16, 2016) Lt. Cmdr. Allison Terray tries a virtual reality headset at the Innovation Jam hosted aboard Wasp-class amphibious assault ship USS Essex (LHD 2). U.S. Navy Photo by Mass Communication Specialist 2nd Class Molly A. Sonnier.

What Happens to Naval Innovation Deferred?

By Roger Misso

So far this year, we have seen the effective termination of the CNO’s Rapid Innovation Cell (CRIC) and the announced ending of the Strategic Studies Group (SSG). Recently, we have also learned that Navy Warfare Development Command’s (NWDC) popular site “Navy Brightwork” on the joint website MilSuite (which has +500,000 users) will cease to be supported by an official Navy command. 

We are more than one year from Secretary of the Navy Ray Mabus’ “Task Force Innovation” announcements at the 2015 Sea-Air-Space conference. Nearly two dozen action memos have led to high-level documents on important topics such as Artificial Intelligence (AI), Robotics, and Big Data. They are an essential reading of the coverage while our service continues to pound away against ISIL at the line of scrimmage.

But sailors and civilians at the deckplate level have seen only a string of perceived losses this year. The concept of the CRIC, SSG, and Brightwork are exactly what our Navy needs. But rather than support, there seems to be a shopping-around for something newer and shinier, or an inability to stand up and fight for the things that will help us win the conflicts of tomorrow.

The end effect for sailors is an innovation and strategic communication shell game that heightens the barrier of entry into naval innovation communities. As soon as our sailors learn of such outstanding innovation communities like CRIC, Brightwork, and SECNAV’s “Hatch,” the pea has passed on, hiding elsewhere. It shouldn’t be a surprise then, when you see the same familiar faces showing up in innovation circles.

More importantly, what will happen to the dozens of junior enlisted and officers who were excited about CRIC, the 1,220 users of Navy Brightwork, and more broadly, the thousands of Navy officers, enlisted, and civilians with both the ideas and the drive to help us fight and win as a service? Are we alienating the very future innovators we seek to enable? Or are we onboarding them into successful communities of practice?

Who We Are

Sailors seem to come in three varieties when it comes to naval innovation:

  • The Uninterested
  • The Unknown
  • The Under-Utilized

Not much can be done with the folks in the first category; there will always exist a sizable population seeking to expend the minimum required effort to do their job and go home.

The highest potential for the Navy comes from Categories Two and Three. “The Unknown” sailors are those with great ideas, or a great deal of care, for the service, but who might not know where to pitch and refine their idea, or how to channel their fire.

“The Under-Utilized” sailors are those already active in the remaining innovation spaces, or those left behind by the dissolution of the CRIC and other such organizations. They are those who have pitched at ATHENA Project events, submitted white papers and project proposals, or have been members of various innovation cells and quasi-red teams.

These are sailors who have a more informed view of the lay-of-the-land when it comes to project management, requirements, Research, Development, and Acquisitions, and the like. These are sailors who work full-time day jobs, and in their spare time devote countless hours to projects they believe will make the Navy a better fighting force. These are sailors willing to go the extra mile for a good cause and committed leadership.

What We Need

In September 2001, days before the terrorist attacks of 9/11, then-Rear Admiral James Stavridis wrote that we must “[be] open to ideas and protective of those who advocate disruptive technologies.” More than platforms and payloads, our “Unknown” and “Under-Utilized” sailors are the Navy’s asymmetric advantage today.

To reach these sailors, the Navy must do two things:

  • Create innovation pathways that are simple and intuitive
  • Develop a strategic communications and outreach plan that is clear, cogent, concise, and backed by the highest level of leadership

First, pathways for innovative ideas and individuals are required today for our Navy to win tomorrow. When the enemy denies us use of multi-billion dollar platforms, systems, or satellites, the difference between victory and defeat will be those who can think, adapt, act, and inspire quickest. We cannot afford to build these pathways after the first strike; we must build this culture now.

Organizations like the CRIC leave such a gaping void because they allow sailors to practice both initiative and leadership. They are an empowering construct that clearly communicates trust between senior and junior leaders. They are a proving ground for new policies and technologies that would otherwise take us decades to bring to the Fleet. We need more outlets like this in our Navy, not less.

SAN DIEGO (Feb. 10, 2015) Master Chief Petty Officer of the Navy (MCPON) Mike Stevens visits service members with the CNO's Rapid Innovation Cell (CRIC) during the Western Conference and Exposition (WEST) 2015. U.S. Navy photo by Mass Communication Specialist 1st Class Martin L. Carey.
SAN DIEGO (Feb. 10, 2015) Master Chief Petty Officer of the Navy (MCPON) Mike Stevens visits service members with the CNO’s Rapid Innovation Cell (CRIC) during the Western Conference and Exposition (WEST) 2015. U.S. Navy photo by Mass Communication Specialist 1st Class Martin L. Carey.

Funding, however, is a constraint. Junior sailors do not have a hand in programming or budgeting decisions that will affect the forces they lead in the future. They cannot advocate before Congress the absolute necessity of robust pathways for innovation from the deckplates.

Yet, as they have been doing since before the days of the Naval Lyceum, committed sailors come together in the margins of our service to support one another and share ideas. Today, CRIC[x], the Defense Entrepreneurs Forum, and the Naval Constellation host a vibrant “shadow Navy” of officers, enlisted, and civilians of every rank, fleet area, and background.

In order to capitalize on the talent of these groups, the Navy must develop pathways for individuals to lead their own projects or actively influence policy throughout the fleet. If Congressional marks preclude us from funding organizations like CRIC, commands in DC, Millington, and every fleet concentration area should develop local innovation cells and red teams.

Precedence for these moves can be found in the first innovation cells started by Admiral Stavridis more than 20 years ago, and more recently, by Pacific Fleet’s “The Bridge” innovation group. These small pockets of dedicated sailors can be a command’s competitive advantage, helping adapt to both dynamic wartime circumstances and common-sense reform to improve quality of life for all sailors.

Second, we must define what we mean by “innovation,” communicate our intent, and back it all up.

Innovation is defined differently by different people. Sailors ask, “Do you want me to build something? Or think something?” As a service, our answer should be, “All of the above, if you can!” Whether it is a product, a policy, or inculcating a different way of thinking, we should seek to empower and connect those who boldly and constructively work to make our Navy better.

However, we need to communicate this in a way that sailors can recognize, remember, and repeat. Apple’s “Think Different” advertising campaign defined their brand in just two words; our Navy should be similarly brief. 

Despite the CNO’s call for “high velocity learning” in the force, rampant misunderstanding abounds. There are still commanding officers and staffs that snuff out or disparage innovators in their ranks.

One thing is clear: whether it comes from SECNAV or CNO, innovators need top-cover from the highest level to succeed. While many COs and mid-level staff officers are part of the solution, there are a significant number of officers, enlisted, and General Schedule workers who comprise the “frozen middle,” stultifying progress for any number of reasons. If we want to do things faster, and better, we need both leadership from the very top to “have our backs,” and the groundswell of energy from below that already exists.

Where We’re Going

These are not new ideas. In the same September 2001 Proceedings article, Admiral Stavridis advocated for the service to “[create] an idea factory on the sea service staffs,” “build a cadre of innovators,” “emphasize prototyping and leasing,” and “explore a ‘dual track’ procurement system,” among other recommendations.

Fifteen years has passed since his writing. Innovation from the deckplates is still imperative for the Navy. Yet we are stuck steaming in circles, instead of making way towards the horizon. We may be able to gap billets and programs, but we cannot gap ideas, and we cannot gap leadership.

We are a service of command by negation and, more recently, distributed lethality. Let us also innovate by negation, and distribute our ideas, trust, and ingenuity. If we fail to unfurl our sails as such and set a bold course, we may find ourselves asking:

What happens when naval innovation from the deckplates is deferred? “Does it dry up, like a raisin in the sun?”

LT Roger Misso is an E-2C Naval Flight Officer. He is currently working at the Pentagon, and in the shadows to advance naval innovation. You can find him on Twitter @rogermisso. The views express herein are solely those of the author and are presented in his personal capacity on his own initiative. They do not reflect the official positions of the Department of Defense, or any other U.S. Government agency.

Featured Image: U. S. Navy recruits study using electronic tablets (e-tablets) in the USS Hopper Recruit Barracks at Recruit Training Command (RTC).

Sea Control 115 – Blue Water Metrics and Monitoring Oceans

seacontrol2Blue Water Metrics, 2nd Place Winner of Tuft’s 100K New Ventures contest, is on a quest to crowdsource data collection on the health of our seas; in short, the use of pre-existing maritime platforms, from ferries to fishermen, as homes for an array of data collection equipment all over the world. Matthew Merighi, our director of Publications and member of Blue Water Metrics, will join us to discuss how this effort will work, from the technology to the marketplace.

1458137630150

DOWNLOAD: Blue Water Metrics

Circles in Surface Warfare Training

By Steve Wills

Surface fleet leadership engaged in a number of innovation attempts beginning in the 1970s and culminating with the commissioning of the Basic and Advanced Division Officer Courses (BDOC) program in 2012. Nevertheless, not all of these attempts were well-thought out. One of these missteps was the high profile closing of the Surface Warfare Officer School Division Officers Course (SWOSDOC) in 2003. This change appears to have come from a misguided desire to decrease personnel costs, improve the flow of officers from commissioning source to the fleet, improve retention of Surface Warfare officers, and appear to innovate within the zeitgeist of the “transformation” movement of the early and mid 2000’s. SWOSDOC was replaced by a program of computer-based training (CBT) in which prospective Surface Warfare Officers (SWOs) transited directly from disparate commissioning sources directly to their first ships. This effort proved a failure and was gradually replaced through a return to formalized schoolhouse-based training. In 2012, the CBT method was terminated and replaced by more traditional Basic and Advanced Division Officer Courses (BDOC and ADOC) held in two segments before and after the prospective SWO’s first division officer tour. An analysis of this innovation failure is a cautionary tale for those debating or implementing reform. It appears that the objectives that motivated the would-be reformers were erroneous, short-sighted, and could have been avoided by a careful understanding of the history of surface warfare training.

A Short History of Surface Warfare Training

“Plowing Ahead through Rough Seas”

Surface Warfare training has historically been a journeyman process in which a new officer reporting to his or her first ship remains in a probationary status until evaluated by his or her peers and superiors, most importantly their commanding officer (CO), for competency and professional qualification. Prior to the start of the Second World War, nearly all officers came from the United States Naval Academy (USNA). However, by the war’s end reserve officers commissioned for war service outnumbered regular officers (nearly all USNA graduates), by a factor of nearly 5.5 to 1.[i] Following[ii] the war, a need to maintain a larger peacetime force demanded a larger pool of officer accessions than the USNA could provide, and officers from Naval Reserve Officer Training Corps (NROTC) and Officer Candidate School (OCS) continued to supply the fleet with larger percentages of newly commissioned officers.

The Navy also began to embrace technological advancements at an accelerated effort in the surface fleet that required greater competency in newly commissioned officers (ensigns). The submarine and aviation communities had been confronted by advanced technologies beyond the scope of USNA training from their inception, and had instituted professional courses of instruction to train and qualify their officers for service in submarines and aircraft. By the mid-Cold War, technological advancements such as radar, sonar, and data processing networks such as the Naval Tactical Data System (NTDS) had significantly affected the surface fleet.

The training program for postwar surface officers in the late 1940’s and 1950’s had not kept pace with technological advance. Evidence from the period suggests that few professional training courses were available once an officer commissioned. Unlike USNA graduates, those coming from civilian colleges via the NROTC program did not have extensive professional training, but were expected to fulfill significant duties. Future Vice Chairman of the Joint Chiefs of Staff, Admiral David S. Jeremiah, reported to his first ship in 1956 after graduation from the University of Oregon and found himself qualified as Officer of the Deck (OOD) after standing only three under instruction watches.[iii] One Captain told an NTDS project officer aboard his ship for testing that, “No damn computer was going to tell him what to do, and for sure, no damned computer was going to fire his missiles (which it would not do in any case).”[iv] In such a climate of fear and resistance it became readily apparent that additional professional training would be required by surface officers in order to maximize the operational capabilities of the new weapons, sensors and associated data link equipment.

The Naval Destroyer Officers School, the forefather of the present Surface Warfare Officers School Command, was commissioned in July 1961 at Newport, RI with support from then-Chief of Naval Operations (CNO), and surface warfare officer, Admiral Arleigh Burke.[v] Its mission was “to improve combat readiness and tactical knowledge for junior naval officers on all ships.”[vi] The first focus was on training Heads of Department, for which no specific training program existed before the establishment of the Destroyer School despite their vast responsibilities.[vii]

The success of the Destroyer School prompted calls from the fleet for a similar course designed to provide similar training to new division officers before they reported to their first ships. A 1965 Naval Institute Proceedings article by Lieutenant (junior grade) Roy C. Smith IV highlighted the problems facing the newly commissioned officer on a contemporary warship. Smith wrote, “Being a “professional” in the Navy of the present day requires a more-than-working knowledge of advanced, ever-changing engineering, weapons, and electronic systems; complicated tactical and operational procedures; and a sound foundation in the increasingly more horrifying naval administrative structure.”[viii] He added that a formalized course would be more desirable than the present situation where officers spent, “between six and twelve months out of their first four years of service attending courses to provide some specific skill” and that “a six month school at the beginning of an officer’s career would have the benefit of both providing a better trained officer and reducing the need for the smaller skill specific schools.”[ix]

The First Surface Warfare Division Officer School class began in September 1970 as a pilot program with 24 officers.[x] Its genesis was largely due to the efforts of the revolutionary CNO Admiral Elmo Zumwalt. Zumwalt was concerned about surface officer retention and founded a number of warfare-based junior officer retention groups soon after assuming the office of CNO. These groups reported their findings to the CNO in person and those of the surface group were especially incisive. It made over 100 recommendations including “more rigorous standards, better schooling, and a surface warfare pin equivalent to the dolphins worn by submariners or the wings by the aviators.”[xi] Zumwalt acted immediately on these recommendations as surface warfare junior officer retention was a paltry 14% in 1970.[xii] The CNO had the Bureau of Naval Personnel (BUPERS) create a Surface Warfare designator in April 1970, and revised the SWO qualification process the following year to include a mandatory year of service on their ship before new officers could attain the SWO qualification.[xiii] The surface warfare breast insignia followed in November 1974.[xiv] An All Hands magazine article from March 1975 described the goal of the new Surface Warfare Officers School Command (SWOSCOLCOM) as “to train junior officers so that they can be fully productive from the moment they board their first ship… The curriculum at the school leans heavily on practical work and focuses on knowledge required by the junior surface warfare officer in fulfilling his role as junior officer of the watch, CIC watch officer and division officer.”[xv]

SWOS in Newport, RI
SWOS in Newport, RI.

The evolution of the surface warfare training program and associated designator was based on the idea that advances in technology, changes in U.S. society brought about by the war in Vietnam, and low retention of surface officers required defined, measurable professional training. Admirals Burke and Zumwalt, as well as other surface officers understood that the best way to address these problems was through a professional training program, and that the age-old, journeyman program of naval officer qualification was not the best path moving forward into the last quarter of the 20th century.

A Radical Course Change

“A hard left rudder in increasingly heavy seas”

The perception of SWOSCOLCOM as the surface warfare center of excellence began to slip somewhat in the late 1980’s following the damage incurred by the frigates USS Stark and USS Samuel B. Roberts as a result of battle damage and casualties they sustained in missile attacks and mine strikes (respectively). A December 1987 Proceedings article by CAPT John Byron, a diesel submarine officer, condemned SWOS unfairly in the eyes of many surface officers by stating that “the surface navy was not ready for combat… all of the Stark’s officers had attended the course,” and that SWOS itself was somehow guilty by association in that dereliction in training.[xvi] A number of officers responded to CAPT Byron’s complaints, notably CDR R. Robinson Harris who pointed out that only the very best officers were detailed to head SWO training and that many, if not most COs of the Surface Warfare School were selected for Flag.[xvii]

Surface warfare retention also began to slide in the wake of the end of the Cold War. A 2001 Junior Officer survey stated that only 33% of current SWO junior officers planned to remain in the community past their initial obligation.[xviii] The survey also revealed that only 43% of SWO junior officers aspired to rise to command of their own ship, which survey takers thought indicated a lack of professionalism.[xix] Some graduates of the basic SWOS course reported that the school was too long, many of the course instructors completed hour-long courses in twenty minutes and that the quality of instruction was poor.[xx] A SWOSCOLCOM study of the SWOS basic class of 1998 also revealed that it took on average 17 months from arrival on-board their first ship until an officer completed the requirements for the surface warfare designator.[xxi] Some Commanding Officers reported that this length of qualification meant that they only had qualified first tour division officers for a few months before they rotated to their second tours. This combination of weakened retention, lack of community pride, and a lengthy SWO pin training period strongly motivated surface warfare leaders of the early 2000’s to significantly re-think how surface warfare training should be conducted.

The solution to these problems, as well as the additional costs involved in moving new ensigns to Newport and from there to their new duty stations, was a radical shift to computer-based training (CBT). Instead of attending SWOS and associated billet specialty programs for upwards of 12-14 months before reporting to their first ship, new officers would now report directly to their ships with a packet of computer disks from which they would instead be trained by their own ship’s officers. CBT was designed around cutting costs, improving retention via efficiency and increasing the number of warfare-qualified officers aboard ships. It was expected that the SWOS school command could save upwards of $15 million dollars a year in training costs by moving division officer training from the classrooms in Newport to a shipboard environment.[xxii] Retention was expected to improve though this new system, although no scientific studies or predictions were given as to how this might be achieved. Instead, cost savings were projected for even miniscule retention improvements, and these alone were touted as good reason for adopting the proposed training change.[xxiii] The fact that there were always a number of officers forced to become SWOs due to attrition from other warfare training programs was not addressed in the survey effort.

800px-thumbnail (1)
NEWPORT, R.I. (May 16, 2007) – Surface Warfare Officer’s School (SWOS) students navigate their virtual vessel through a number of simulated hazards in the school’s full-mission bridge. U.S. Navy photo by Mass Communication Specialist 2nd Class Jason McCammack.

Even studies advocating this change postulated significant potential problems with a CBT approach to surface warfare division officer training such as: quality of instruction at commissioning sources would need to be improved, midshipman training cruises would need to be more formalized with specific qualification goals, and some billets supported by schools in Newport such as Damage Control Assistant (DCA) and Information Systems/Communications Officer might be lost to surface officers and transferred to limited duty officers (LDOs).[xxiv] All of these changes were brought about based on a limited number of inputs, specifically retention, training costs, and several select surveys of junior officers. The issue of professional quality in training was addressed in a manner that suggested experience at sea would always be superior to that of classroom training ashore.

The change was made in 2003 when then-Commander Naval Surface Force Pacific Fleet Vice Admiral Timothy LaFleur described the change as one that would “result in higher professional satisfaction, increase the return on investment during the first division officer tour, and free up more career time downstream.”[xxv] First tour division officers would still go to SWOS at Newport, RI, but at a point about six months into their assignment and for only four to six (later reduced to three) weeks in a kind of “finishing school” designed to test their knowledge just after their expected qualification as Officer of the Deck (OOD) underway. This change would have significant negative effects moving forward into the decade.

Problems with Computer-Based Training

“Mind Your Helm!”

The shift in initial surface warfare officer training from an ashore, classroom-based setting to an afloat, ship based environment did not go nearly as well as planned. By 2009, one Naval Postgraduate School (NPS) Study on the change frankly stated, “The new program may not be working as well as intended.”[xxvi] The NPS study interviewed 733 students from 12 different SWOS “finishing classes.” All of these students took a pretest to measure their knowledge upon reporting to Newport for the three week course.[xxvii] It identified seven significant shortfalls in the CBT program. Officers assigned to combatant warships (cruisers, destroyers and frigates, commonly referred to as CRUDES in the service) did better than those assigned to amphibious warships and other classes of ships. Those ships assigned to Atlantic Fleet units did worse than other geographic areas. Naval Academy graduates did worse than those from NROTC and Officer Candidate School (OCS). An officer’s undergraduate performance was mirrored in his or her performance on the test. Graduates with technical majors did better on the test than did non-technical undergraduate majors. Women had significantly lower grades than men. Finally, racial and ethnic and racial minorities did not do as well as their white counterparts.[xxviii] Nevertheless, crucially, the researchers who carried out the test found that nearly all of these score disparities disappeared when all students were provided face to face, traditional classroom training.

The researchers also suggested that there were a number of pre-existing studies (before 2003) suggesting that a switch to computer-based training in order to save money was fraught with negative effects, especially a drop in the quality of instruction. The survey noted that the Navy CBT program was designed to take place in an environment where the trainee had a full time job as a division officer at sea, an environment not well-studied enough for such a dramatic training change in the opinion of the researchers.[xxix] The quality and quantity of mentoring and support to the shipboard students from the other officers aboard the students’ ships varied widely. The students surveyed generally had a negative opinion of the change. They felt ill-prepared to lead their divisions and preferred face to face as opposed to computer-based training. Worst of all, many CBT students thought the change in training made them feel less valued and professional in comparison with other unrestricted line communities.[xxx]

There was an abundance of negative reaction to the CBT program from its inception to its demise. One captain bluntly stated, “No other first-rate Navy in the world pushes newly commissioned officers out the door and directly to combatants without the benefit of formal training or underway familiarization.”[xxxi] Another felt the commanding officers would need to be more involved as the principal instructor aboard their ships as opposed to the safety observer. He stated, “For complex evolutions, like mooring to a buoy, towing, division tactics, or helo operations while in formation, a Commanding Officer is no longer able to act as a removed, above-the-fray safety observer. Instead, he has to become closely and intimately involved in solving any problems. He becomes very much like the Officer of the Deck, himself.”[xxxii]

Graduates of the new program also wrote about their unfavorable experiences. One lieutenant who completed the program condemned the idea that an officer could successfully teach herself the basics of being a Surface Warfare Officer while simultaneously leading a shipboard division. She also dismissed the three-week division officer course conducted at the end of her first division officer tour. It contained information that she should have known before reporting to her ship, and its short length, crammed with too much information was a needless, “ trial by fire” when “We have the ability and the money to set up our division officers for success.”[xxxiii]

The Navy Returns to Traditional Means of Surface Warfare Division Officer Instruction

“Shift your rudder”

The steady drumbeat of criticism from the fleet made an impact with surface warfare leadership. Commander, Naval Surface Forces Atlantic Fleet, Vice Admiral Derwood Curtis restored a modicum of traditional surface warfare classroom training with the establishment of a four week course at Newport for new ensigns before reporting to their first ships entitled “SWO INTRO.”[xxxiv] The class was specifically designed to teach “3M, division officer fundamentals, basic watchstanding and leadership.” In an interview on the now defunct SWONET internet site, Curtis said, “Some ensigns were coming to our ships not ready to perform.”[xxxv] Fleet Forces Commander Admiral John Harvey, himself a surface warfare officer, condemned the CBT program as a “flat-out failure” during a 2010 House Armed Services Committee Hearing (HASC) on fleet readiness. Admiral Harvey went on to say that the Navy had erred in sending prospective SWOs to sea unprepared and placing the burden of their training on commanding officers who “have already got a few other things to worry about.”[xxxvi]

The surface navy took another step closer to returning to the pre-2003 SWOS Division Officer course by standing up the Basic Division Officer Course (BDOC) in October 2012. The written record is more scarce on the reasons for this change, but a combination of the problems identified by Admiral Harvey in his 2010 testimony, rising naval capabilities in China, and a need to restore warfare competencies that had atrophied over the period of the post-Cold War likely required a return to more formal, professional surface warfare instruction. Some independent writers have suggested that the retreat from formal classroom instruction made the surface navy appear less professional in comparison with the aviation, submarine, nuclear power, and naval special warfare communities.[xxxvii] These other warfare disciplines have training elements that deliver qualified or nearly qualified officers when they report to their first fleet assignment. Even with the return of BDOC, the surface community instead delivers an officer that is ready to train vice a trained officer “ready to drive and fight at the pointy-end from the moment they cross the brow.”[xxxviii]

Commander of the PLA Navy Admiral Wu Shengli visits the Surface Warfare Officer School in September 2014. Image: US Navy.
Commander of the PLA Navy Admiral Wu Shengli visits the Surface Warfare Officer School in September 2014. Image: US Navy.

What does the History of Surface Warfare Training Say about Innovation?

“Captain, We Steamed Over Our Own Towline!”

The commissioning of BDOC in October 2012 would seem to complete a circle of innovative effort that began over fifty years earlier with the founding of the original Destroyer School for Department Head students at Newport in 1961. Surface Forces Commander Vice Admiral Thomas Copeman’s convocation speech for the first BDOC course reflected the basic need for the school. He said, “The surface warfare business we are in is very challenging. Our ships are complicated. They are the most technologically complex machines that this country has built and it takes a lot of hard work to learn how to fight them, learn how to maintain them, and learn how to train Sailors to maintain them.”[xxxix] Vice Admiral Copeman’s remarks are very similar to those of Rear Admiral Charles Weakley, Commander Destroyer Force Atlantic Fleet, whose charge to the new Destroyer School in 1961 was “to provide the destroyer force, through a system of functional education and training, with officers professionally qualified and motivated to function as effective naval leaders on board ship.”[xl] The Navy must avoid similarly counterproductive innovative activity as it strives to create a culture of innovation in the 21st century.

It is imperative that those reviewing the proposed change know the empirical history of the subject in question. A short review of historical material readily available in 2003 might have suggested that the Navy created a classroom training program in 1961 because the traditional, journeyman practice of training surface naval officers was deemed inadequate in light of advanced technology, the faster pace of operations, and greater complexity of naval warfare in the 1960’s. Similar conditions involving new technology and complexities of modern, joint warfare existed in 2003. Instead of following past, proven practices, the navy opted for a hypothetical, untested solution in order to cut costs and appear “transformational,”the “flavor of the day” in the early 2000’s. History may not always hold an exact answer, but it sometimes provides additional insight and clarity for those engaged in the evaluation of a new concept.

Captain Dave Welch, CO of SWOS, presents a certificate to a graduate of the Advanced Division Officer's Course (ADOC). November 2015.
Captain Dave Welch, Commanding Officer of Surface Warfare Officer School Command, presents a certificate to a graduate of the Advanced Division Officer’s Course (ADOC). November 2015.

Data from surveys is an important component to any decision on innovation, but such inputs need to be broad before making significant change. Admiral Zumwalt carried out similar surveys in 1970 to those carried out in the early 2000’s regarding surface warfare training and retention of surface warfare officers. In both periods Navy leadership identified retention as a key issue, but the 1970’s era response offered a variety of measures designed to improve retention while advancing professionalism. The changes in the early 2000’s appear to have been driven by a desire to reduce expenditures on travel and assignment to Newport, with a secondary goal in improved retention and education of surface warfare officers. There was hope that professionalism could be maintained, but how this was to be achieved in a demanding operational climate aboard ship was not given adequate attention. Those authors of the 1970’s era initiatives were junior officers from Admiral Zumwalt’s survey groups. Those of the 2000’s were largely civilian analysts who had not served aboard a U.S. Navy warship and could not be wholly conversant with the shipboard culture they proposed to radically alter.[xli] While outsiders sometimes view systemtic problems with clarity, their views must be balanced by insiders who can ensure durable, effective solutions are undertaken. This was not the case in the SWO training shift of 2003.

Finally, changes undertaken with the principal goal of saving money or hurrying a process are fraught with danger. The overriding pressure to achieve financial or time savings threatens to overtake innovative ideas and turn them into quick-fix vehicles for the achievement of specific goals. The 2000’s era changes to the surface warfare training program started with cost and time reduction, not the maintenance or professionalism or retention, as their primary entering argument. Surface warfare training traditionally contained a combination of formalized classroom instruction and practical application of those skills in evolutions at sea in order to produce a qualified surface warfare officer. The move to computer-based training assumed that the practical underway training could be replaced through simulation. A 2003 RAND study cited as one in favor of CBT began as follows:

“Recently, however, a combination of economic, operational, and political changes has prompted the Navy to consider shifting the balance toward more shore-based training. The high cost of underway training, the increased operational tempo, reduced access to training ranges, and other factors have decreased the attractiveness of underway training.”[xlii] (bold added for emphasis)

If simulation could serve as an effective replacement for complicated underway training, it is not surprising that the navy determined that a shore-based program like the Basic SWOS school that was labeled “uneconomic” could also be replaced by a CBT program. It was just another example of economy being deemed more important than the maintenance of professionalism in the minds of naval training leadership.

The 2002 NPS thesis on the Sea to SWOS program initiative stated that retention was the primary goal, but all eight benefits listed from the proposed change were financial rather than professional or operational in character.[xliii] The professional goals were more of an afterthought than a guiding principle. There was also a belief in the surface navy in the late 1990’s and early 2000’s that any problem might be solved if enough computers could be mobilized in response, although this point requires more than the anecdotal evidence available.[xliv]

The case of surface warfare officer training suggests that the history file ought to be the first stop for anyone engaged in the review and approval of innovative ideas. Those engaged in the planning and approval of the new computer-based surface warfare training program should have reviewed past surface warfare training initiatives and experiences before radically returning the fleet to a journeyman culture. The history clearly suggested that a fast-paced operational environment, with complex technologies and evolutions was no place to send untrained officers.

Type 42 UK DDG HMS Edinburgh turns in a circle before making a port visit to New York.
Type 42 UK DDG HMS Edinburgh turns in a circle before making a port visit to New York in 2013. Image: Royal Navy.

Failures in innovation can also serve as harbingers of deeper problems. It is not surprising that this degradation in training occurred within the same decade labeled by the Balisle Report as one of multiple failures in a “circle of readiness” that included training, manning, and material conditions in the surface fleet. [xlv] While it took nearly a decade for the problems in material conditions within the surface fleet to manifest themselves to higher authority, shortcomings in junior officer training were readily apparent in less than five years.

History is often ignored or given little regard by the operational navy. One of the author’s mentors once told him that, “history gets a paragraph, even in a historical analysis, before facts and figures assume their usual commanding position.” It is perhaps time for the fleet to invest more in the examination of our past before embarking on what it perceives to be new and innovative concepts. The navy must endeavor to avoid future, needless circles of effort such as the surface warfare training debacle of the last decade by examining our previous failures and follies.

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.

[i] James Robinson, “Initial Training of Surface Warfare Officers. A Historical Perspective from World War 2 to 2008”, Leavenworth, KS, U.S. Army Command and Staff College (Master’s Thesis), 2008, p. 10.

[ii]

[iii] Ibid, p. 25.

[iv] David L. Bouslaugh, When Computers Went to Sea, The Digitalization of the United States Navy, Los Alamitos, CA, IEEE Computer Society press, p. 243.

[v] http://www.public.navy.mil/surfor/Pages/SurfaceWarfareOfficerSchool.aspx#.VZVhIFLuMSU, last retrived 02 July 2015.

[vi] Ibid

[vii] Robinson, p. 34.

[viii] Ibid, p. 35

[ix] Ibid, pp. 35-36.

[x] Ibid, p. 37.

[xi] Malcolm Muir, Jr. Black Shoes and Blue Water: Surface Warfare in the United States Navy, 1945-1975. Washington D.C., Naval Historical Center, 1996, p. 224.

[xii] Ibid, p. 223.

[xiii] Ibid, p. 224.

[xiv] http://www.navy.mil/ah_online/archpdf/ah197503.pdf, p. 12.

[xv] Ibid, pp. 12, 13.

[xvi] Ibid, pp. 56. 57.

  [xvii] Ibid, p. 57.

[xvii] Christopher Galvino, “Cost Effectiveness Analysis of the “Sea to SWOS” Training Initiative on the Surface

Warfare Officer Qualification Process”, Monterey, CA, The Naval Postgraduate School, December 2002, p. 2.

[xviii]Ibid, p. 2.

[xix] Ibid.

[xx] Robinson, pp. 60-61.

[xxi] Ibid, p. 3.

[xxii] Ibid, p. 49.

[xxiii] Ibid, p. 50.

[xxiv] Ibid, pp. 51-53.

[xxv] Robinson, p. 63.

[xxvi] Bowman, William R, Crawford, Alice M, and Mehay, Stephen, “An Assessment of the Effectiveness of Computer-Based Training for Newly Commissioned Surface Warfare Division Officers”, Monterey, CA, Naval Postgraduate School, 24 August, 2009, p. ix.

[xxvii] Ibid.

[xxviii] Ibid, p. xi.

[xxix] Ibid, p. x.

[xxx] Ibid, p. xi.

 [xxxi] Stephen. F Davis., Jr., “Building the Next Nelson”. United States Naval Institute.

Proceedings. Annapolis: Jan 2007. Vol. 133, Iss. 1; pg. 1.

 [xxxii]Kevin S. J. Eyer, “On the Care and Feeding of Young SWOs”. United States Naval

Institute. Proceedings. Annapolis: Jan 2009. Vol. 135, Iss. 1; pg. 51, 4 pgs.

[xxxiii] Robinson, pp. 74-75.

[xxxiv] Ibid, p. 77.

[xxxv] Ibid.

[xxxvi] Admiral John Harvey, Testimony before House Armed Services Committee, Subcommittee on Sea Power and Expeditionary Forces, One Hundred Eleventh Congress, Second Session, Washington D.C., U.S. Government Printing Office, 28 Jul 2010.

[xxxvii] Jon Paris, “The Virtue of Being a Generalist; Part 3, Viper and Pitfalls of Good Enough”, The Center for International Maritime Security (CIMSEC), NEXTWAR blog, 19 August 2014, https://cimsec.org/virtue-generalist-part-3-viper-pitfalls-good-enough/12575

[xxxviii] Jon Paris, “The Virtue of Being a Generalist; Part 2, Are all Nuggets Created Equal?” Center for International Maritime Security (CIMSEC), NEXTWAR blog, 15 August 2014, https://cimsec.org/virtue-generalist-part-2-nuggets-created-equal/12200

[xxxix] Steven Gonzales, “SWOS Launches New Basic Division Officer Course”, Washington D.C., Chief of Naval Information Press Release, 03 October, 2012, file:///I:/SWOS/SWOS%20Launches%20New%20Basic%20Division%20Officer%20Course.htm

[xl] Michele Poole, “Building Surface Warriors”, Annapolis, MD, United States Naval Institute Proceedings, May 1998, Volume 124/3/1. 143, http://www.usni.org/magazines/proceedings/1998-05/building-surface-warriors

[xli] file:///I:/SWOS/Navy%20Re-Engineers%20Surface%20Warfare%20Training.htm

[xlii] Roland J. Yardley, Harry J. Thie, John F. Schank, Jolene Galegher, and Jessie L. Riposo, “Use of Simulation for Training in the U.S. Navy Surface Force”, Washington D.C., Research and Development Corporation, 2003, p. iii.

[xliii] Galvino, pp. 47-50.

[xliv] Jack Dorsey, “Navy Equips 2000 Officers with Palm V Hand Held Computers”, Virginia Beach, VA, The Virginian-Pilot, 2000. http://www.siliconinvestor.com/readreplies.aspx?msgid=12862250

[xlv] Philip J. Balisle, “Fleet Review Panel of Surface Force Readiness,” Norfolk, VA and San Diego, CA, Commander Fleet Forces Command and Commander, Pacific Fleet, 26 February 2010, pp. 4, 5.