There’s a moment where I know an “innovative” project isn’t going to make it.
The work is thoughtful. Ambitious. Sometimes even a little uncomfortable—in a good way. It pushes on how things currently work. It asks users (and the system) to do something different. It feels like innovation.
And then someone asks:
“So… when can we deliver this?”
Not “what would need to change for this to work?” Not “how big of a shift is this?” Not even “are we ready for something like this?”
Just: how fast can we ship it?
I’ve been in that moment more times than I can count.
Projects framed as blue-sky thinking. Future-state vision. “Let’s rethink this from the ground up.” There’s language about transformation. Industry change. Big bets. And for a little while, it feels real.
But that moment—the delivery question—is usually where I know what’s coming next.
Because when something actually changes how an experience works, it almost always requires more than just interface changes. It touches how data is structured, how systems communicate, who owns the work, what the business is willing to support.
You don’t have to name it formally to feel it. You just know: this isn’t a surface-level change.
But that’s not the conversation we have.
Instead, the work gets translated—quickly—into something that fits inside the boxes we already have. What can we ship this year? What can we do without changing the backend? What’s the smallest version of this that’s still “something”?
The problem isn’t the questions.
It’s what they assume is fixed.
That’s the uncomfortable part.
Because at some point, the vision gets broken down into an MVP. Then broken down again. Until what’s left is technically related to the original idea, but no longer asks anyone—user, system, or organization—to do anything differently.
It’s safer. More feasible. Easier to deliver.
It also doesn’t change anything.
Most of what we call innovation never had a chance.
And that’s the part that took me a while to understand.
This isn’t a failure of execution. It’s not bad design. It’s not even necessarily misalignment in the way we usually mean it.
It’s something quieter than that.
I’m not sure we ever actually chose to do innovation.
Or at least—not in the way it would require.
We said we wanted it.
We asked for big thinking.
We used the language.
But at the point where it would require real commitment—when it would mean changing how things actually work—we made a different decision.
Usually a reasonable one.
Just…a different one.
I used to think the problem was that innovation “didn’t survive” delivery. That good ideas somehow got lost along the way.
Now I’m not so sure.
Because looking back, a lot of those ideas didn’t fail later. They were never really positioned to succeed in the first place.
Not because the idea wasn’t good. Because the conditions never were. Not with the timelines. Not with the level of change they implied.
There’s a version of this where the takeaway is: “organizations should commit more to innovation.” But I don’t think that’s quite right either.
Because sometimes, choosing not to innovate is the right call. In mature products. In trust-heavy systems. In environments where stability matters.
Improvement, refinement, and craft aren’t lesser work. They’re often the responsible choice.
The problem isn’t that we don’t innovate enough.
It’s that we’re not always honest about what we’re choosing.
We call something innovation, even when we’re planning to deliver it under constraints that can’t support it. We create visions without aligning on what it would take to make them real. We move forward as if the work still carries the same intent, even after it’s been reshaped into something else.
Over time, that pattern starts to feel familiar.
You see the vision. You feel the potential. And then you hear the question:
“So when can we deliver this?”
And you already know.
I don’t have a clean answer for how to fix it. But I do think there’s something worth naming here.
Innovation isn’t what you call it. It’s what you commit to.
Change. Risk. Time.
What actually has to give for something new to stick. Sometimes we choose that. A lot of the time, we don’t.
And maybe the work—at least to start—is just being a little more honest about the difference.