In 1985, Intel was in trouble. Japanese competitors were dominating the memory chip market that Intel had helped invent. Inside the company, leadership debated what to do. During one conversation, Andy Grove, then Intel’s president and COO, asked CEO Gordon Moore a deceptively simple question: “If we were replaced tomorrow, what would a new CEO do?” Moore didn’t hesitate. “He would get us out of the memory business.”
The two men looked at each other and realized something uncomfortable. They already knew the answer; they just hadn’t acted on it. Intel exited the market that had defined its identity and doubled down on microprocessors, a decision that reshaped the company and ultimately the technology industry.
The lesson wasn’t just about strategy. It was also about the strategic courage to say no. But that only matters if it creates room for something better.
Innovation needs judgment
Most organizations celebrate experimentation. But after years working with large innovation portfolios, one pattern has become clear to me. The limiting factor isn’t the supply of ideas: it’s the ability to choose between them and identify the right process to take the winning one forward.
Every organization accumulates projects that once looked promising but never quite gain momentum. The technology works, but the market is uncertain; or the prototype impresses internally, but scaling would take years.
These projects rarely fail outright. Instead, they linger as “zombie projects,” shuffling along year after year, absorbing talent, leadership attention, and budget without ever becoming a real business.
Over time, they quietly drain the most valuable resources innovation needs, starting with leadership attention. And because every dollar and person-hour you commit to these ideas is unavailable elsewhere, you must prove that the idea is worth it.
The hidden cost of not deciding
Large organizations are especially vulnerable to this dynamic. Not because they lack capability, but because scale changes incentives. Ending a project can feel like admitting a mistake.
Multiply that behavior across dozens of teams and the result is predictable. Innovation portfolios become crowded. Decision cycles slow down. Resources are spread across too many bets.
Unsurprisingly, only a small fraction of corporate innovation pilots ever reach scale, with roughly 95% of new product launches ultimately falling short.
The problem is not statistical. It has more to do with not having the structure in place that allows you to filter ideas properly.
Why resource allocation matters more than you think in innovation
Let me be clear. It’s better to spend thousands evaluating an idea than millions fixing or unwinding it later, so you have to be ruthless about what passes through your filter. Research shows that dedicated transition teams can cut demonstration failure rates by around 50%.
We have some well-known corporate examples of resource reallocation. Consider Apple’s turnaround in the late 1990s. When Steve Jobs came back, the company had dozens of overlapping products and a confusing strategy. One of his first moves was to cut the product line down to just a handful of core offerings. That brought focus back, and within a year, the company was profitable again.
Stories like this can make failure seem like just part of the process. But the downside is that time and resources go into ideas that probably should’ve been filtered out much earlier.
Ultimately, the innovation funnel matters more than the idea pipeline. In strong innovation systems, early-stage ideas face rigorous scrutiny. If the signals aren’t there, the project stops: not because it failed, but because resources are needed elsewhere.
As a result, the surviving projects move faster because they aren’t competing with dozens of parallel experiments. Not only that, but leadership attention sharpens and investment becomes more decisive.
Disciplined rejection in practice
In practice, saying no is less about dramatic leadership moments and more about building the right systems, including defining clear continuation criteria before projects even begin. Teams know what commercial indicators must appear for a project to move forward.
Portfolio reviews play a critical role in this. Leaders need to ask, if we were starting today, would we still invest in this?
Culturally, organizations must also normalize stopping work. Teams need to understand that ending a project is not career damage. Leaders should actually reward those who identify when an initiative should be shelved, and openly acknowledge shutting down their own initiatives to help create that environment.
Finally, companies need to broaden their thinking about pathways to market, especially when the capabilities needed to scale them don’t exist internally. An external partner might be able to move with greater speed and operational clarity, unbound by organizational limitations.
The courage to cut
Many describe innovation as a creative act. In large organizations, though, it looks much closer to capital allocation. Leaders are constantly deciding where time, money and attention should go. That’s why the ability to say no matters so much.
Zombie projects can quietly drain time, talent, and money for years, simply because no one has the courage to kill them. Disciplined rejection is what creates the space real breakthroughs need to cut through the noise.
But that can only get you so far. What happens next defines the success of the technology.
The strongest organizations make deliberate choices about the future of the ideas that survive, with an honest evaluation of what it takes to see them through commercialization—whether that’s developing them internally or placing them with partners that have the skill and resources needed to scale them.
Saying no is the first step. True advantage comes from making sure the right ideas actually go somewhere.