Coaching

The Three Words That Kill Innovation Before It Starts

Every organization has a vocabulary of refusal. It’s not written in any policy manual. It’s not part of the onboarding deck. But it’s spoken fluently in every conference room, every Slack channel, every quarterly review — and it kills more ideas than any competitor ever will.


Every organization has a vocabulary of refusal. It’s not written in any policy manual. It’s not part of the onboarding deck. But it’s spoken fluently in every conference room, every Slack channel, every quarterly review — and it kills more ideas than any competitor ever will.

Phil McKinney, the former CTO of HP, spent years cataloging these phrases. He calls them corporate antibodies — the linguistic immune response that attacks new ideas before they can develop. You’ve heard every one of them.

“Insufficient ROI.” This is the most sophisticated antibody because it sounds like rigor. It demands that a disruptive idea — by definition one that creates a market that doesn’t exist yet — justify itself using metrics from the market it’s about to replace. Clayton Christensen documented this exact mechanism in The Innovator’s Dilemma: rational resource-allocation processes systematically refuse disruptive technologies because the numbers always favor the existing business.

“That’s not how we do things here.” This one is pure identity protection. As Dorothy Leonard-Barton showed in her research on core capabilities, the values and routines that made an organization successful become the primary obstacle to its renewal. “That’s not how we do things” is the organizational equivalent of an immune cell flagging a beneficial foreign body as a pathogen.

“We tried that before.” Past tense as prison sentence. The fact that a similar idea failed in 2019 under different market conditions, different leadership, and different technology says almost nothing about whether it would work in 2026. But this phrase shuts down the conversation instantly because it carries the implicit authority of organizational memory.

Robert Sutton and Huggy Rao, in their Stanford research published as The Friction Project, gave a name to the broader phenomenon: jargon monoxide. It’s the organizational language that makes work harder without anyone noticing it’s doing so. Their research identified five friction troubles that function as de facto refusal: oblivious leaders who don’t see the friction they create, addition sickness that piles on processes and meetings rather than removing them, broken connections between teams, jargon that obscures rather than clarifies, and the frenzied pace that makes reflection impossible.

Edgar Schein’s foundational work on organizational culture explains why these patterns are so persistent. Culture, Schein argued, is not what’s written on the wall. It’s the shared tacit assumptions learned through problem-solving history — the unspoken rules about what can and cannot be said, who can and cannot say it, and what happens to people who violate the norms. The antibody phrases are surface artifacts of deep cultural assumptions about authority, risk, and what the organization believes it is.

Here’s what makes this actionable rather than just depressing: antibodies are countable. You can literally sit in your next leadership meeting with a notepad and tally the phrases that shut down possibility. “Show me the business case.” “Let’s table that for now.” “I don’t think leadership will go for it.” “We don’t have the bandwidth.” Every one of these is a data point. And the density of antibody phrases in your meetings is a remarkably accurate proxy for how much refusal culture you’re carrying.

Sutton and Rao’s work suggests another diagnostic: map the friction. How many approval steps stand between someone having an idea and someone testing it? How many days does an unbudgeted sign-off take? How many people need to say yes before a small experiment can run? These aren’t just process questions. They’re the structural manifestation of the antibody vocabulary — the organizational machinery that says “no” without anyone having to say the word.

The antibodies aren’t going to eliminate themselves. They exist because they served a purpose once — protecting the organization from reckless decisions, maintaining quality standards, preserving institutional knowledge. The work isn’t to kill the immune system. It’s to teach it the difference between a pathogen and a breakthrough.

 

Key Takeaways

  • Count the antibodies. In your next three meetings, keep a tally of phrases that shut down ideas — “insufficient ROI,” “we tried that,” “that’s not how we do things here,” “let’s table that.” The number is your refusal culture score.
  • Challenge “insufficient ROI” with the Christensen question: are we evaluating this idea against the market it’s trying to create, or against the market we’re trying to protect? If it’s the latter, we’ve just engineered our own disruption.
  • Subtract before you add. Sutton and Rao’s research on “addition sickness” shows that organizations reflexively pile on processes rather than removing them. Before your next initiative, ask: what approval, meeting, or review can we eliminate?
  • Name the assumptions underneath the language. “That’s not how we do things here” is a cultural artifact. The question beneath it is: what do we believe about ourselves that makes this idea threatening? That’s where the real work lives.

 

The Challenge

Run an antibody audit this week. Pick one meeting and count every phrase that shuts down a possibility. Don’t judge, don’t intervene — just count. Then share the number with your team and ask: is this what we want?

Similar posts

Get notified of new insights

Be the first to know about new insights into the world of innovation.  We send out monthly updates on what it takes to integrate innovation into your organization.