These Five Principles Will Accelerate Innovation

As Director of the U.S. Army’s Rapid Equipping Force Pete Newell delivered innovation at speed and scale in the Department of Defense. Pete is now CEO of BMNT, a company that delivers innovation solutions and processes for governments.

Here are Pete’s 5 principles that will accelerate innovation.


To help a large Defense organization wrestle with how to increase the velocity of innovation in their ranks Steve Blank and I spent the better part of last week with our heads together reviewing everything we learned in the five years since we merged the concepts of problem curation and Lean while launching the innovation pipeline.

The original Innovation Pipeline sketch – 2016

I spent yesterday sifting through the most recent lessons learned and results from a series of accelerators BMNT is running for the intelligence community. Then last night I watched the final presentations from the inaugural Hacking for National Security course in Australia before jumping over to teach Stanford’s Hacking for Defense® (H4D) class.

Looking back on the week I’m blown away by how far we’ve come since we merged the two methodologies five years ago and by how fast we are discovering the pathways toward solving incredibly hard problems. Some examples:

  • In less than six weeks a Stanford H4D team has redefined a problem related to security vetting and radicalization while also describing the pathway a solution could follow to deployment within the Department of Defense and the Intelligence Community.
  • A Navy team recently sourced 80 problems, then curated down to one priority problem to solve. In less than 60 days they created 26 MVPs while interviewing over two dozen companies. They then incubated and delivered a solution that will help get large vessels back to sea faster, potentially saving the Navy $20M-$30M a year.
  • In just three weeks, the DIA MARS team sourced 100 problems from nearly 400 people, then curated and selected five priority problems to focus on. In eight weeks, five teams conducted more than 125 interviews (across 53 stakeholder organizations) and 12 experiments to deliver five validated proofs-of-concept and the evidence needed to confidently invest resources to prototype three of the five based on their user desirability, technical feasibility and organizational viability.

What I observed from the week’s deep dive: Whether it is an agency cross-functional team or a university-based “Hacking for” team we are accelerating, five key concepts drive the foundation for this increasing pace of learning and solution delivery. They are

  1. The power of Lean Methodology is supercharged when discovery begins with a well-curated and prioritized problem. Getting to one well-curated problem requires access to a source of hundreds of them.   
  2. Problem curation doesn’t stop until discovery is complete — the process of trying to discover the solution to a problem helps define the actual problem (and for .gov folks the actual requirement for the future solution).
  3. Stakeholder mapping and nailing the value propositions for beneficiaries, buyers, supporters, advocates and potential saboteurs are critical to building a pathway through the phases of the innovation pipeline and transitioning a solution to deployment. 
  4. The key to understanding value propositions is in building interviews that are based on a set of hypotheses (about the problem, the stakeholder and potential solutions to be explored) and data to be captured while using minimum viable products (just enough “product” to increase the efficacy of a conversation and increase the speed of learning).
  5. Innovation happens because of people and it takes a village. Whether academic-based like our Hacking for Defense teams or internal organizational Integrated Product or Cross-Functional Teams (IPTs/CFTs), accelerator teams perform best when supported by:
    1. Teachers – who can ground teams in a common framework and language for the discipline of innovation and entrepreneurship.
    2. Coaches – who can walk teams through the practical application of innovation tools in context with the problem they are trying to solve.
    3. Mentors – who will provide relentlessly direct feedback to teams and challenge them on the quality of the hypotheses, MVPs and the analysis of what they’ve learned, while driving them through each pivot rather than letting them get bogged down in “analysis paralysis.”
    4. Advisors – who will provide alternative viewpoints that will enable teams to see clearer pathways through bureaucracies.
    5. Connectors – who will help teams rapidly grow their networks to gain new insights from unique partners not yet discovered.

If your organization is running innovation activities or an accelerator and these five principles aren’t part of their program they are likely wasting your organization’s time and resources, and contributing to Innovation Theater instead of deploying solutions to real problems.

—–

Next up we’ll dig into how the innovation pipeline serves a parallel process for managing innovation

Enterprise Innovation for the 21st Century

Today’s environment requires separate systems for innovation and execution that operate with parallel and sometimes overlapping processes


3 Responses

  1. Fascinating stuff that you’re doing there, Steve!

  2. interesting stuff
    Merrill

  3. Hi, from the Phils. here, I am new to this community. Thank you, Steve, for unselfishly sharing your wisdom with us. H4D is new to me, and it is already a required course in the UK! wow!

Leave a Reply

%d bloggers like this: