Why Entrepreneurs Start Companies Rather Than Join Them

If you asked me why I gravitated to startups rather than work in a large company I would have answered at various times: “I want to be my own boss.” “I love risk.” “I want flexible work hours.” “I want to work on tough problems that matter.” “I have a vision and want to see it through.” “I saw a better opportunity and grabbed it. …”

It never crossed my mind that I gravitated to startups because I thought more of my abilities than the value a large company would put on them. At least not consciously. But that’s the conclusion of a provocative research paper, Asymmetric Information and Entrepreneurship, that explains a new theory of why some people choose to be entrepreneurs. The authors’ conclusion — Entrepreneurs think they are better than their resumes show and realize they can make more money by going it alone.  And in most cases, they are right.

I’ll summarize the paper’s conclusions, then share a few thoughts about what they might mean – for companies, entrepreneurs and entrepreneurial education. (By the way, as you read the conclusions keep in mind the authors are not talking just about high-tech entrepreneurs. They are talking about everyone who chooses to be self-employed – from a corner food vendor without a high school diploma to a high-tech founder with a PhD in Computer Science from Stanford.)

The authors’ research came from following 12,686 people over 30+ years. They found:

  1. Signaling. When you look for a job you “signal” your ability to employers via a resume with a list of your educational qualifications and work history. Signaling is a fancy academic term to describe how one party (in this case someone who wants a job) credibly conveys information to another party (a potential employer).
  2. Capable. People choose to be entrepreneurs when they feel that they are more capable than what employers can tell from their resume or an interview. So, entrepreneurs start ventures because they can’t signal their worth to potential employers.
  3. Better Pay. Overall, when people choose entrepreneurship they earn 7% more than they would have in a corporate job. That’s because in companies pay is usually set by observable signals (your education and experience/work history).
  4. Less Predictable Pay. But the downside of being an entrepreneur is that as a group their pay is more variable – some make less than if they worked at a company, some much more.
  5. Smarter. Entrepreneurs score higher on cognitive ability tests than their educational credentials would predict. And their cognitive ability is higher than those with the same educational and work credentials who choose to work in a company.
  6. Immigrants and Funding. Signaling (or the lack of it) may explain why some groups such as immigrants, with less credible signals to existing companies (unknown schools, no license to practice, unverifiable job history, etc.) tend to gravitate toward entrepreneurship. And why funding from families and friends is a dominant source of financing for early-stage ventures (because friends and family know an entrepreneur’s ability better than any resume can convey).
  7. Entrepreneurs defer getting more formal education because they correctly expect their productivity will be higher than the market can infer from just their educational qualifications. (There are no signals for entrepreneurial skills.)

Lemons Versus Cherries. The most provocative conclusion in the paper is that asymmetric information about ability leads existing companies to employ only “lemons,” relatively unproductive workers. The talented and more productive choose entrepreneurship. (Asymmetric Information is when one party has more or better information than the other.) In this case the entrepreneurs know something potential employers don’t – that nowhere on their resume does it show resiliency, curiosity, agility, resourcefulness, pattern recognition, tenacity and having a passion for products.
This implication, that entrepreneurs are, in fact, “cherries” contrasts with a large body of literature in social science, which says that the entrepreneurs are the “lemons”— those who cannot find, cannot hold, or cannot stand “real jobs.”

So, what to make of all this?
If the authors are right, the way we signal ability (resumes listing education and work history) is not only a poor predictor of success, but has implications for existing companies, startups, education, and public policy that require further thought and research.

Companies: In the 20thcentury when companies competed with peers with the same business model, they wanted employees to help them execute current business models (whether it was working on an assembly line or writing code supporting or extending current products). There was little loss when they missed hiring employees who had entrepreneurial skills. However, in the 21stcentury companies face continuous disruption; now they’re looking for employees to help them act entrepreneurial.  Yet their recruiting and interviewing processes – which define signals they look for – are still focused on execution not entrepreneurial skills.

Surprisingly, the company that best epitomized this was not some old-line manufacturing company but Google. When Marissa Mayer ran products at Google the New York Times  described her hiring process, “More often than not, she relies on charts, graphs and quantitative analysis as a foundation for a decision, particularly when it comes to evaluating people…At a recent personnel meeting, she homes in on grade-point averages and SAT scores to narrow a list of candidates, many having graduated from Ivy League schools, …One candidate got a C in macroeconomics. “That’s troubling to me,” Ms. Mayer says. “Good students are good at all things.”

Really.  What a perfect example of adverse signaling. No wonder the most successful Google products, other than search, have been acquisitions of startups not internal products: YouTube, Android, DoubleClick, Keyhole (Google Maps), Waze were started and run by entrepreneurs. The type of people Google and Marissa Mayer wouldn’t and didn’t hire started the companies they bought.

Entrepreneurship. When I shared the paper withTina Seelig at Stanford she asked, “If schools provided better ways to signal someone’s potential to employers, will this lead to less entrepreneurship?”  Interesting question.

Imagine if in a perfect world corporate recruiters found a way to identify the next Steve Jobs, Elon Musks, or Larry Ellisons. Would the existing corporate processes, procedures and business models crush their innovative talents, or would they steer the large companies into a new renaissance?

The Economic Environment. So, how much of signaling (hiring only by resume qualifications) is influenced by the economic environment? One could assume that in a period of low unemployment, it will be easier to get a traditional job, which would lead to fewer startups and explain why great companies are often founded during a downturn. Those who can’t get a traditional job start their own venture. Yet other public policies come into play. Between the late 1930s and the 1970s the U.S. tax rate for individuals making over $100,000 was 70% and 90% (taxes on capital gains fluctuated between 20% and 25%.) Venture capital flourished when the tax rates plummeted in the late 1970s. Was entrepreneurship stifled by high personal income taxes? And did it flourish only when entrepreneurs saw the opportunity to make a lot more money on their own?

