What Founders Misunderstand About Persistence and Stubbornness
Persistence is often praised as the ultimate founder virtue, but without the ability to be corrected by reality, it becomes stubbornness. Learn how to distinguish between the two.
The core misunderstanding about persistence is the belief that it requires a linear, unwavering commitment to an initial idea. In reality, persistence is a commitment to the problem you are solving, while stubbornness is an attachment to the specific solution you first imagined. One keeps you in the game; the other ensures you eventually run out of resources while building something nobody wants.
In the early days of Postly, I had to confront this tension directly. It is easy to romanticize the 'visionary' who ignores the critics, but in the middle of a long build, ignoring the market isn't visionary—it is expensive. True persistence is the willingness to stay in the uncomfortable space of the unknown until reality reveals the path forward. It requires what I call being 'teachable fast.'
The Answer: Mission vs. Method
Persistence is the drive to reach a destination. Stubbornness is the refusal to change the map even when you realize the terrain has shifted. For a founder, the destination is a sustainable, valuable product that solves a real pain point. The map is your current feature set, your pricing model, and your go-to-market strategy.
As I documented in The Long Build, ideas are the least reliable part of the startup process because almost every early idea is partly wrong, partly naive, and partly incomplete. If you are persistent, you use that realization to iterate. If you are stubborn, you interpret the market's lack of response as a failure of the customers' imagination rather than a failure of your product's current form.
The Postly Lesson: Monetization as Persistence
Many founders mistake avoiding monetization for 'purity' or 'focusing on the user.' In the Postly journey, I realized that seeking real economic validation early was actually an act of persistence. It was the persistent pursuit of the truth.
Monetization reveals seriousness. It prioritizes tradeoffs and forces you to confront whether your product is merely interesting or genuinely valuable. Stubbornness would have been sticking to a free model because I was afraid that charging would 'cheapen' the mission. Persistence was the willingness to evolve the monetization method to find where the real value lived. This shift is part of the broader tension between ambition and patience that every builder must navigate.
A Framework for Discernment
To distinguish between these two states, you must look at how you handle feedback and complexity. Persistence welcomes the 'arrival of complexity' as evidence that the company has become real enough to create serious consequences. Stubbornness views complexity as an annoyance that gets in the way of the 'pure' original vision.
| Signal | Persistence | Stubbornness |
|---|---|---|
| Customer Feedback | Looking for the pain beneath the prescription. | Ignoring feedback that contradicts the original vision. |
| Monetization | Testing if value is real enough to pay for. | Delaying charging to avoid 'polluting' the idea. |
| Product Complexity | Accepting systems as evidence of growth. | Mistaking complexity for evidence of personal failure. |
| Pivoting | Changing the 'how' to save the 'why.' | Refusing to change the 'how' until the 'why' dies. |
Failure Modes: The Cost of Being Right
The most dangerous failure mode for a founder is 'Heroic Hindsight'—the belief that because you were right about one thing, you must be right about everything. This leads to a form of stubbornness where you stop being a student of your own market.
Validation is not applause. It is evidence that someone values the outcome enough to give time, trust, or money. When a founder becomes more addicted to the applause of their peers than the evidence of their users, they have crossed from persistence into stubbornness. They are no longer building a product; they are defending an ego. This often happens in the 'valley' between validation and scale, a period I explore further in my essays on how ambition and patience change over time.
The Teachable Founder
GrowthDiary is built on the principle that startup life eventually stops rewarding emotional reactiveness. In the beginning, urgency can look like energy. But as the product matures, you must become less eager to please everyone and more willing to protect the long-term identity of the product.
This means being willing to say 'no' to features that don't fit, even if you’ve spent months thinking about them. It means being willing to simplify when complexity starts pretending to be sophistication. This isn't giving up; it is the highest form of persistence—the persistence of clarity.
Field Notes for the Long Build
- Separate pain from prescription: Listen to where the customer hurts, but don't always build exactly what they ask for. Your job is to find the most coherent solution to that pain.
- Seek economic validation early: If people won't pay for it, you are either solving the wrong problem or solving it for the wrong people. Persistence means finding the right combination.
- Embrace the sequence: You cannot skip from conviction to growth. You must pass through exposure, monetization, and complexity. Stubbornness tries to jump the queue; persistence walks the path.
- Protect your judgment: Learn from the market without surrendering your judgment to it. The market tells you where the holes are; you decide how to bridge them.
If you are currently feeling the weight of a long build, ask yourself: Am I holding onto this feature because it is working, or because I am afraid of being wrong? The answer to that question determines whether you are building a legacy or just being difficult. For more on surviving the middle of the journey, you can continue with The Long Build and GrowthDiary essays.
Follow via RSS: latest articles · full article archive