The defense community is recently (and not-so-recently) awash in calls for innovation to ensure that we are militarily postured to meet future challenges and possess the agility necessary to turn toward those challenges we did not anticipate.
For example, we have the Pentagon's Third Offset Strategy and Air University's call for "Airmen to offer innovative solutions to address problems facing the Air Force in a time of increasingly daunting global and fiscal challenges." We also see what B. J. Armstrong describes as a small movement
... growing across the defense community which realizes that the challenges of the new century are going to require innovative and creative solutions. Parts of this movement, inspired from the junior ranks of our services, look to embrace the ideals of innovation and entrepreneurship from the business world. These dedicated women and men recognize that the budget, manpower, and resource challenges in a post-war drawdown mean that new ways of doing things will be required.
The Red Queen and Alice |
Why should the powers-that-be support such an effort, though, especially in the face of limited resources? In times of plenty, we have the resources but lack the imperatives for innovation. In times of need, we lack the resources but the necessity is much more clear. This is the conundrum.
That innovation (or at least the ability to innovate) is necessary in the abstract seems self-evident (and if not self-evident then compelling arguments can be made for its necessity). The world changes around us. There are adversaries, potential adversaries, allies, and potential allies all about us who all seek to increase their own relative advantage, and every change they make (whether they intend it or we like it) affects the calculus of our own continuing advantage. We are all trapped in a Red Queen Race, and survival depends upon our capacity to find new solutions to new problems, more efficient solutions to old problems, and the creation of new problems for our competitors.
But innovation for the sake of innovation is a mistake. The folks at the Havok Journal make a fine argument that not all "outside the container" thinking is worthwhile. Paraphrasing egregiously, they claim that the container was built by someone for some reason, sometimes the container is just fine, and those looking to operate outside its confines often "don’t really understand the fundamentals of [their] profession and don’t want to take the time to learn." (The full article is well worth reading, and I highly recommend it. My self-serving paraphrasing does not do it justice.)
Art, Science, and Engineering |
So, why post this thought in a forum all about analysis? I thought you'd never ask.
We (analysts, mathematicians, statisticians, modelers, computer scientists, etc.) are a part of this environment, too. Our worldviews and tools must be no less adaptable than those of the doctrine writers, planners, and strategists of the world. More important (and a little frightening) is the possibility of reified and static analytic ideas becoming framing concepts for the rest of the strategic world.
Optimality is a favorite and appropriate example. For what do we optimize force structure? A world and a worldview. What is the consequence if either situation fails to meet our assumptions? Something less than optimal. How do we minimize the probability that failures of optimality (or analysis in general) are catastrophic? Welcome to the problem of framing analysis in a way that supports the decision needs of leadership in a way that meets the needs of today, tomorrow, and the future. And welcome to the need for innovation in our own community.
So, what does this all mean? How are art, science, engineering, innovation, expertise, exploration, and exploitation to be managed? Not surprisingly, I have some thoughts on the matter:
- Expertise matters. The problems we face as military analysts are trivial in neither their costs not their consequences. If military operations research is to synthesize inputs and techniques from diverse disciplines (math, statistics, economics, computer science, etc.) expertise in those disciplines is important. Destruction and creation can produce positive results by accident, but will produce innovation far more reliably if the agents involved really understand the underlying philosophical and technical principles.
- Diversity is more than important. Without diversity of experience and expertise, it is difficult to find and exploit the skis, handlebars, outboard motors, and tank treads in our experience to create effective snowmobiles. This is an interesting concept for military operations research. Ours is an academic discipline that is inherently interdisciplinary, but an interdisciplinary field will always struggle with sufficient isolated expertise to facilitate effective interdisciplinary exploration.
- Tolerance for individual failure is critical. Evolution and innovation are bottom-up processes, and there must be room for both exploration and exploitation. In an ecosystem, failure is fatal, but that is a system relying on chance to create the necessary genetic and phenotypic variations that facilitate adaptation to changing environments at a population level. The loss of individuals is not important, since the adaptation is neither social nor volitional. On the other hand, analytic innovation is a volitional act by rational social agents, and intellectual variation leading to dead ends cannot lead to deadly individual ends (unless the objective is abject conformity). This is the primary purpose of a community/institution in the context of organizational innovation. It exists to exploit the known, incentivize exploration, and protect the explorers from censure. We need to be free to disagree, argue, and explore.
For our community these observations result in some imperatives for action. Simply put, a structure that prizes expertise and diversity in that expertise (not expertise in that diversity) while facilitating exploration of new ideas and analytic approaches is what we should seek.
Commission for Military Reorganization at Konigsberg, 1807 |
No comments:
Post a Comment