The Organisational Immune Response or …

Corporate InnovationLayer 4Operations & ProcessesGovernance & Continuity

3 Mar

"Why Your Company Is Designed to Kill Its Own Innovation"

TLDR;-) Large organisations don't resist innovation because they're broken. They resist it because they're working. Four mechanisms do the killing: procedural resistance, resource competing, standard dilution, passive waiting. Each is a legitimate organisational function operating in the wrong context. If the immune response is firing, you're probably working on the wrong layer.

Eighty-three per cent of companies rank innovation as a top-three priority. Three per cent are ready to act on it. That is not a typo. BCG's 2024 Most Innovative Companies report calls what remains "zombie innovation systems": organisations going through the motions of innovation without strategic commitment, waiting for certainty that will never arrive.

The standard explanation is that organisations resist change. Entrenched managers. Risk-averse cultures. Bureaucratic inertia. Comfortable framing. Identifies villains. Also wrong.

Vijay Govindarajan, in The Other Side of Innovation (2010), states it precisely: people inside large organisations are not doing the wrong things and killing innovation. They are doing exactly what they should be doing to keep the performance engine running. And that is what kills innovation.

The resistance is the organisation functioning. The same mechanisms that protect operational quality, govern resources, maintain brand consistency, and manage risk also identify and neutralise anything genuinely new. I call this the organisational immune response. It operates through four distinct mechanisms. Each one is a legitimate organisational function that becomes pathological when applied to innovation requiring different operating conditions.

The four mechanisms

