Policy and Strategy Must Determine Force Development
U.S. force development should be driven by how our forces might be employed to protect vital national interests. Prior to 9/11, “capabilities-based” defense analysis reinforced shallow thinking about war and disconnected war from policy and strategy. The belief that surveillance and information technology could lift the fog of war elevated a desired military capability to the level of strategy. After 9/11, military operations were not clearly subordinated to comprehensive plans that aimed to achieve policy goals and objectives.
I think this excerpt from BG McMaster's article captured the essence of the problem. This article combined with Robert Jone's article in SWJ, "Populace Centric Engagement" help paint a picture that points to one Sun Tzu's cautions, "tactics without strategy is the noise before defeat.

http://smallwarsjournal.com/mag/2008...engagement.php

We are not struggling in this conflict due to the technological gains resulting of RMA, but rather because we tended to perceive war in a new way, or more simply we tried to model conflict to fit our preconceived technological solutions to it. Quite simply we created a lie. The technological gains have allowed us to be wildly successful at the tactical level, but tactical successes do not always equate to strategic success. BG McMaster's assessment that the capabilities approach to RMA reinforced shallow thinking about war and disconnected it from policy is spot on. RMA methodology has reinforced myths about war, but the question remains is a capabilities approach the wrong approach to drive technological evolution of our military forces? I don't think we know what the future will look like, and developing capabilities to address a wide range of potential threats is prudent, but a capability is not a strategy, it is simply a tool in the tool box. Perhaps the only revolution we need is in our military professional develop curriculum?