Leaving a Company. Some new ventures are started by people who leave big companies to strike out on their own – meaning they weren’t trying to find employment in a corporation, they were trying to get away from it.  While starting your own company may look attractive from inside a company, the stark reality of risking one’s livelihood, financial stability, family, etc., is a tough bar to cross.  What motivates these people to leave the relative comfort of a steady corporate income and strike out on their own?  Is it the same reason – their company doesn’t value their skills for innovation and is just measuring them on execution? Or something else?

Entrepreneurial Education. Is entrepreneurship for everyone? Should we expect that we can teach entrepreneurship as a mandatory class? Or is it calling? Increasing the number of new ventures will only generate aggregate wealth if those who start firms are truly more productive as entrepreneurs.

Lessons Learned

  • Entrepreneurs start their own companies because existing companies don’t value the skills that don’t fit on a resume
  • The most talented people choose entrepreneurship (Lemons versus Cherries)
  • Read the paper and let me know what you think

 

The State of Entrepreneurship

Co-founder magazine just interviewed me about the current state of entrepreneurship – in startups and large companies – and how we got here. I thought they did a good job of capturing my thoughts.

Take a read here.

click here to read the rest of the article

Innovation at Speed – when you have 2 million employees

Success no longer goes to the country that develops a new fighting technology first, but rather to the one that better integrates it and adapts its way of fighting…Our response will be to prioritize speed of delivery, continuous adaptation, and frequent modular upgrades. We must not accept cumbersome approval chains, wasteful applications of resources in uncompetitive space, or overly risk-averse thinking that impedes change.

If you read these quotes, you’d think they were from a CEO who just took over a company facing disruption from agile startups and a changing environment. And you’d be right. Although in this case the CEO is the Secretary of Defense. And his company has 2 million employees.


In January, Secretary of Defense Mattis released the 2018 National Defense Strategy. This document tells our military – the Department of Defense – what kind of adversaries they should plan to face and how they should plan to use our armed forces. The National Defense Strategy is the military’s “here’s what we’re going to do,” to implement the executive branch’s National Security Strategy. The full version of the National Defense Strategy is classified; but the 10-page unclassified summary of this strategic guidance document for the U.S. Defense Department is worth a read.

Since 9/11 the U.S. military focused on defeating non-nation states (ISIS, al-Qaeda, et al.) The new National Defense Strategy states that we need to prepare for competition between major powers, calling out China and Russia explicitly as adversaries, (with China appearing to be the first.) Secretary Mattis said, “Our competitive advantage has eroded in every domain of warfare.”

While the Defense Strategy recognizes the importance of new technologies e.g. autonomous systems and artificial intelligence – the search is no longer for the holy grail of a technology offset strategy. Instead the focus is on global and rapid maneuver capabilities of smaller, dispersed units to “increase agility, speed, and resiliency .. and deployment … in order to stand ready to fight and win the next conflict.” The goal is to make our military more “lethal, agile, and resilient.”

The man with a lot of fingerprints on this document is the Deputy Secretary of Defense Patrick Shanahan. Shanahan came from Boeing, and his views on innovation make interesting reading.

“The DoD must become less averse to risk” is something you’ve rarely heard in the government. Yet, Shanahan said, “Innovation is messy, if the (defense) department is really going to succeed at innovation, we’re going to have to get comfortable with people making mistakes.”

All of this means that significant changes will be needed in the Department of Defense’s culture and policies.  But now the change agents and innovation insurgents who have been fighting to innovate from the bottom up at Office of Naval Research, National Geospatial-Intelligence Agency, Joint Improvised-Threat Defeat Organization, Defense Intelligence Agency, National Security Agency, Defense Innovation Unit Experimental, Intelligence Advanced Research Projects Activity, etc., will have the support all the way to the Secretary of Defense.

The innovation language in this document is pretty mind blowing – particularly the summary on page 10. It’s almost as they’ve been reading the posts Pete Newell and I have written on the Red Queen Problem and the Innovation Pipeline.

This document, combined with the split of Acquisition and Logistics, (the office responsible for buying equipment for the military), from Research and Engineering will enable the DoD to better connect with private industry to get technology integrated into the defense department. The last time the country mobilized private industry at scale was the Cold War.

As you read the excerpts below from the 2018 National Defense Strategy imagine the shockwaves this would send through any large company.  This is a pretty unprecedented document for the military.

on page 3
“…Maintaining the Department’s technological advantage will require changes to industry culture, investment sources, and protection across the National Security Innovation Base. “

on page 4
“Defense objectives include: …Continuously deliver performance with affordability and speed as we change Departmental mindset, culture, and management systems;

on page 5
Foster a competitive mindset. To succeed in the emerging security environment, our Department and Joint Force will have to out-think, out-maneuver, out-partner, and out-innovate revisionist powers, rogue regimes, terrorists, and other threat actors. We will expand the competitive space while … reforming the Department’s business practices for greater performance and affordability

on page 7
Cultivate workforce talent. … Cultivating a lethal, agile force requires more than just new technologies and posture changes; …it depends on the ability of our Department to integrate new capabilities, adapt warfighting approaches, and change business practices to achieve mission success. The creativity and talent of the American warfighter is our greatest enduring strength, and one we do not take for granted.
…A modern, agile, information-advantaged Department requires a motivated, diverse, and highly skilled civilian workforce. We will emphasize new skills and complement our current workforce with information experts, data scientists, computer programmers, and basic science researchers and engineers…The Department will also continue to explore streamlined, non-traditional pathways to bring critical skills into service, expanding access to outside expertise, and devising new public-private partnerships to work with small companies, start-ups, and universities.

