Why Most Innovators Quit One Year Too Early

Innovation isn’t a trait some teams have and others don’t. It’s a condition — and most owners only find out whether they have it when everything else has stopped working.

You have a prototype. It works — sort of. You’ve shown it to people you trust and got back the two responses that always arrive together: enthusiastic nodding from people who don’t fully understand it, and carefully-worded scepticism from people who do.

Your business partner is starting to ask the question you’ve been avoiding. The bank account looks like it did two years ago. The market has moved on to something else, and you’re still here — in the shed, on the whiteboard, in a spreadsheet at 11pm — trying to solve a problem most people decided wasn’t worth solving.

Here is the question that determines everything from this point: why are you still doing this?

If your answer is because I want to build a business — you’ll stop. If your answer is something else entirely — something that has almost nothing to do with money — you might be the kind of owner the research says actually succeeds.

This isn’t a motivation problem. It’s a purpose gap.

When an innovation team loses momentum, the standard diagnosis is execution failure: wrong strategy, wrong market, wrong timing. Sometimes that’s true. But in studying the teams that don’t fail — the ones that keep moving through the long, expensive, demoralising middle of a real breakthrough — a different pattern emerges.

The teams that endure are not more talented. They are not better funded. They do not have better market timing. What they have is a shared answer to a question most business frameworks never ask: what is this actually for?

Not what does it do. Not what is the market size. What is it for — in a way that matters beyond the P&L?

I call this the purpose gap. It’s the invisible distance between what your team is building and why any of you actually care about it. It’s not a soft, motivational concept. It’s a structural condition. When the purpose gap is wide, teams fragment under pressure. When it’s narrow — when everyone in the room shares a reason that isn’t reducible to revenue — teams develop what one founder I spoke with called stubborn persistence: the capacity to keep going long after the rational case for continuing has dissolved.

Why purpose is a survival mechanism, not a values exercise

Two patterns appeared with striking consistency in the businesses that survived their hardest periods.

The first was a shared positive purpose that extended beyond the product. The businesses that endured weren’t just building things. They were building things for something — for an industry they believed was broken, for a community they were part of, for a problem that affected people they cared about. This purpose wasn’t decorative. It was load-bearing. It carried the team through the periods when the commercial case was weak and the critics were loud.

The second was the capacity to absorb pressure without losing direction. Not the absence of pressure — the capacity to absorb it. The teams that displayed this had something outside themselves to orient to when internal doubt became overwhelming. Purpose, in these teams, wasn’t a statement on a wall. It was a navigation system.

The mechanism works like this. When a team encounters a serious obstacle — a product failure, a market rejection, a funding collapse — two things happen. First, individuals look inward, to their own reasons for continuing. Second, they look outward, to each other, for confirmation that the reason still holds. If both anchors hold, the team moves forward. If either fails, the energy that looked like momentum begins to quietly leak. The work continues. The conviction doesn’t. And in innovation work, conviction is the resource that matters most — because it’s the one you can’t buy.

What this looks like in practice

One story keeps surfacing as a near-perfect illustration of this dynamic.

A small team — a father and a son — spent a decade trying to solve a problem most people in their industry considered either unsolvable or not worth solving. The problem was not dramatic by the standards of the technology world. But it mattered to them in a way that was completely disproportionate to the commercial opportunity they could have demonstrated on a spreadsheet at the time.

In those ten years, they failed repeatedly. Prototypes that didn’t work. Approaches that seemed promising for months before revealing a fundamental flaw. The kind of slow, expensive, episodic failure that most investors would have walked away from in year three.

What kept them going was not a pivot strategy. It was not a new business model. It was the stubborn belief — held between the two of them, and eventually by a small community quietly following their work — that the thing they were building would matter to something beyond their own success.

When they finally launched, they raised over A$16 million in a matter of weeks. Not because the market suddenly wanted what they had built. Because a community that had watched them persist — that had seen the purpose hold even when everything else was uncertain — decided that this was something worth backing.

The product was extraordinary. But the persistence was what made the product possible.

The one thing you can do today

Write down — in one sentence — why your team is building what it’s building. Not what it does. Not the problem it solves. Why this. Why now. Why you.

Then share it with every person on your team, individually, and ask them to respond with their version of the same sentence.

If the answers are roughly the same, you have a purpose anchor. If they’re materially different, you’ve just found your most important work — not the product, but the conversation that needs to happen before the product can survive its hardest year.

This exercise takes twenty minutes. The absence of it has ended more innovation efforts than bad technology ever has.

Frequently asked questions