- What Is Innovation Theater, and How Big Is the Problem?
- What Did Innovation Labs Get Wrong About Skunk Works?
- What Are the 12 Patterns That Kill Innovation Labs?
- What Does an Innovation Lab Really Cost?
- What Is the Five Year Lifecycle of Lab Failure?
- How Do You Tell Innovation Theater From Real Innovation?
- Which Companies Innovate Without a Lab?
- What Is the Anti-Lab Innovation Framework?
- What Five Questions Should You Ask Your Innovation Lab?
- How Do You Convert a Lab Into a Capability?
- Frequently Asked Questions
- About the Stagnation Assassin
What Is Innovation Theater, and How Big Is the Problem?
Innovation theater is the practice of making a visible show of innovating while the actual adoption lags far behind the performance. The term was popularized by fintech innovation veteran Rich Turrin, who described labs that function as stage sets rather than agents of change. The test is simple: ask what revenue the lab has generated.
Walk into a Fortune 500 innovation lab and the show is genuinely impressive. Sticky notes covering every wall. Bean bags and a ping pong table signaling creativity. Polished demos of the future of banking, retail, or manufacturing. Bright people, palpable energy, limitless apparent potential. Then ask the revenue question and the room goes quiet.
Fifty million dollars over five years. Two hundred patents filed, a thousand ideas generated, zero products launched. A competitor with no lab shipped twelve products in the same window by embedding innovation into daily operations. Patents are not products. Demos are not revenue. Sticky notes are not strategy.
Labs proliferated across financial services, healthcare, and retail over the last decade, ranging from a conference room with a whiteboard to purpose built facilities of twenty thousand square feet. I am not going to hand you a precise adoption percentage, because the credible ones do not exist and the ones that circulate are vendor surveys with elastic definitions. The scale is obvious enough without a fake denominator, and so is the outcome: most of these labs do not deliver what was promised at the ribbon cutting.
What Did Innovation Labs Get Wrong About Skunk Works?
Nearly every innovation lab claims Lockheed’s Skunk Works as its ancestor, then copies the aesthetic and discards the mechanism. Kelly Johnson’s team delivered the XP-80 prototype in 143 days, beating its contracted deadline by seven. What produced that was not creative freedom. It was a hard deadline, a named customer problem, and consequences.
The origin matters because the modern retelling inverts it. In 1943, German jets had appeared over Europe and the Army Air Tactical Service Command needed an answer. Johnson assembled a hand picked team in a rented circus tent beside the Lockheed plant in Burbank, working ten hour days, six days a week, entirely under his command. Note that this was Lockheed Aircraft Corporation, decades before the Lockheed Martin merger, and note something else the legend usually omits: the P-80 arrived too late for the war it was built for. The deadline was still real, and the constraint still produced the aircraft in a quarter of the time a normal program would have taken.
Every innovation lab claims Skunk Works as inspiration and leaves out the part that mattered. Johnson had a contracted deadline, a named customer problem, and consequences for missing. No bean bags, no ideation sessions. If you need a special building in order to be innovative, you have already answered the question.
Set the two side by side. Skunk Works ran on complete autonomy from corporate bureaucracy, non negotiable deadlines, direct connection to an urgent customer need, a small team with absolute authority, and success measured by a working aircraft. The modern lab runs on open ended ideation, isolation from real business constraints, no clear success metric, distance from actual customer problems, large teams with ambiguous authority, and success measured in ideas generated and patents filed. Skunk Works existed to solve an existential problem. Most labs exist to solve an image problem.
What Are the 12 Patterns That Kill Innovation Labs?
Twelve recurring patterns account for most lab failures, and they compound rather than operate alone. Rich Turrin’s 2018 article on why most innovation labs are failing named the dirty dozen framing from inside the fintech lab world. What follows is my own field taxonomy, built from the same failure mode in industrial settings.
- The ROI delusion. “We are a lab, we do not need ROI” is the battle cry of a doomed initiative. When a lab exempts itself from financial accountability, it exempts itself from its own reason for existing.
- The technology fetish. Teams fall in love with blockchain, AI, or quantum computing and never ask whether the technology solves a problem a customer has. Chase the customer understanding first and the technology second.
- The people problem. Labs optimize the technology and ignore the humans who must adopt it, producing solutions that require organizational changes nobody wants and behavior shifts nobody will make.
- The leadership mismatch. Reporting the lab to a CIO or CTO puts it under leaders who have spent careers optimizing for stability and uptime. Those are the right instincts for infrastructure and the wrong ones for experimentation.
- The integration impossibility. Labs develop innovations the core business has no mechanism to absorb. Without a defined path to production, even the good ones die inside the lab.
- The measurement vacuum. Labs count ideas generated instead of problems solved, patents filed instead of products launched, demos built instead of revenue booked, and press coverage instead of customer adoption.
- The talent trap. Labs hire innovation specialists who have never shipped a product, scaled a business, or been held to a market constraint. Talented people with no shipping scar tissue produce beautiful impossibilities.
- The timeline fantasy. Without deadlines, innovation degrades into philosophy. Labs operate on geological time while their markets move quarterly.
- The validation void. No market validation, no customer feedback, no competitive analysis. The lab builds in a vacuum chamber, solving problems that do not exist for customers who will not pay.
- The internal rejection. Even a genuinely valuable innovation meets organizational antibodies. The core business views the lab with suspicion, resentment, or indifference, and any of the three is fatal to adoption.
- The culture clash. Innovation requires tolerating failure, moving fast, and holding autonomy. Corporations punish failure, demand process, and require control. The mismatch is structural, not attitudinal.
- The expectation inflation. Having spent millions on the space and the furniture, executives expect breakthroughs on a schedule. When they do not arrive, patience evaporates and funding follows it out the door.
What Does an Innovation Lab Really Cost?
The budget line understates the cost by a wide margin. Four categories compound: direct waste on facilities and salaries producing nothing, opportunity cost from diverted talent and management attention, cultural damage as cynicism spreads, and strategic blindness, which is the most expensive of the four because it is the one nobody books.
Hypothetical: a five year lab at meaningful scale might carry five million in facility costs, fifteen million in salaries for a team of twenty, ten million in technology and equipment, ten million in consultants and programs, five million in marketing and events, and five million in overhead. That totals fifty million dollars. If the products launched number zero and the revenue generated is zero, the return is negative one hundred percent regardless of how many patents sit on the wall.
I am deliberately not modeling the alternative investment as a tidy comparison. The version of that calculation floating around business writing assumes a success rate and a return multiple, both invented, and the arithmetic usually does not survive checking. What I will assert is the qualitative claim, which is stronger anyway: capital distributed across product teams that must ship to customers is subject to a market test that lab capital never faces.
Opportunity cost is where the real damage sits. Top talent diverted from revenue generating work. Capital that could have funded proven initiatives. Management attention consumed by theater. Time your competitors used to pull ahead while you were planning a transformation that never shipped.
Strategic blindness is the one that kills companies. The lab creates the illusion of innovation. Executives point at it as evidence of forward thinking while the actual business model decays underneath them. It is corporate morphine: it numbs the pain of disruption without treating the disease, and the patient feels fine right up until they do not. Harvard Business Review’s work on growth outside the core makes the same structural point about why adjacent bets fail when they are disconnected from the capabilities that actually produced the company’s advantage.
What Is the Five Year Lifecycle of Lab Failure?
Labs fail on a predictable schedule. Year one is the honeymoon of press coverage and impressive demos. Year two brings the reality check as integration stalls. Year three is the pivot, with new leadership and redefined metrics. Year four is decline and departures. Year five is the quiet death by reorganization.
The tell is year three. That is when metrics get redefined to show success, which is the organizational equivalent of moving the goalposts and then congratulating yourself on the field position. If your lab has already renamed what it measures, you are further along this curve than the budget suggests, and the quick wins pressure arriving in year two was the early warning you missed.
How Do You Tell Innovation Theater From Real Innovation?
By output category, not by effort or sincerity. Theater produces slide decks, patent applications, demo videos, press releases, conference talks, and sticky note collections. Real innovation produces revenue growth, market share gains, customer acquisition, operational efficiency, and competitive advantage. Everything in the first list is an input dressed as a result.
The customer blindness underneath is the common cause. The UX researcher Jared Spool has described bank innovation labs built for the executives touring the floor rather than for the customers who would use the product, and the pattern generalizes well past banking. When a lab optimizes for impressiveness to visitors, it produces museum pieces. When it optimizes for implementation, it produces products. Those two objectives look similar in a planning meeting and diverge completely in the build.
Which Companies Innovate Without a Lab?
The companies that innovate consistently tend to violate lab orthodoxy entirely. Amazon distributes innovation across small autonomous teams with direct customer connection. 3M protects experimentation time inside regular roles. Google historically ran a similar model for engineers. The common factor is that none of them centralized innovation into a separate building.
Amazon’s approach embeds innovation in every team rather than one team, uses two pizza teams with genuine autonomy, connects builders directly to customer problems, and measures success by customer adoption. There is no separate innovation lab because innovation is not treated as a department.
3M’s 15 percent time makes innovation part of everyone’s job, protects time for experimentation inside the normal role, and provides a clear path from idea to product. Failures are expected and budgeted rather than punished, and the successes become internal legends that reinforce the behavior.
Google’s 20 percent time belongs in the past tense, and that is instructive rather than disqualifying. The program was widely reported to have faded well over a decade ago as the company scaled and management focus tightened. The mechanism worked while the culture supported it, and it decayed when the surrounding incentives changed. That is exactly the point: distributed innovation is a cultural commitment, not a policy you install once.
What Is the Anti-Lab Innovation Framework?
Five moves replace the lab with a capability: embed innovation in every role rather than one department, connect work to validated customer problems, set aggressive deadlines with enforced kill or scale decisions, measure business outcomes rather than activity, and build the path to production before you build the prototype.
Embed innovation everywhere. Make it part of everyone’s job, reward innovative thinking inside regular roles, create protected time and space for experimentation, and put it in performance reviews. If innovation is not in the review, it is not in the job.
Connect to real problems. Start with customer pain, validate the problem before designing the solution, test with real users immediately, and measure success by adoption rather than by approval.
Set aggressive deadlines. Ninety day sprints for proof of concept, six months maximum for a pilot, and enforced kill or scale decisions at the gate. Speed over perfection, because perfection is how a project avoids ever being judged.
Measure what matters. Revenue impact, customer acquisition, cost reduction, time to market, user adoption, competitive position. Every one of those is checkable by someone outside the team, which is the property that ideas generated and patents filed conspicuously lack.
Create clear paths to production. Put operations people on the innovation team from day one, plan integration before the build, give the core business a stake in the outcome, and commit the scaling resources up front rather than arguing about them after the pilot succeeds.
What Five Questions Should You Ask Your Innovation Lab?
Five questions expose whether you fund innovation or theater, each demanding a number rather than a narrative. What was the last product it launched? How much revenue has it generated? What share of its innovations reach customers? How many has the core business adopted? What is the fully loaded cost per implemented innovation?
If you cannot answer those with specific figures, you already have your answer. Note what the questions have in common: every one measures something that leaves the building. A lab can produce enormous internal activity and score zero on all five, and the reason that happens so often is that nobody in the reporting chain has an incentive to ask. Adding these five to the quarterly review is the cheapest intervention available to you, and it takes one meeting.
How Do You Convert a Lab Into a Capability?
Five steps convert theater into capability: kill the lab mindset that treats innovation as a place, distribute innovation goals across teams, connect every effort to validated customer reality, compress timelines with enforced decision points, and measure ruthlessly against ordinary business standards rather than special innovation ones.
- Kill the lab mindset. Innovation is a practice, not a location. Everyone innovates or nobody does. Integration beats isolation and execution beats ideation, and if that sounds obvious it is worth asking why the org chart says otherwise.
- Distribute innovation. Give every team innovation goals, allocate real time for experimentation, reward shipped innovations rather than filed patents, and make failure cheap while making the learning from it mandatory.
- Connect to reality. Start from customer problems, validate with market evidence, build with implementation constraints in the room, and measure with the same business metrics you apply everywhere else.
- Speed up everything. Set ninety day proof points, kill slow projects fast, treat a quick failure as a successful experiment, and scale the winners immediately rather than studying them.
- Measure ruthlessly. Track innovation ROI, compare it against your ordinary investment returns, and hold it to business standards. Celebrate profit, not process. This is the same orthodoxy discipline applied to the one function that has convinced everyone it deserves an exemption.
Your lab is currently building either the future or its own mausoleum, and the patents on the wall are evidence of one or the other. The question was never whether you have an innovation lab. It is whether you have innovation, and if the honest answer requires a special building, you have already answered it.
Frequently Asked Questions
Are all innovation labs a waste of money?
No. Labs that carry hard deadlines, direct customer contact, a defined path into the core business, and business grade metrics can work. The failure pattern is structural isolation combined with exemption from financial accountability. A lab that is measured like a business unit tends to behave like one.
What is the single strongest predictor that a lab will fail?
The absence of a defined path to production. A lab can hire well, pick good problems, and still produce nothing that reaches a customer if the core business has no mechanism and no incentive to absorb its output. Plan integration before the first prototype, not after it succeeds.
Why do patents make such a poor innovation metric?
Because a patent measures novelty and legal defensibility, not customer value or revenue. Filing is entirely within the team’s control, which makes it a comfortable metric that rises whether or not anything reaches a market. Any metric a team can hit without leaving the building will eventually replace the metric that matters.
Should the innovation lab report to the CIO or CTO?
Usually not. Those roles are built around stability, uptime, and risk reduction, which are the right instincts for infrastructure and the wrong ones for experimentation. Innovation reporting works better under a leader with profit and loss responsibility, because that person already answers for outcomes rather than for systems.
How long should you give a new innovation effort before judging it?
Set ninety day proof points and a six month pilot ceiling, with kill or scale decisions enforced at each gate. Open ended timelines are what turn innovation into philosophy. If an effort cannot show a customer facing signal within two quarters, the constraint is usually the problem selection rather than the timeline.
About the Stagnation Assassin
Todd Hagopian is a Fortune 500 transformation executive who has generated $3B+ in shareholder value across Berkshire Hathaway, Illinois Tool Works, Whirlpool, and JBT Marel, where he serves as VP of Global Product Strategy. Known as The Stagnation Assassin, he is the author of two published books: The Unfair Advantage: Weaponizing the Hypomanic Toolbox and Stagnation Assassin: The Anti-Consultant Manifesto. His blog is published in 15+ languages and read by operators worldwide. Bring him to your stage via his speaking page or connect with him on LinkedIn.
Founder of the Stagnation Intelligence Agency and a former Leadership Council member at the National Small Business Association, he holds an MBA from Michigan State University with a dual major in Marketing and Finance. Related reading includes the Stagnation Encyclopedia, the three essential leadership behaviors, technology in the HOT System, and the full author bio.
Take the five questions above into your next quarterly review and require a number for each one. Last product launched, revenue generated, share of innovations reaching customers, count adopted by the core business, fully loaded cost per implemented innovation. If four of the five come back as a story instead of a figure, you are funding theater and you now have the evidence to say so. Book a working session and we will run the audit together.