on page 10
The current bureaucratic approach, centered on exacting thoroughness and minimizing risk above all else, is proving to be increasingly unresponsive. We must transition to a culture of performance where results and accountability matter.

Deliver performance at the speed of relevance. Success no longer goes to the country that develops a new fighting technology first, but rather to the one that better integrates it and adapts its way of fighting…. Current processes are not responsive to need; the Department is over-optimized for exceptional performance at the expense of providing timely decisions, policies, and capabilities to the warfighter. Our response will be to prioritize speed of delivery, continuous adaptation, and frequent modular upgrades. We must not accept cumbersome approval chains, wasteful applications of resources in uncompetitive space, or overly risk-averse thinking that impedes change. Delivering performance means we will shed outdated management practices and structures while integrating insights from business innovation.

Organize for innovation. The Department’s management structure and processes are not written in stone, they are a means to an end–empowering the warfighter with the knowledge, equipment and support systems to fight and win. Department leaders will adapt their organizational structures to best support the Joint Force. If current structures hinder substantial increases in lethality or performance, it is expected that Service Secretaries and Agency heads will consolidate, eliminate, or restructure as needed.


Up to now innovation within the Department of Defense has been the province of a small group of insurgents, each doing heroic efforts. Now innovation at speed has become a nation’s priority.  Culture change is hardest in the middle of a large organization. It will be interesting to see how each agency in the Department of Defense (and its contractors) adopts the strategy or whether the bureaucratic middle kills it/waits it out. Time will tell whether it provides real change, but this is a great start.

Why GE’s Jeff Immelt Lost His Job – Disruption and Activist Investors

This article first appeared on the Harvard Business Review blog

Jeff Immelt ran GE for 16 years. He radically transformed the company from a classic conglomerate that did everything to one that focused on its core industrial businesses. He sold off slower-growth, low-tech, and nonindustrial businesses — financial services, media, entertainment, plastics, and appliances. He doubled GE’s investment in R&D.

In his Harvard Business Review article summing up his tenure, Immelt recalls that the two things that influenced him most were Marc Andreessen’s 2011 Wall Street Journal article “Why Software Is Eating the World,” and Eric Ries’s book The Lean Startup.

Andreessen’s article helped accelerate the company’s digital transformation. GE made a $4 billion bet on connecting industrial equipment via the Internet of Things (IoT) and analytical software with a suite of products called the “Predix Cloud”.

In response to reading Eric Ries’s The Lean Startup, GE adopted Lean and built their Fastworks program around it. Beth Comstock, GE vice chair responsible for creating new businesses, embraced the lean process. Over a period of years, every GE senior manager would learn the Lean Startup, and GE would be the showcase for how modern companies use entrepreneurial management to transform culture and drive long-term growth.

Innovation at GE was on a roll.

Then it wasn’t.

In June 2017, the board “retired” Jeff Immelt and promoted John Flannery to CEO. Since then Flannery has replaced Immelt’s vice chairs responsible for innovation. Beth Comstock is out. So is John Rice, the head of Global Operations along with CFO Jeffrey Bornstein.

Last week’s Wall Street Journal story on GE opened with, “John Flannery, the leader of General Electric for just 2½ months, has already begun dismantling the legacy of his predecessor…” Flannery has pledged to unload $20 billion of GE businesses in the next two years. “We need to make some major changes with urgency and a depth of purpose. Everything is on the table,” Flannery said on a conference call to discuss quarterly earnings. “Things will not stay the same at GE.”

Instead of lean innovation programs, there is a mandate to cut $2 billion in expenses by the end of next year, lift profits and raise the dividend.

So what happened? Are lean innovation and the Startup Way a failure in large companies?

In fact, what happened is activist investors.

During Jeff Immelt’s tenure GE’s stock-market value fell by about half. Its stock is trading where it was 20 years ago. So far in 2017, GE is the worst performing stock on the Dow Jones Industrial average.

In 2015 Trian Partners, an activist investor, bought $2.5 billion of GE stock – about 1.5% of the company. The firm wrote a white paper, “Transformation Underway… But Nobody Cares” which essentially said that GE stock was undervalued because investors didn’t believe that Immelt and GE management would do the things needed to deliver a higher stock price and dividends.

Trian was pretty clear about what they thought the company should do:

  • Take on $20 billion in debt (returning the cash to shareholders by buying back GE stock).
  • Increase operating margins to 18% (by cutting expenses).
  • Buy back more stock than the $50 billion stock purchase plan GE already had in place.

Immelt believed that doing these three things would optimize the stock price and increase the value of Trian’s investment, but the debt and cuts would endanger GE’s long-term investment in innovation.

And now Immelt is now the ex-CEO, and Trian Partners just a got a seat on the GE board.

Activist Investors
The “corporate raiders” of the 20th century have rebranded themselves as “activist investors” of the 21st. With refrains of “unlock hidden value” and “increase shareholder value,” and powered by over $120 billion in assets, activist investors like Trian look for companies like GE (or Procter and Gamble) that have a share price which is underperforming relative to its peers (or those with large amounts of cash on their balance sheets). They then buy stock in these public companies and attempt to convince management to increase the price of the shares.

