The U.S. Naval Institute on Naval Innovation. John E. Jackson. Читать онлайн. Newlib. NEWLIB.NET

Автор: John E. Jackson
Издательство: Ingram
Серия:
Жанр произведения: Прочая образовательная литература
Год издания: 0
isbn: 9781612518541
Скачать книгу
essentially create a new market by changing a fundamental value equation, thus reshaping an existing marketplace, usually rapidly and somewhat unexpectedly. Clay Christenson, a noted thinker and writer about innovation, has repeatedly pointed out the need to find, evaluate, and embrace disruptive innovations and technologies—even when it is not obvious that their time has come.

      An example of disruption would be the arrival of the telephone during the era of the telegraph. Telegraph lines already crisscrossed the country, and there were trained operators, delivery boys to run the messages, huge investments, and lots of profit in all that. Why would anyone want to have a telephone? But the technology enabled the innovation of real-time conversation, thus reshaping the marketplace for communication. Such marketplace innovation has occurred often through history and seems to be accelerating in the twenty-first century.

      I began reading and learning about innovation seriously about twenty years ago, and the more I look at big organizations and how leaders manage them, the more I believe in the need for it. The most important approach to innovation I’ve employed over the years is the use of “innovation cells.” This means simply carving out a few very bright and mildly untethered people from the organization and giving them the authority, resources, and above all the charter to find and try new ideas. I tried this first about fifteen years ago when I was a young captain at sea in command of a group of about a dozen destroyers. I had a good group of ship captains in command of the individual ships, but I saw no real innovators among them, so I asked each of the ship captains to propose a junior officer for my innovation cell. I did the same with the various aircraft squadrons that were part of my command. After interviewing all of the candidates, I chose five of them, attached them temporary duty to my staff, and told them to think about antisubmarine warfare and strikes at sea on enemy combatant ships.

      “Your job is to make everyone upset with your crazy ideas,” I told them. “And don’t worry if most of your schemes fail. In fact, I expect most of them to fail. This is like baseball—if you’re hitting .250, and one in four of your ideas bears some fruit, you’re having a solid season. You hit on one in three and it’s .333—a career year for almost any ballplayer. Anything better than that is a Hall of Fame year, which I’m not expecting (but it would be nice).” I gave them a small budget, the luxury of time to work on their ideas, and turned them loose.

      Many of their ideas were goofy and unmanageable. I remember one proposal to use old fifty-gallon oil drums tied together to simulate submarines for target practice. They tried to attach unclassified communication devices to our military systems in ways that would have violated every element of policy and regulation on the books. And they had lots of other unworkable ideas.

      But they also came up with several new ways to employ our detection systems in synergistic ways, fusing the data. This means taking input from various sensors—such as a radar, which uses electromagnetic radio waves to measure a physical object; a sonar, which uses sound waves to do the same; and infrared detectors, which measure heat—and merging them together to create a coherent location and picture of a target. We did this both at sea and on the ground in Andean and Central American jungles.

      The team did some superb work using emerging technologies, including tiny unmanned air vehicles dubbed “wasps” and real-time translation devices that we called “phraselators.” They also explored ways to attack very low radar cross-section high-speed patrol craft, an increasing threat in coastal warfare.

      Above all, the innovation cell had a synergistic effect as people throughout my command—about three thousand folks in all—saw that the leadership valued (indeed demanded) innovation. People who were not part of the innovation cell started to talk about new ways of doing business as a matter of routine. Ideas were batted back and forth across the wardroom table and in the squadron ready rooms. It was an awakening of sorts. And of course we continued to do the basic blocking and tackling that comes with the job of military preparation. But by adding to our effort through innovation, we were able to bring our game up to a new level.

      That experience made me a believer. In each of my subsequent jobs I set up an innovation cell of some sort and tried to encourage new ways of thinking, reading, writing, and sharing ideas on innovation.

      For the military broadly, of course, all this came into sharp focus after 9/11 when we were suddenly confronted with a very new sort of opponent—essentially a network of opponents who were superb innovators. Gradually over the post-9/11 decade our own innovations began to kick in, and we were able to create new ways of thinking about conflict and the tools, techniques, and procedures necessary to construct our own networks (leveraging special operations forces); deploying new types of sensors (unmanned vehicles, especially armed drones); collecting intelligence through big data (the cyberworld); using existing platforms in new ways (intercontinental ballistic missile–launching submarines converted to Tomahawk cruise missile shooting platforms, large deck amphibious ships providing “lily pad” bases for special forces); describing and implementing new ways of looking at conflict through international law; and other innovations.

      Indeed, after the 9/11 strikes on New York and Washington, it was clear that we—the military—needed to develop very new ways of thinking about conflict. I was asked by Adm. Vern Clark, the chief of naval operations, to stand up an innovation cell. We built Deep Blue (after the IBM chess-playing machine and also a play on words connoting the deep ocean) on the backbone of the Navy Operations Group, the small think tank that Rear Adm. Joe Sestak had created immediately after 9/11. Our job at Deep Blue was to come up with new ideas, forging them in the intensity of what we felt at the time was a new era of warfare.

      Some of our ideas failed; for example, a “sea swap” to keep ships forward deployed and fly their crews back and forth—although the concept is getting a new look in view of today’s more resource-constrained environment. We designed new types of combat groups (expeditionary strike groups) centered on large amphibious ships combined with destroyers and submarines, carrying drones and special operations forces. Another idea was to repackage communications using chat rooms, e-mail, and primitive versions of social networks to leverage lessons learned operationally. We looked at unmanned vehicles on the surface of the sea, below the ocean, and in the air. We created training simulators using off-the-shelf video games as bases. And Deep Blue also looked at the idea of the “expeditionary sailor,” reflecting the fact that tens of thousands of sailors would soon be serving far from the sea in the deserts of Iraq and the mountains of Afghanistan. How to train, equip, and prepare them for duty like that? Innovation!

      Around this time I attended a conference at which all the Navy flag officers were present. I was a newly minted one-star admiral heading up Deep Blue. It was a memorable meeting for a couple of reasons. At one point a vastly senior four-star admiral approached me during a coffee break. He was a naval aviator, and he was very displeased with the emphasis we were placing on drones and other unmanned air vehicles. His comments, in a nutshell, were that I was “standing into danger,” as we say in the Navy, in a career sense. And being a typical aviator, he was not subtle. “Stavridis,” he said, “your career is over unless you learn how to stay in your lane.” That was fairly unsettling but not entirely unexpected. When I mentioned this to a senior surface officer, a three-star who was a mentor and leader in the community, his comment was, “You better trim your sails, Jim.” Hardly reassuring.

      The other memorable revelation at the all–flag officer conference was delivered by the CNO. He talked at length about a study of flag officer traits that he had commissioned by a well-regarded consulting firm specializing in leadership training. The results of that study were compared with those of similar studies of very senior executives in private industry. The Navy admirals scored very high in almost every desirable trait: leadership, organization, dedication, energy, alignment, and peer review. But there was an exception to this parade of good news: Navy admirals scored the lowest in . . . willingness to take career risk—essentially the willingness to try new things, to champion innovation and change. I found it extremely ironic that this group of admirals—all of whom had demonstrated extreme reserves of physical courage in flying high-performance aircraft, spending months at sea, and conducting dangerous special operations—were simply afraid to take the bureaucratic risks that come with innovation.

      Despite these obvious indications that