Every large company has an innovation program of some kind. Labs, centers of excellence, internal accelerators, hackathons, design sprints, venture arms, partnership programs. The investment is real — dedicated staff, external consultants, conference budgets, prototype facilities. The output, in most cases, is a rolling series of presentations, pilot proposals, and proof-of-concept projects that never become products anyone can buy.
I've run innovation programs for Nike, Coca-Cola, Hallmark, P&G, and other Fortune 500 clients. The pattern across those engagements is consistent: organizations with programs that ship are structurally different from organizations with programs that produce slide decks. The difference is not effort, talent, or budget. It's a set of specific structural decisions about authority, team size, metrics, and executive sponsorship — and most companies have gotten at least one of them wrong.
The term "innovation theater" has been in circulation long enough to be a cliché. Naming the pattern hasn't made it less common. If anything, the proliferation of innovation vocabulary — "fail fast," "design thinking," "moonshot" — has made it easier to dress up theater as strategy. The diagnostic I use is simpler than any framework: in the last 24 months, how many products or services from your innovation program have been commercialized and are generating revenue? If the answer is zero, you're running theater regardless of what the program looks like from the outside.
The theater inventory:
activities that signal commitment
but don't produce output.
Innovation theater has a recognizable set of recurring activities. Each one can be valuable in specific contexts — and each one is frequently deployed as a substitute for the harder work of actually building and shipping something. The question is whether these activities feed into a commercialization pipeline or replace one.
Innovation theater persists
because it serves real
organizational needs.
It would be easier to fix innovation theater if it were purely dysfunction. Theater persists because it serves real organizational purposes — and that's what makes it hard to displace even when everyone knows it isn't working.
It signals strategic intent without requiring resource commitment. A large company visibly investing in innovation programs can point to that investment in earnings calls, recruitment pitches, and strategy reviews without committing to specific outcomes. The program is the signal. What it produces is secondary. This is a communication function, not an innovation function, and it serves a real purpose for the organization.
It provides a safe container for organizational learning. Innovation programs give large organizations a structured way to explore adjacent ideas without the business case rigor that governs core business decisions. That exploratory function has real value — many genuine innovations start as experiments that don't look like business cases. The problem is when exploration never transitions to commercialization.
"The hardest conversation in corporate innovation is telling a leadership team that their program is theater. The second hardest is convincing them to fix the structure rather than just try harder."
It protects careers. Innovation programs that produce prototypes and pilots let individuals demonstrate activity and creativity without the career risk of a failed commercial launch. A pilot that ends quietly is far less damaging than a scaled product that fails publicly. Theater is a career risk management strategy embedded in organizational structure.
Five signals your innovation
program is theater. Most companies
have at least three.
| Signal | What It Looks Like | What It Means |
|---|---|---|
01 — Output Metric What do you measure? |
Counting ideas generated, pilots launched, partnerships formed, events attended | Activity metrics replace outcome metrics. You're measuring inputs because you have no outputs to measure. |
02 — Decision Authority Who can say yes? |
Innovation team can propose but not decide. Every advancement requires committee approval. | The team cannot self-authorize past the proposal stage. Real work requires real authority. |
03 — Resource Access How does work get resourced? |
Each project requires a separate resource request process through normal budgeting channels | The innovation team doesn't have standing budget to act. Each project competes with operations for funding. |
04 — Failure Response What happens when a project fails? |
Failure is treated as a negative event; project leaders face soft career consequences | The culture penalizes risk-taking regardless of what the values poster says. People will optimize for avoiding failure, not for shipping. |
05 — Commercialization Path How does a project become a product? |
No defined path from innovation team to commercial launch. Projects "hand off" to business units at some undefined point. | Without a defined commercialization path, projects die in the handoff. The innovation team builds; nobody takes it to market. |
Programs that actually ship
are structurally different
in four specific ways.
Across the innovation programs I've run and studied, the ones that consistently produce commercialized output share four structural characteristics. None of them are radical. All of them are uncommon at large companies.
Small Team Mandate
Programs that ship run on teams of three to six people with full-stack capability — product, design, and commercial sense in the same room. Large innovation teams — fifteen, twenty, thirty people — generate coordination overhead and diffusion of accountability that slows output. The best programs I've run or advised have been small enough that everyone knows who owns what, and large enough to cover the required capabilities. When teams grow past six, the first thing to go is speed.
The Autonomy Requirement
Effective innovation teams have genuine decision authority within a defined scope — not "influence" or "recommendation" authority, but actual authority to spend budget, make product decisions, and advance projects without committee approval. The scope of that authority should be narrow enough to feel manageable to the sponsoring executive. But within that scope, the team must be able to act without asking permission. Every approval gate is a speed cost. Speed is the primary variable separating programs that ship from programs that don't.
The Speed Signal
Programs that ship establish a specific, short time horizon for their first output. The goal is not a perfect product — it's something real in market within 90 days. That constraint forces the team to scope ruthlessly, decide quickly, and prioritize learning over completeness. The 90-day signal also creates organizational credibility: when an innovation team ships something real within three months of standing up, the rest of the organization takes it seriously. That credibility unlocks the resources and cooperation needed for bigger swings.
Defined Commercialization Path
The transition from innovation team to commercial operation is where the majority of good ideas die in large companies. Programs that work have defined this transition before the first project starts: which business unit will own a commercialized product, what the handoff criteria are, who makes the call on whether a project advances, and what happens to the team members who built it. Ambiguity in that handoff creates the pilot treadmill — projects that keep getting extended because nobody wants to own the risk of a commercial launch.
The executive sponsor is
not a formality. They're
the whole game.
In my experience running innovation programs for large companies, the single most predictive variable for whether a program ships is the quality and commitment of the executive sponsor. Not team quality. Not budget. Not methodology. The sponsor.
The right executive sponsor has three characteristics that are non-negotiable. First, genuine organizational authority — not just a title, but the ability to move resources, override committee decisions, and protect the team from the organizational antibodies that will attack any novel idea that threatens existing revenue streams. Second, skin in the game — their reputation and career advancement are partially tied to whether the program produces real output, not just activity. Third, they understand the difference between managing an innovation team and managing an operations team, and they don't collapse the two.
Every large organization has antibodies — people and processes that exist to protect the existing business model from disruption. They are not villains. They are rational actors protecting things that generate real revenue and real employment. An innovation team that proposes a new channel, a new pricing model, or a new product category will inevitably threaten someone's budget, headcount, or territory. Those people will push back — through committee processes, risk reviews, cross-functional concerns, and the variety of friction that large institutions specialize in producing.
The executive sponsor's job is to run interference. Not to eliminate the antibodies — they serve a real function — but to create enough protected space for the innovation team to move from idea to pilot to market proof before the antibodies can kill it. A sponsor who won't do this is a name on an org chart that provides cover without providing protection. That's the most dangerous configuration: it signals the program has backing without actually providing it.
The program architecture
that produces shipped products
instead of slide decks.
Across multiple Fortune 500 innovation engagements, the program architecture that consistently produces output looks like this:
Defined scope with a clear commercial thesis. The program has a specific problem to solve and a clear view of what success looks like. "Drive innovation in our category" is not a commercial thesis. "Build a direct-to-consumer channel that captures the 25–35 demographic we're losing to challengers, targeting $10M revenue in 24 months" is. The specificity of the thesis determines the quality of the work.
Standing budget, not project-by-project funding. The innovation team controls an annual budget without re-approval processes for individual projects below a defined threshold — typically $2–5M for programs operating inside Fortune 500 companies. Projects above that threshold require sponsor approval. Below it, the team acts without a committee. This is the single most impactful structural change most companies can make.
Metric alignment to commercialization, not activity. The program's success metrics are revenue generated, products launched, and customers acquired — not ideas generated, pilots run, or partnerships formed. If the program lead's annual review is based on activity metrics, you've already lost. Metrics shape decisions, and activity metrics produce activity.
A defined kill-or-advance gate at 90 days. Every project in the program has a 90-day review at which the team presents market evidence — real customers, real usage, real revenue — and the sponsor makes a binary call: advance with increased resources or kill it. No extensions, no "continue at current scope," no third-quarter pilots. The discipline of this gate is what separates programs that ship from programs that accumulate perpetual pilots.
When to kill the program
vs. when to restructure it —
and how to tell the difference.
Not every theater program is worth restructuring. Some have accumulated enough organizational history, staffing commitments, and political capital that restructuring is harder than starting fresh. The decision between restructuring and killing depends on two variables: whether the right executive sponsor exists and is willing to commit, and whether the current team has the capability to operate in a high-autonomy, high-accountability environment.
Kill the program if the sponsoring executive treats innovation as a reporting function rather than a commercial function. Kill it if the team has been conditioned to optimize for presentation quality over market output. Kill it if the commercialization path doesn't exist and nobody is willing to define it. Starting fresh with a clear mandate, a committed sponsor, and a small team empowered to act is faster and cheaper than restructuring an organization that has optimized for theater.
Restructure if the sponsor is genuinely committed and has real authority, if the core team is capable and just needs permission to operate differently, and if the organizational infrastructure to support commercialization exists but hasn't been connected to the innovation program. Restructuring works when the inputs are right and only the structure is wrong.
The measure of an innovation program is how many products it has shipped that are generating revenue. Not ideas generated, not pilots run. By that measure, most programs are underperforming dramatically relative to their investment. Fixing it is not a culture problem or a talent problem. It's a structure problem, and structure is fixable.
Running an innovation program that isn't shipping?
I've run innovation programs for Nike, Coca-Cola, Hallmark, and P&G — and I've seen the patterns clearly enough to diagnose them quickly. If your program is producing presentations instead of products, the conversation usually starts in the same place. The form takes two minutes.
Start the conversation Enterprise Innovation practice →