One key difference in 21st century activists is that they don’t need to buy much of the company’s stock to gain control. (Trian only owns ~1.5% of the GE and P&G shares.) They do it by influencing the votes of the majority of the shareholders. And in the 21st century, the majority of public company shareholders are institutional investors (banks, insurance companies, pensions, hedge funds, REITs, investment advisors, endowments, and mutual funds), not individuals. (In 2015, the 10 largest shareholders in a typical S&P 500 company held almost half of the company’s stock.)  What gives institutions even more say is that while individual shareholders vote their shares 30% of the time, institutions vote their shares 90%. (In the case of P&G, 40% of its stock was owned by small investors, helping the company fight off a 2017 proxy battle with Trian.)

After the dot.com crash in 2001 and the financial crisis of 2008, traditional investors who previously held their shares for the long-term — public pension funds, institutional investors and money managers — are now more interested in short-term gains. This means that company boards who used to side with management no longer automatically protect them, and as Jeff Immelt discovered, may even side with an activist.

Activist investors have a simple goal: increase the value of their investment. But first they need to get management of a company to change their existing strategy. To do that, they start with an implicit (GE) or explicit (P&G) threat of a proxy fight for a seat on the company board.  Next, they make a public presentation to management — like Trian’s “Transformation Underway… But Nobody Cares” — explaining what actions they think the company should take to increase the price of the stock.  Next, they use the financial press and blogs to spread their message to the institutional investors. If that still doesn’t work, they can start a proxy fight and try to gain control of shareholder votes so they can replace the board — and ultimately the company management.

If their campaign is successful, like Trian’s was at GE, they’ll have a seat on the board and a new CEO and management. They’ll have GE execute a playbook to increase the value of their investment: share repurchase programs, increased dividends, and, to reduce expenses, layoffs, factory closings, spin-offs of profitable parts of the company, sell-offs of the least profitable divisions, and asset stripping. And as Trian’s presentation suggests, they’ll get GE to take on more debt to buy back stock. And often they calculate that selling the sum of parts is greater than keeping the company together as a whole. Or they may even put the entire company up for sale.

There is an upside to an activist investor taking a run at a company. It’s often a cattle prod to a stagnant company, or one ignoring disruption by new startups. GE’s gross margin was 21% last year, compared with 28% at United Technologies and 30% at Siemens. At a minimum, as is happening to GE now, it forces a company to go through a review of its strategy. (At GE the biggest problem in 2017 was major revenue misses in their Power business.) The new GE CEO is focusing on a back-to-basics approach to the business: dramatically reducing expenses, with the visible symbols of getting rid of company planes, company cars, and delaying a fancy new headquarters, etc.

The bad news is once they take control of a company, long-term investment is not the goal of an activist investor. They often kill any long-term strategic initiatives. Often the short-term cuts directly affect employee salaries, jobs, and long-term investment in R&D. The first things to go are R&D centers and innovation initiatives.

So What is a CEO to Do?
A CEO of a public company needs to know what explicit and implicit guidance they are getting from their board and institutional investors.

Large public companies like Amazon, Tesla, Netflix, etc. capture the imagination of investors and can focus on revenue and user growth instead of on the bottom line. Almost 20 years after Amazon was launched, it has massive revenue growth and barely has a meaningful profit. Investors in these companies believe that the company’s investments in user growth will result in long-term profits. (Newly public tech companies are now going public with dual-class stock, which allows the founders to have more voting rights than the general public. This protects them from activist investors and allows them to put long-term interests ahead of quarterly results.)

But GE’s core businesses don’t have the scale of those online businesses. No innovation program, lean or otherwise, would have helped the dismal performance of their Power segment.

Companies and government organizations are discovering that innovation activities without a defined innovation pipeline results in innovation theater.  And an innovation pipeline needs to be driven with speed and urgency and results measured by the impact on the top and bottom line.

In hindsight, GE Fastworks wasn’t the problem at GE, and while the Predix Cloud has had a painful birth, GE’s investment in the industrial Internet of Things (IoT) and lean will pay off in the future. But the impact of future innovations couldn’t compensate for poor execution in its traditional businesses. GE’s board was not happy with their margins, stock price, and how Wall Street viewed the future of the company. The immediate threat of a proxy fight with an activist investor forced a decision on the future direction of the company.

The Red Queen Problem – Innovation in the DoD and Intelligence Community

“…it takes all the running you can do to keep in the same place. ”
The Red Queen Alice in Wonderland

Innovation, disruption, accelerators, have all become urgent buzzwords in the Department of Defense and Intelligence community. They are a reaction to the “red queen problem” but aren’t actually solving the problem. Here’s why.


In the 20th century our nation faced a single adversary – the Soviet Union. During the Cold War the threat from the Soviets was quantifiable and often predictable. We could specify requirements, budget and acquire weapons based on a known foe. We could design warfighting tactics based on knowing the tactics of our opponent. Our defense department and intelligence community owned proprietary advanced tools and technology. We and our contractors had the best technology domain experts. We could design and manufacture the best systems. We used these tools to keep pace with the Soviet threats and eventually used silicon, semiconductors and stealth to create an offset strategy to leapfrog their military.

That approach doesn’t work anymore. In the 21st century you need a scorecard to keep track of the threats: Russia, China, North Korea, Iran, ISIS in Yemen/Libya/Philippines, Taliban, Al-Qaeda, hackers for hire, etc. Some are strategic peers, some are near peers in specific areas, some are threats as non-state disrupters operating with no rules.

In addition to the proliferation of threats, most of the tools and technologies that were uniquely held by the DoD/IC or only within the reach of large nation states are now commercially available (Cyber, GPS, semiconductors, analytics, centrifuges, drones, genetic engineering, agile and lean methodologies, ubiquitous Internet, crypto and smartphones, etc.). In most industries, manufacturing is no longer a core competence of the U.S.