The metaphor of "corporate antibodies" has been around for years. Mitra Best (then PwC's U.S. Innovation Leader) wrote in HBR in 2012 that people and processes extinguish new ideas as soon as they begin coursing through the organisation. The metaphor is vivid. It is also imprecise. Saying "the organisation resists" is like a doctor saying "you're unwell." The treatment depends on the mechanism.

Procedural resistance is governance doing its job. The initiative must pass through existing approval processes, stage-gates, compliance reviews, and governance frameworks designed for a different type of work. These processes require revenue forecasts for something that has never existed and ROI projections grounded in historical data that, by definition, a new initiative cannot provide. The innovation gauntlet was built to evaluate known quantities. Genuine novelty cannot pass through it on the gauntlet's own terms.

Govindarajan catalogues the functional channels precisely. HR refuses to waive compensation rules for specialist hires the pilot needs. IT claims the project is too small to warrant exceptions to standard systems. Each function is applying its procedures correctly. The aggregate effect kills the initiative. No single department is responsible. All of them are.

Larry Keeley's research at Doblin adds a subtler dimension. Organisations have procedures for product development: stage-gate processes, R&D budgets, product roadmaps. They have no equivalent procedures for profit model innovation, structure innovation, or process innovation. The absence of procedures is itself procedural resistance. Not blocking, but channelling. Innovation flows where the pipes already exist.

Resource competing is stewardship doing its job. Every euro and every hour spent on the innovation initiative is not spent on existing operations. Operations have dedicated budgets, established KPIs, and people whose performance reviews depend on delivery. Manufacturing is upset about scheduling small, inefficient production runs for the pilot. General managers of existing product lines are anxious about cannibalisation. The sales team is reluctant to push a product without a track record.

None of these people are wrong. They are protecting resources they are accountable for. The innovation is competing for attention against activities that are better understood, lower risk, and more directly tied to this quarter's results. Operations always wins that competition. The returns are measurable and immediate.

Standard dilution is quality assurance doing its job. The innovation threatens brand consistency, operational norms, or quality frameworks. Marketing worries about brand damage if the new product fails. Technology insists the innovation must work with existing systems. Compliance requires the new initiative to meet frameworks designed for mature operations.

Keeley's empirical research, analysing over 2,000 innovations, shows the gravitational force of this mechanism. Organisations overwhelmingly cluster innovation effort in product performance and systematically neglect configuration types (profit model, structure, process) and experience types (service, channel, brand). Average innovators use 1.8 types of innovation per offering. Top companies use 3.6. Product innovation is the safe choice because it reinforces existing standards: better features, improved quality, familiar territory. Standard dilution does not just block unfamiliar innovation. It pulls effort toward the most familiar kind.

Passive waiting is risk management doing its job. The organisation declines to commit resources until the innovation has proven itself. But proof requires resources. So the pilot is under-resourced, the timeline is extended, and leadership reviews the underwhelming results with exactly the scepticism the under-resourcing guaranteed. A self-fulfilling prophecy dressed as prudence.

This is the most common mechanism, the most invisible, and the most damaging. It does not feel like resistance. It feels like good judgement. BCG's zombie innovation data is passive waiting measured at industrial scale: eighty-three per cent priority, three per cent readiness.

Why this is not dysfunction

Roger Martin provides the sharpest articulation of the structural logic at work. His "Presumption of Guilt" concept (2022) names the asymmetry precisely: in business, the status quo enjoys the presumption of innocence. Innovation carries the burden of proving it will succeed in the future. That burden is logically impossible for anything genuinely new to meet.

The existing model has track record data. The innovation, by definition, has none. Martin extends this in his 2025 Nudgestock piece: the analytical frameworks organisations use to evaluate projects enforce a methodology that implicitly assumes the future will be identical to the past. Innovation is being asked to prove itself inside a system designed to validate continuity. The analytical deck is stacked before the conversation begins.

Martin's Strategy Choice Cascade shows why this is structural, not cultural. Choices in the cascade, from winning aspiration through where-to-play, how-to-win, must-have capabilities, to enabling management systems, lock together like puzzle pieces. The management systems layer encompasses resource allocation, decision rights, and measurement. Martin calls shared capabilities across business units "reinforcing rods," like steel running through a concrete building. They create consistency. They also resist anything that would break it.

This is the structural trap. The tighter the cascade integration, the stronger the competitive advantage. And the stronger the competitive advantage, the more violently the system resists anything that would disrupt the integration. The most successful organisations have the strongest immune response. This is not a flaw in the system. It is the system working as designed.

Kotter and Schlesinger's research on change resistance (HBR, 1979) arrives at the same place from a different direction. Among their four reasons people resist change, one stands out: "different assessments of the situation." Resisters may disagree on substantive grounds. They may see more costs than benefits, not just for themselves but for the organisation. Managers, Kotter acknowledges, are not always in possession of all the facts. The resisters are sometimes right.

Keeley's clustering data reveals the downstream consequence at industry scale. Product innovation has the lowest return on investment and least competitive advantage of all ten types. Feature wars devolve into what Keeley calls expensive races to parity. Configuration innovation (profit model, structure, process) is both the most defensible and the type that triggers the strongest immune response across all four mechanisms simultaneously: new governance required, cross-functional resources contested, existing norms broken, no precedent available.

The immune response does not just block innovation. It channels it toward the least threatening form. Organisations innovate where the immune system tolerates it: incrementally, in product features, within existing structures. The types of innovation that would create lasting advantage are exactly the types the organisation is configured to reject.

When the feature becomes a bug

The immune response is adaptive when the environment is stable. Governance, stewardship, quality assurance, and risk management are useful when the underlying activities and practices remain roughly constant. The response becomes pathological when the context shifts and the organisation does not.

Simon Wardley identifies the specific mechanism: co-evolution. When underlying activities evolve (computing shifts from product to utility, for example), practices must co-evolve (from scale-up to scale-out architecture, from capital expenditure to operational expenditure). Organisations resist this double transformation: both the activity change and the practice change. The immune response fires twice, and the compounding inertia becomes structural.

Wardley's punctuated equilibrium insight makes this concrete. Organisations expect gradual change because that is what the long product era delivered: thirty to forty years of incremental improvement. The product-to-utility transition is different. It is slow until it is suddenly fast. By the time the evidence is overwhelming, Wardley observes, it is often too late. The immune response kept working long after the context it was protecting had become obsolete.

The practical question for anyone running a corporate innovation initiative is whether the immune response they're encountering reflects a genuine defence of something still valuable or a defence of something the organisation should have released two years ago.

This is where diagnostic specificity matters. In my Critical Path Layers framework for corporate innovation, Layer 2 (Organisational Feasibility) includes a stakeholder architecture mapping and a veto audit: who has formal or informal power to kill the initiative, and what are they defending? The veto set in large organisations is often larger than the approval set. There are many ways for an initiative to die and few ways for it to survive.

The veto audit forces a classification that most change management approaches skip. For each blocker, the question is not "how do we get past them" but "is their defence legitimate in the current context?" Some blockers have real concerns the initiative team has not addressed. Some are defending a position the market has already moved past. Treating both the same way is how organisations waste years on stakeholder engagement that should have been structural change.

Locating the signal

If you run or sponsor an innovation initiative inside a large organisation, these questions locate where you are.

Which mechanism is active? Is the initiative being blocked by existing processes (procedural resistance), starved of resources (resource competing), diluted to fit current norms (standard dilution), or left waiting for evidence it cannot produce without commitment (passive waiting)? Name it. The mechanisms require different responses.
What function is the resistance performing? Governance? Stewardship? Quality assurance? Risk management? Is that function still serving the organisation in the current context, or is it defending a position that the environment has already moved past?
Has the context shifted? Wardley's co-evolution test: have the underlying activities evolved while the practices remain static? If so, the immune response is protecting the wrong thing. The defence is legitimate in a context that no longer exists.
Are you working on the right layer? The immune response is often a signal about sequencing, not about stakeholder management. An initiative triggering maximum immune response across all four mechanisms is usually a transformation-class initiative that has skipped foundational work. The organisation is not being difficult. The organisational ground has not been prepared.

If the immune response is firing on all four mechanisms, you are probably working on the wrong layer. Step back. Identify the unresolved dependency upstream. Solve that first.

The immune response is not the enemy. It is diagnostic information. Read it.

Alexandra Najdanovic is the founder of Aieutics, working with leadership teams on strategic transformation, innovation sequencing, and AI-readiness.