Innovation Isn’t a Spark. It’s a System We Choose to Build
- May 6
- 2 min read
By Ken Herron
I used to think innovation showed up in moments.
A breakthrough idea in a meeting. A flash of clarity in the middle of a conversation. The kind of spark people point to later and say, that’s where everything changed.
But the longer I’ve worked inside organizations, the more I’ve realized those moments are rarely the cause.
They’re the result.
Early in my career, I watched a team rally around a bold idea. It had energy. It had belief. It even had early traction. For a brief window, it felt like we were doing something that mattered.
And then, slowly, it disappeared.
Not because the idea was wrong. Not because the people lacked talent. But because the system around it didn’t know how to carry it forward. Decisions stalled. Ownership blurred. Feedback came too late to matter. What started as momentum turned into hesitation, and hesitation turned into silence.
That experience changed how I think about innovation.
We like to talk about creativity as the engine. Brainstorms. Whiteboards. Inspiration. But most organizations don’t fail at generating ideas. They fail at sustaining them.
Innovation breaks down not at the point of imagination, but at the point of structure.
If no one owns the problem clearly, ideas drift. If validation takes too long, learning slows. If feedback loops are delayed or diluted, teams optimize for comfort instead of truth. Over time, even the most promising ideas lose their shape.
What I’ve come to believe is this: innovation is not an act of brilliance. It’s a system of decisions.
It lives in how quickly a team can test something real. It shows up in how openly people can challenge assumptions without consequence. It depends on whether learning is treated as progress, not failure.
And most of all, it reflects what leadership chooses to reward.
I’ve seen environments where innovation is encouraged in language but constrained in practice. Where teams are told to experiment, but only within invisible boundaries. Where outcomes matter more than insight, and certainty is valued over curiosity.
In those environments, innovation becomes episodic. A burst here. A win there. But nothing that compounds.
Contrast that with organizations that design for learning.
They make ownership explicit. They create lightweight ways to test ideas before they become expensive. They shorten the distance between action and feedback. They remove the friction that turns curiosity into risk.
The shift isn’t dramatic on the surface. It’s structural underneath.
And it changes who gets to participate.
Because when innovation depends on charisma or hierarchy, only a few voices carry weight. But when it’s built into the system, more people step forward. Different perspectives surface. Creativity becomes less about permission and more about contribution.
That’s where innovation starts to feel less like pressure and more like possibility.
For me, the most meaningful shift has been letting go of the idea that innovation needs to be extraordinary.
It doesn’t.
It needs to be supported.
It needs to be safe enough to try, fast enough to learn, and clear enough to act on.
The organizations that understand this don’t wait for the next spark. They build the conditions where sparks can survive.
And over time, that’s what turns moments into momentum.
Connect With Ken
Comments