U.S. agencies that historically owned technology superiority and fielded cutting-edge technologies now find that off-the-shelf solutions may be more advanced than the solutions they are working on, or that adversaries can rapidly create asymmetric responses using these readily available technologies.

The result is that our systems, organizations, headcount and budget – designed for 20th century weapons procurements and warfighting tactics on a predictable basis – can’t scale to meet all these simultaneous and unpredictable challenges. Today, our DoD and national security agencies are running as hard as they can just to stay in place, but our adversaries are continually innovating faster than our traditional systems can respond. They have gotten inside our OODA loop (Observe, Orient, Decide and Act).

We believe that continuous disruption can only be met with a commitment to continuous innovation.

Pete Newell and I have spent a lot of time bringing continuous innovation to government organizations. Newell ran the U.S. Army’s Rapid Equipping Force on the battlefields of Iraq and Afghanistan finding and deploying technology solutions against agile insurgents. He’s spent the last four years in Silicon Valley out of uniform continuing that work. I’ve spent the last six years teaching our country’s scientists how to rapidly turn scientific breakthroughs into deliverable products by creating the curriculum for the National Science Foundation Innovation Corps – now taught in 53 universities. Together Pete, Joe Felter and I created Hacking for Defense, a nationwide program to teach university students how use Lean methodologies to solve defense and national security problems.

The solution to continuous disruption requires new ways to think about, organize, and build and deploy national security people, organizations and solutions.

Here are our thoughts about how to confront the Red Queen trap and adapt a government agency to infuse continuous innovation in its culture and practices.

Problem 1: Regardless of a high-level understanding that business as usual can’t go on, all agencies are given “guidance and metrics (what they are supposed to do (their “mission”) and how they are supposed to measure success). To no one’s surprise the guidance is “business as usual but more of it.” And to fulfill that guidance agencies create structure (divisions, directorates, etc.) designed to execute repeatable processes and procedures to deliver solutions that meet the requirements of the overall guidance.

Inevitably, while all of our defense and national security agencies will tell you that innovation is one of their pillars, innovation actually is an ill-defined and amorphous aspirational goal, while the people, budget and organization continue to flow to execution of mission (as per guidance.)

There is no guidance or acknowledgement that in our national security agencies, even as we execute our current mission, our capabilities decline every year due to security breaches, technology timing out, tradecraft obsolescence, etc. And there is no explicit requirement for creation of new capabilities that give us the advantage.

Solution 1: Extend agency guidance to include the requirements to create a continuous innovation process that a) resupplies the continual attrition of capabilities and b) creates new capabilities that gives us a mission advantage. The result will be agency leadership creating new organizational structures that make innovation a continual process rather than an ad hoc series of heroic efforts.

Problem 2: The word “Innovation” actually describes three very different types of activities.

Solution 2: Use the McKinsey Three Horizons Model to differentiate among the three types. Horizon 1 ideas provide continuous innovation to a company’s existing mission model and core capabilities. Horizon 2 ideas extend a company’s existing mission model and core capabilities to new stakeholders, customers, or targets. Horizon 3 is the creation of new capabilities to take advantage of or respond to disruptive technologies/opportunities or to counter disruption.

We’d add a new category, Horizon 0, which kills ideas that are not viable or feasible (something that Silicon Valley is tremendously efficient at doing).

These Horizons also apply to government agencies and other large organizations. Agencies and commands need to support all three horizons.

Problem 3: Risk equals failure and failure is to be avoided as it indicates a lack of competence.

Solution 3: The three-horizon model allows everyone to understand that failure in a Horizon 1/existing mission activity is different than failure in a Horizon 3 “never been done before” activity. We want to take risks in Horizon 3. If we aren’t failing with some efforts, we aren’t trying hard enough. An innovation process embraces and understands the different types of failure and risk.

Problem 4: Innovators tend to create activities rather than deployable solutions that can be used on the battlefield or by the mission. Accelerators, hubs, cafes, open-sourcing, crowd-souring, maker spaces, Chief Innovation Officers, etc. are all great but they tend to create innovation theater – lots of motion but no action. Great demos are shown and there are lots of coffee cups and posters, but if you look at the deliverables for the mission over a period of years the result is disappointing. Most of the executors and operators have seen little or no value from any of these activities. While the activities individually may produce things of value, they aren’t valued within the communities they serve because they aren’t connected to a complete pipeline that harnesses that value and turns it into a deliverable on the battlefield where it matters.

Solution 4: What we have been missing is an innovation pipeline focused on deployment not demos.

The Lean Innovation process is a self-regulating, evidence-based innovation pipeline. It is a process that operates with speed and urgency, where innovators and stakeholders curate and prioritize their own problems/Challenges/ideas/technology. It is evidence based, data driven, accountable, disciplined, rapid and mission- and deployment-focused.

The process recognizes that Innovation isn’t a single activity (an incubator, a class, etc.) it is a process from start to deployment.
The canonical innovation pipeline:

As you see in the diagram, there are 6 steps to the innovation pipeline: sourcing, challenge/curation, prioritization, solution exploration and hypothesis testing, incubation and integration.

Innovation sourcing: a list of problems/challenges, ideas, and technologies that might be worth investing in. These can come from hackathons, research groups, needs from operators in the field, etc.

Challenge/Curation: innovators get out of their own offices and talk to colleagues and customers with the goal of finding other places in the DoD where a problem or challenge might exist in a slightly different form, to identify related internal projects already in existence, and to find commercially available solutions to problems. It also seeks to identify legal issues, security issues, and support issues.

