The corporate innovation lab is often the most expensive theatre production in business. We’ve all seen the script: a “glossy” launch event, a handful of entrepreneurs-in-residence with cool sneakers, and a slide deck full of future-state revenue curves that hockey-stick toward the moon. Yet, a year later, the projects are quietly wound down, the “innovators” return to their consultancy firms, and the sponsor pats themselves on the back for having “tried innovation.”
Why does this cycle repeat? It isn’t for a lack of talent or intent. It’s because we’ve built a system where the core business needs predictability and efficiency, while innovation requires uncertainty and optionality. When these two worlds collide without a bridge, the core business—with its procurement gravity, legacy IT debt, and risk-averse governance—invariably wins. If we want to move beyond innovation theatre, we need to stop designing for novelty and start designing for integration.
The Transfer Gap: Why Great Ideas Die in Purgatory
There is a recurring failure mode in corporate incubators: the lack of a practiced handover mechanism. Success in a lab is often measured by outputs—demo days, patents, or prototypes. But in the real world, an experiment that never makes it into a product roadmap or a go-to-market plan is fundamentally useless. Many labs find themselves in a state of purgatory: neither fully owned by the core business nor independent enough to scale on their own.
Google’s Area 120 has famously illustrated both the potential and the peril of this model. While some ideas flourish, many are cancelled when corporate priorities shift. This isn’t just a Google problem; it’s a structural tension. As noted by my recent analysis on incubator failure, these labs often fail because they don’t change the day-to-day habits that suffocate new ideas. To fix this, we must treat experiments as products from day one, with clear “kill criteria” and a defined path toward the production stack.
Protecting the Breakout from Corporate Gravity
To make innovation survive the journey from lab to line, we have to protect it from the very bureaucracy that keeps the main business running. Procurement, security, and compliance are optimised for stability. If a new IoT solution or an AI-driven service requires a bespoke middleware that the core IT team refuses to maintain, it is effectively a “dead letter” before it even launches.
Product leaders should insist on three practical shifts to counter this:
- Architect for Integration: From the first sprint, design within the constraints of the core data models and security protocols. If it can’t be integrated, it shouldn’t be built.
- Embed Cross-Functional Accountability: Stop the “handover” culture. Create teams that include a delivery sponsor from the core organisation who has “skin in the game.”
- Shift the KPIs: Replace prototype counts with adoption metrics. Are people using it? Is the cost-to-serve sustainable? If a lab cannot define a plausible adoption path, the work belongs back in discovery, not in development.
Avoiding the “Rot” of Misaligned Incentives
We are currently seeing a broader trend of “enshittification”—a term coined by Cory Doctorow to describe how platforms decay when they prioritise rent extraction over user value. This same “rot” can infect internal innovation. When a lab is incentivised by short-term business metrics or PR wins rather than genuine user outcomes, the quality of the “innovation” declines, and noise grows.
In the gaming industry, commentators have pointed to the decay in subscription curation, where services that once grew value for players now prioritise rent-seeking deals. This is a cautionary tale for any CDO or CTO. If your innovation pipeline is merely a tool for short-term margin padding, you aren’t innovating; you are merely liquidating your brand’s future for a better quarterly report.
Building a Disciplined Pipeline for the Long View
Real innovation isn’t about the “new year, new budget” hype. It’s about a systematic, repeatable approach to moving from opportunity to operational deployment. Whether it’s a manufacturing firm like the illustrative Aurora Windows or a global telecommunications giant, the “secret sauce” is the same: rigorous learning plans and protected runway.
Instead of chasing the latest hype cycle—be it the metaverse or the current AI frenzy—leaders must look at technology cycles with a longer lens. From the Luddites of the industrial revolution to the two waves of the mobile revolution I witnessed at Nokia, the winners aren’t those who shout the loudest during the bubble. The winners are those who build autonomous, empowered teams capable of navigating the “boring” parts of scaling: governance, unit economics, and user empathy.
If you are leading an innovation initiative today, ask yourself: is your team empowered to kill a project that isn’t working, or are they just performing for the next demo day? True innovation starts with the courage to dismantle the theatre and replace it with a factory for repeatable value. Start by identifying one “theatrical” metric in your lab and replace it with a hard adoption KPI today.
Leave a Reply