At some point in the last decade, most large organizations made the same bet: that innovation was a resource problem.
Not enough ideas? Build a lab. Not enough creativity? Run a hackathon. Not enough new thinking? Hire a Chief Innovation Officer, give them a budget, and wait. The assumption underneath all of it was that the organization's problem was a deficit — of ideas, of creativity, of raw innovative capacity — and that the solution was to import or manufacture what was missing.
I've watched this play out in organization after organization. And the results are remarkably consistent: beautiful innovation theaters, modest outcomes, and a creeping sense among leadership that their people "just aren't entrepreneurial."
Here's what I actually believe: the ideas are already there. They're sitting in the heads of your engineers, your customer service reps, your middle managers, your frontline teams. The people closest to your customers, your operations, and your real problems almost certainly have a clearer view of what needs to change than anyone in a dedicated innovation function.
They're just not telling you. And they have very good reasons not to.
What Gets Learned
People don't arrive at organizations afraid to share ideas. They learn to be.
It happens gradually, through a series of small but legible signals. An idea raised in a meeting gets redirected to a more pressing agenda item. A proposal submitted through official channels comes back months later as someone else's initiative — or not at all. A team member who challenged an existing process gets quietly labeled "not a team player." Someone who voiced a dissenting view in an all-hands gets passed over in the next round of promotions.
None of these events need to be dramatic. They don't need to be malicious. They just need to happen consistently enough that people learn the lesson: the cost of speaking up is real, and the reward is uncertain at best.
Amy Edmondson's research on psychological safety captures this with precision. The calculation people make — often unconsciously — isn't "is this a good idea?" It's "is it safe to say this here?" And in most organizations, for most people, the honest answer is some version of no.
The result isn't silence exactly. People still participate. They still attend the innovation workshops and fill out the idea submission forms. But what they share in those formats is a carefully filtered version of what they actually think — safe enough to say, bland enough not to threaten anything, stripped of the real friction that might make it worth hearing.
What your innovation program is getting isn't the ideas in your organization. It's the ideas people are comfortable performing in front of leadership.
The Trust Deficit
Call it what it is: a trust deficit.
Not distrust in the conspiratorial sense — most employees don't think leadership is out to get them. But trust in the specific sense that matters for innovation: the belief that honesty won't be punished, that imperfect ideas will be engaged with rather than dismissed, that the people who raise uncomfortable questions won't quietly pay a social or professional price for doing so.
This kind of trust isn't built through values statements or innovation culture decks. It's built through behavior — specifically, through what leaders do when someone says something that's inconvenient, unfinished, or wrong.
The leaders who build genuinely innovative cultures share a specific habit: they respond to imperfect ideas with curiosity instead of judgment. Not false positivity — they're not cheerleaders for every half-formed thought. But they ask questions before they evaluate. They make it visibly safe to be unfinished. And over time, their teams learn a different lesson: that the cost of speaking up here is low, and the reward is real.
That behavioral pattern is harder to implement than a hackathon. It requires leaders to manage their own reactions in real time, repeatedly, in front of their teams. It requires a kind of disciplined vulnerability — the willingness to sit with uncertainty, to not immediately evaluate and direct, to model the open-minded engagement you're asking your people to risk.
Most innovation interventions don't touch this at all. They add process and subtract permission structures, and then wonder why the pipeline is thin.
What Theater Looks Like
A useful diagnostic: count the ratio of innovation structures to honest conversations in your organization.
Innovation structures are visible. The lab, the sprint, the designated ideation time, the suggestion box with a submissions counter on the intranet. Honest conversations are harder to see, but you know them when they're absent. They're the feedback that never makes it to leadership. The meeting after the meeting where the real concerns get aired. The exit interview where someone finally says what they'd been thinking for two years.
If your organization has more structures than honest conversations, you're running theater. You've built the stage and the lighting without writing the play.
The irony is that the structures themselves can actively suppress the honest conversations. When people see that there's an Official Innovation Process, they conclude that unsanctioned ideas — the ones raised outside the process, the messy ones that don't fit the framework — aren't welcome. The process signals what kind of thinking is permitted. And the thinking that doesn't fit the form gets left out.
Four places to start:
Make it safe to criticize existing things, not just propose new ones. The most valuable ideas in most organizations aren't additions — they're deletions. The product feature nobody uses, the process that made sense five years ago, the meeting that should have been an email. Create explicit permission to name what isn't working, and watch what surfaces.
Respond to bad ideas the same way you respond to good ones — with genuine engagement. The moment you dismiss an idea quickly, you haven't just responded to that idea. You've sent a message to everyone in the room about what happens to people who share imperfect thinking. The cost of a dismissive reaction is always larger than it looks.
Close the loop, loudly and specifically. One of the fastest ways to kill idea-sharing behavior is to let ideas disappear. If someone raised something three months ago and never heard back, they didn't learn that the idea wasn't chosen. They learned that sharing isn't worth the effort. Even a "we considered this and here's why we went a different direction" is an investment in future honesty.
Look for who's stopped talking. In most organizations, there's a subset of people who used to push back, used to ask hard questions, used to offer unconventional perspectives — and quietly stopped. Find them. Not to demand their ideas, but to understand what happened. Their silence is a direct record of what your culture has been teaching.
Your organization isn't short on ideas. It's short on the conditions that make sharing ideas feel worth the risk.
No lab fixes that. No hackathon fixes that. What fixes it is leadership behavior, practiced consistently, over time — the slow, unglamorous work of making it genuinely safe to say what you actually think.
That's not an innovation initiative. That's a leadership practice. And it's available to you right now, without a budget line, without a new hire, without a framework.
The question is whether you're willing to start with yourself.
JL Heather is co-founder of Centered, an innovation consultancy that helps senior leadership teams build the cultures and capabilities needed to sustain breakthrough performance.