This process also helps identify who the customers for possible solutions would be, who the internal stakeholders would be, and even what initial minimum viable products might look like.

This phase also includes building initial minimal viable products (MVPs.) Some ideas drop out when the team recognizes that they may be technically, financially, or legally unfeasible or they may discover that other groups have already built a similar product.

Prioritization: Once a list of innovation ideas has been refined by curation, it needs to be prioritized using the McKinsey Three Horizons Model.

Once projects have been classified, the team prioritizes them, starting by asking: is this project worth pursing for another few months full time? This prioritization is not done by a committee of executives but by the innovation teams themselves.

Solution exploration and hypotheses testing: The ideas that pass through the prioritization filter enter an incubation process like Hacking for Defense/I-Corps, the system adopted by all U.S. government federal research agencies to turn ideas into products.

This six- to ten-week process delivers evidence for defensible, data-based decisions. For each idea, the innovation team fills out a mission model canvas. Everything on that canvas is a hypothesis. This not only includes the obvious – is there solution/mission fit? — but the other “gotchas” that innovators always seem to forget. The framework has the team talking not just to potential customers but also with people responsible for legal, support, contracting, policy, and finance. It also requires that they think through compatibility, scalability and deployment long before this gets presented to engineering. There is now another major milestone for the team: to show compelling evidence that this project deserves to be a new mainstream capability. Alternatively, the team might decide that it should be spun into its own organization or that it should be killed.

Incubation: Once hypothesis testing is complete, many projects will still need a period of incubation as the teams championing the projects gather additional data about the application, further build the minimum viable product (MVP), and get used to working together. Incubation requires dedicated leadership oversight from the horizon 1 organization to insure the fledgling project does not die of malnutrition (a lack of access to resources) or become an orphan (continue to work with no parent to guide them).

Integration and refactoring: At this point, if the innovation is Horizon 1 or 2, its time to integrate it into the existing organization. (Horizon 3 innovations are more likely set up as their own entities or at least divisions.) Trying to integrate new, unbudgeted, and unscheduled innovation projects into an engineering organization that has line item budgets for people and resources results in chaos and frustration. In addition, innovation projects carry both technical and organizational debt. This creates an impedance mismatch between the organizations that can be easily be resolved with a small dedicated refactoring team. Innovation then becomes a continuous cycle rather than a bottleneck.

Problem 5: The question being asked across the Department of Defense and national security community is, “Can we innovate like startups in Silicon Valley” and insert speed, urgency and agility into our work?

Solution 5: The reality is that the DoD/IC is not Silicon Valley. In fact, it’s much more like a large company with existing customers, existing products and the organizations built to support and service them. And much like large companies they are being disrupted by forces outside their control.

But what’s unique is, that unlike a large company that doesn’t know how to move rapidly, on the battlefields of Iraq and Afghanistan our combatant commands and national security community were more agile, creative and Lean than any startup. They wrote the book on how to collaborate (read Team of Teams) or adopt new technologies (see the Rapid Equipping Force.) The problem isn’t that these agencies and commands don’t know how to be innovative. The problem is they don’t know how to be innovative in peacetime when innovation succumbs to the daily demands of execution. Part of the reason is that large agencies are run by leaders who tend to be excellent Horizon 1 managers of existing people, process and resources but have no experience in building and leading Horizon 3 organizations.

The solution is to understand that an innovation pipeline requires different people, processes, procedures, and metrics, then execution.

Problem 6: How to get started? How to get leadership behind continuous innovation?

Solution 6: To leadership, incubators, cafes, accelerators and hackathons appear to be just background noise unrelated to their guidance and mission. Part of the problem lies with the innovators themselves. Lots of innovation activities celebrate the creation of demos, funding, new makerspaces, etc. but there is little accountability for the actual rapid deployment of useful tools. Once we can convince and demonstrate to leadership that continuous innovation can solve the Red Queen problem, we’ll have their attention and support.

We know how to do this. Our country requires it.
Let’s get started.

Lessons Learned

  • Organizations must constantly adapt and evolve, to survive when pitted against ever-evolving opposition in an ever-changing environment
  • Government agencies need to both innovate and execute
  • In peacetime innovation succumbs to the demands of execution
  • We need explicit guidance for innovation to agencies and their leadership requiring an innovation organization and process, that operates in parallel with the execution of current mission
  • We need an innovation pipeline that delivers rapid results, not separate, disconnected innovation activities

Office of Naval Research (ONR) Goes Lean

The Office of Naval Research (ONR) has been one of the largest supporters of innovation in the U.S. Now they are starting to use the Lean Innovation process (see here and here) to turn ideas into solutions. The result will be defense innovation with speed and urgency.

—-

Here’s how the Office of Naval Research (ONR) was started. In World War II the U.S. set up the Office of Scientific Research and Development (OSRD) to use thousands of civilian scientists in universities to build advanced technology weapons (radar, rockets, sonar, electronic warfare, nuclear weapons.) After the war, the U.S. Navy adopted the OSRD model and set up the Office of Naval Research – ONR. Since 1946 ONR has funded basic and applied science, as well as advanced technology development, in universities across the U.S. (Stanford’s first grants for their microwave and electronic lab came from ONR in 1946.)

Rich Carlin heads up ONR’s Sea Warfare and Weapons Department. He’s responsible for science and programs for surface ships, submarines, and undersea weapons with an annual budget of over $300 million per year.

