Creating « Strategic Surprise »
One of the most innovative organizations on the planet is not a private enterprise, but a government agency. Surprised? Well, that’s exactly their mission: creating and preventing strategic surprise.
Founded in 1958 at the height of the Cold War, the Defense Advance Research Projects Agency (DARPA) works to enhance U.S. technological capabilities. With a relatively small staff and budget considering its mission, DARPA has produced world-changing innovations over the years. They include the Internet, integrated circuit design, artificial intelligence, GPS, aircraft stealth technology, and the field of materials science. As DARPA somewhat mutedly puts it « our impact has been outsized over many decades. » (See DARPA’s April 2013 Framework, Driving Technological Surprise: DARPA’s Mission in a Changing World).
How has DARPA racked up such outsize success for more than 50 years? And is their approach transferrable?
Breaking down the DARPA model
Explaining the nature of its work, DARPA says it « relies on diverse performers to apply multi-disciplinary approaches to both advance knowledge through basic research and create innovative technologies that address current practical problems through applied research….
As the DoD’s primary innovation engine, DARPA undertakes projects that are finite in duration but that create lasting revolutionary change. » That takes a few minutes to digest, but a few keywords form the basis of their model: diverse performers, multidisciplinary approaches, basic and applied research, finite projects, and revolutionary change.
In a recent Harvard Business Review piece « Special Forces » Innovation: How DARPA Attacks Problems Regina Dugan, DARPA’s former director and now senior vice president for Advanced Technology & Projects at Motorola Mobility, and her coauthor Kaigham Gabriel, elucidate the DARPA model. They break it down into three key elements:
- » Ambitious goals
- » Temporary project teams
- » Independence
They say DARPA’s model can work elsewhere, but most organizations that have tried have neglected to view its elements as an interdependent system. Let’s take a look at what how these three elements interrelate.
According to Dugan and Gabriel, « Most corporate research budgets are devoted to innovations critical to maintaining companies’ competitiveness in their existing industries. » Disruptive innovations can threaten those organizations.
So, when corporations relegate to business units the definition and funding of « blue sky » research initiatives, business unit leaders almost always try to mitigate potential threats to existing products and services. The resulting compromises squash any truly radical new ideas.
Big leaps in products, services, and processes require what we call « bold goals. » DARPA focuses on an area known as « Pasteur’s Quadrant, » where groundbreaking basic research meets urgent societal needs. A healthy portfolio contains a mix of projects identified from both vantage points: some are based on opportunities presented by emerging technologies, some driven by unsolved user needs that require quantum leaps.
Temporary project teams
DARPA pulls together the best and brightest from diverse backgrounds to work on challenging projects. They deliberately limit tenures as a way to attract top performers. As we know from innovation and 3P interventions in which we’ve been involved, time limits are your friends. They create excitement, unleash creativity, and generate a sense of urgency that Dugan and Gabriel say forces the team to act as a whole and to continually challenge the status quo. Moreover, innovation doesn’t happen in a static environment; rather « the problems and the novelty of the scientific advances needed to solve them are perishable. If the desired capability cannot be created within a fixed time frame, it is likely that someone else will create it or come up with another solution. » Project leaders are given free reign to be impatient. They need obstacles cleared immediately because of the short time frames.
When establishing goals and monitoring progress, DARPA uses quantitative metrics, but avoids traditional product development planning and tracking methods. Breakthrough innovations don’t run according to traditional R&D roadmaps; they get worked out in uncharted territory, by definition. Keeping teams tied to hitting a set of milestones can be counterproductive. Instead, teams focus on fast iterations with checks to see if goals are being approached, and change direction quickly as results emerge and knowledge advances.
At DARPA, decisions are not made by committee. Instead, the advanced research group is given full insight into corporate objectives, as well as the ability to influence those objectives and the autonomy to select their own projects. DARPA explains further in its
April 2013 Framework document:
- « How do we create this portfolio of programs? One major part of the answer is bottom up: DARPA program managers define and propose new programs they believe promise revolutionary change. This is important for several reasons. An effective DARPA program manager is the person closest to the critical challenges and possible technology opportunities in his or her arena, and the personal inspiration and drive behind a novel idea is the spark needed to start a big fire. More fundamentally, surprise rarely comes from groupthink. »
Dugan and Gabriel say that project leaders have a broad set of capabilities, but that rarely includes MBA credentials. « The skill set that you acquire in business school is often about defining the market opportunity, writing a plan, and then faithfully executing it. » Instead, leaders at DARPA are « focused on managing constant flux. »
A robust approach to proposals
When executing its model, DARPA has used a set of questions that provide high-level guidance on project selection.
Created by George Heilmeier, the director of DARPA’s predecessor organization (ARPA), these guiding questions have become legendary in technological circles as the “Heilmeier catechism.” They’re deceptively simple, but incredibly effective when applied rigorously.
- » What are you trying to do? Articulate your objectives using absolutely no jargon. What is the problem? Why is it hard?
- » How is it done today, and what are the limits of current practice?
- » What’s new in your approach and why do you think it will be successful?
- » Who cares? If you’re successful, what difference will it make? What impact will success have? How will it be measured?
- » What are the risks and the payoffs?
- » How much will it cost?
- » How long will it take?
- » What are the midterm and final « exams » to check for success? How will progress be measured?
Innovation takes a system that involves ambitious but focused goals, the right people, and governance policies working in tandem.
That may mean challenging normal organizational policies and procedures. The DARPA model provides some interesting insights in how they’ve designed a system that works for their particular mission.
We encourage you to read the entire HBR article and let us know what you think.