Rich realized that while the Department of Defense DoD spends a lot of money and has lots of requirements and acquisition processes, they don’t work well with a rapid innovation ecosystem. He wanted to build an innovation pipeline that would allow the Navy to:

  • Create “dual-use” products (build solutions that could be used for the military but also sold commercially, and attract venture capital investments.) “Dual-use” products reduce the cost for defense adoption of products.
  • Test if the Lean Innovation process actually accelerates technology adoption and an innovation ecosystem.
  • Use best practices in contracting that accelerate awards and provide flexibility and speed in technology maturation and adoption.

Today ONR has taken the Lean Innovation process, adapted it for their agency, and is running pilots for defense innovation teams.

Lean Innovation is a Process
The Lean Innovation process is a self-regulating, evidence-based innovation pipeline. It is a process that operates with speed and urgency. Innovators and stakeholders curate and prioritize their own problems/Challenges/ideas/technology.

The process recognizes that Innovation isn’t a single activity (an incubator, a class, etc.). It is a process from start to deployment.

The ONR pipeline has all the steps of the canonical innovation pipeline:

Innovation sourcing: a list of problems/challenges, ideas, and technologies that might be worth investing in.

Problem/Challenge Curation: innovators get out of their own offices and talk to colleagues and customers with the goal of finding other places in the DoD where a problem or challenge might exist in a slightly different form, identifying related internal projects already in existence, and finding commercially available solutions to problems. They also seek to identify legal issues, security issues, and support issues.

This process also helps identify who the customers for possible solutions would be, who the internal stakeholders would be, and even what initial minimum viable products (MVPs) might look like.

This phase also includes building initial MVPs. Some ideas drop out when the team recognizes that they may be technically, financially, or legally unfeasible or they may discover that other groups have already built a similar product.

Prioritization: Once a list of innovation ideas has been refined by curation, it needs to be prioritized using the McKinsey Three Horizons Model. Horizon 1 ideas provide continuous innovation to a company’s existing business model and core capabilities. Horizon 2 ideas extend a company’s existing business model and core capabilities to new customers, markets or targets. Horizon 3 is the creation of new capabilities to take advantage of or respond to disruptive opportunities or disruption. We added a new category, Horizon 0, which refers to graveyard ideas that are not viable or feasible.

Once projects have been classified, the team prioritizes them, starting by asking: is this project worth pursing for another few months full time? This prioritization is not done by a committee of executives but by the innovation teams themselves.

Solution exploration and hypotheses testing: The ideas that pass through the prioritization filter enter an incubation process like Hacking for Defense/I-Corps, the system adopted by all U.S. government federal research agencies to turn ideas into products.

This six- to ten-week process delivers evidence for defensible, data-based decisions. For each idea, the innovation team fills out a mission model canvas. Everything on that canvas is a hypothesis. This not only includes the obvious -is there solution/mission fit? — but the other “gotchas” that innovators always seem to forget. The framework has the team talking not just to potential customers but also with regulators, and people responsible for legal, contracting, policy, and finance support.  It also requires that they think through compatibility, scalability and deployment long before this gets presented to engineering. There is now another major milestone for the team: to show compelling evidence that this project deserves to be a new mainstream capability. Alternatively, the team might decide that it should be spun into its own organization or that it should be killed.

Incubation: Once hypothesis testing is complete, many projects will still need a period of incubation as the teams championing the projects gather additional data about the application, further build the MVP, and get used to working together. Incubation requires dedicated leadership oversight from the horizon 1 organization to insure the fledgling project does not die of malnutrition (a lack of access to resources) or become an orphan (no parent to guide them).

Lean Innovation Inside the Office of Naval Research (ONR)
To come up with their version of the innovation pipeline ONR mapped four unique elements.

First, ONR is using Hacking for Defense classes to curate “Problem Statements” (ONR calls them Challenge/Opportunity Statements) to find solution/mission fit and commercial success.

Second, they’re using existing defense funding to prove out these solutions depending on the level of technical maturity. (There are three existing sources for funding defense innovation: COTS/GOTS validation (testing whether off-the-shelf  products can be used); Concept Validation and Technology Advancement; and SBIR/STTR funds – there’s over >$1B per year in the DoD SBIR program alone.)

Third, they are going to use Pete Newell’s company, BMNT and other business accelerators to apply Lean Launchpad Methodologies to build the business case for resulting prototypes and products and to attract private investments.

Fourth, they are going to use grants, purchase orders and Other Transaction Agreements (OTAs) to attract startups and nontraditional defense contractors, speed the award process, and provide startups the flexibility to pivot their business model and prototype/product solution when necessary.

BMNT and Hacking for Defense serve as the essential crosslink for tying together the assets already available in DoD to implement the Lean Innovation process for defense innovation.

Lessons Learned

  • The Office of Naval Research has been funding innovation in universities for 70+ years
  • They are piloting the Lean Innovation Process to move defense innovation forward with speed and urgency

Removing the Roadblocks to Government/Corporate Innovation – When Theory Meets Practice

Innovation theory and innovation in practice are radically different. Here are some simple tools to get your company’s innovation pipeline through the obstacles it will encounter.

Pete Newell and I’ve been working with Karl, the Chief Innovation Officer of a large diversified multi-billion-dollar company I’ll call Spacely Industries. Over the last 15 months his staff got innovation teams operating with speed and urgency. The innovation pipeline had been rationalized. His groups whole-heartedly adopted and adapted Lean. His innovators and stakeholders curated and prioritized their problems/idea/technology before handing them off.

Karl’s innovation pipeline had hundreds of employees going through weekend hackathons. 14 different innovation teams were going through a 3-month I-Corps/Lean LaunchPad program to validate product/market fit. His organization had a corporate incubator for disruptive (horizon 3) experiments and provided innovation support for his company’s operating divisions for process and business model innovations (Horizon 1 and 2.)  Karl’s innovation process looked like this:

(Read our last post for the details.)

Given all this activity we were surprised that in our last call with Karl he started with “I think they’ve beaten me down.” He listed the internal obstacles his teams continued to face, “We’ve created innovation teams in both the business units and in corporate. Our CEO is behind the program. The division general managers have verbally given us their support. But we’re 15 months into the program and the teams still run into continual roadblocks and immovable obstacles in every part of the company. Finance, HR, Legal, Security, Policy, Branding, you name it, everyone in a division or corporate staff has an excuse for why we can’t do something, and everyone has the power to say no and no urgency to make a change.”

The reality is that Karl’s innovation pipeline looked like this:

And worse, every time Karl negotiated to remove a roadblock for one team, he was back negotiating 6 months later to remove the very same one for a different team.

Karl was frustrated, “How do we get all these organizations to help us move forward with innovation? My CEO has been reading all the Lean Innovation books and wants to fix this and is ready to bring in a big consulting firm to redo all our business processes.”

Uh oh.

Recognizing the Roadblocks
Most of the impediments the innovation teams faced were pretty tactical: for example, an HR policy that said the innovative groups could only recruit employees by seniority. Or a branding group that refused to allow any form of the Spacely name to appear on any minimal viable product or web site. Or legal, who said minimal viable products opened the company to lawsuits. Or sales, who shut out innovation groups from doing customer discovery with any existing, or even potential customer. Or finance, who insisted on measuring the success of new ventures on their first year’s revenue and gross margin. Or purchasing who insisting that the teams use their existing vendors that took weeks to deliver simple purchases that Amazon would deliver overnight.

Listening to this we realized that while the company had playbooks for execution, what was missing were specific processes for innovation. We agreed that the goal was not to change any of the existing execution processes, procedures, incentives, metrics but rather to work with all the organizations to write new ones for innovation projects.

And the specific innovation policies would grow one at a time as needed collaboratively from the bottom of the organization, not top down by some executive mandate or consulting firm.

Read this section again. The creation of the innovation policies incrementally by the innovation groups collaborating with the service organizations is a very big idea.

We pointed out to Karl, that if he was successful, innovation and execution policies, processes, procedures, incentives, metrics would then co-exist side-by-side. In their day-to-day activities, the support organizations would simply ask, “Are we supporting an execution process (hopefully 90% of the time) or are we supporting an innovation process?” and apply the appropriate policy.

We offered that a top-down revamp of every business process should be a last resort. We suggested that Karl consider trying a 6-month experimental “Get to Yes” program. (It was critical that his CEO is a supporter.)

Get to Yes
Step one was that Karl needed a single memo from his CEO to his direct reports. We suggested that Karl ask for something like this:


Step two was that Karl needed a memo that went out to all department heads. The one from Finance looked like this:

The “Get to Yes” Collaboration
Every time an innovation team needed a new policy, procedure, etc. from an existing organization (legal, finance, sales, HR, branding, etc.), they worked with their designated point of contact (Finance, HR, Legal, etc.) Working together the two groups used the single-page standard Spacely “Get to Yes” form. It asked what problem the team was trying to solve that required a policy change, how it wanted the new policy to read, the impact the new policy would have on other policies and organizations, and most importantly the risks to the core existing business.

The “Get to Yes” request form looked like this:

In practice, once the finance, legal, and other organizations had gotten top-down guidance that innovation needed solutions to move forward, in 70% of the instances the approvals could be worked out at the lowest part of both organizations.

For the times that the innovation team and point of contact couldn’t agree, the issue got escalated to the appeals board of the appropriate department (legal, hr, security, finance, etc.) They had one week to ask questions, gather information, meet with the innovation team and evaluate the costs and risks of the proposed process. They could either:

  1. approve and adopt
  2. suggest modifications that the team agreed with
  3. deny the request.

The escalation form looked like this:

Although it was just a one-page form, the entire concept was radical:

  • The innovation team would be proposing the new process, procedure, metric, etc. – not waiting for ones to be written.
  • There was a hard 1-week deadline for the execution team to respond.
  • Yes, was the default answer, a No required detailed explanation.

For the few issues that the innovation program thought needed the executive staff attention, one further appeal was possible to the Chief Innovation Officer.

The big idea is that Spacely was going to create innovation by design, not by exception, and they were going to do it by co-opting the existing execution machinery.

The key to making this work was: 1) a simple top-down request from the CEO to their direct reports and from their direct reports down their organization, 2) a collaborative solution seeking partnership between innovation and execution teams, 3) an appeals and escalation process that would be acted on within the next week. And it’s there that the execution department had to make its case of why this request should not be approved. (If there was still no agreement, it became an issue for the executive staff.)

The time for a process resolution in a billion-dollar corporation – two weeks. At Spacely innovation was starting to move at the speed of a startup.

(BTW, when we showed this process to a government agency their first response was, “Oh that will work in a company, but in a government agency we’re bound by laws and regulations that mandate specifically what we are allowed to do.”  So, we modified the Get to Yes program to ensure that a “No” had to specifically point to the law or regulation, not agency legend, then confirm there was no potential exception to the regulation or law that could be applied.)

Lessons Learned

  • Explicit top down support for innovation only takes a single-page memo
    • If you can’t get leadership support, internal innovation won’t happen
  • Innovation process and procedures developed by collaboration, not by exception
  • Execution organizations now manage both execution and innovation
  • Innovation policy, process and procedures get written as needed, one at a time
  • Over time a set of innovation processes are created from the bottom up
  • Bias for immediate action not perpetual delay
%d bloggers like this: