The Effort Myth: When Persistence Becomes Stubbornness
Entrepreneurship rewards effort, but it doesn’t guarantee a return on it. That’s a hard truth for smart, capable founders and entrepreneurs because effort is one of the few things you can fully control when everything else feels uncertain. In the early days, that control can be useful. You learn faster by doing. You get momentum. You build the muscle of follow-through.
The problem is that effort is also the easiest place for the brain to hide. When uncertainty spikes, “more” feels responsible. More outreach. More features. More meetings. More late nights. It looks like commitment. It can even earn praise. But if the effort isn’t tied to evidence, it quietly turns into a substitute for learning. That’s the “effort myth”: the belief that persistence, by itself, is the answer.
At CEED, we see this pattern across stages. Pre-start founders often overbuild because building feels safer than testing. Growth SMEs often overwork the wrong constraint because the business is already moving and it’s tempting to push harder instead of redesigning the system. Different context, same trap: effort becomes the way you avoid the uncomfortable question—what if the assumption is wrong?
When persistence is productive—and when it’s stubborn
The thing that separates persistence from stubbornness is what I refer to as “signal”. Signal means reliable information that should confirm or change a decision—it’s tied to real behaviour or outcomes (not opinions), it shows up repeatedly (a pattern, not a one-off), and it’s decision-relevant (it points to what to change next). A simple rule: signal is evidence you’d trust enough to bet your next two weeks on.
Persistence becomes valuable when it stays connected to learning. You keep going because each cycle produces signal, and the signal helps you adjust. You can explain what you’re trying to prove, what you’re measuring, and what would change your plan. In that case, persistence is not just endurance; it’s disciplined iteration.
Stubborn persistence looks similar from the outside, but it’s fundamentally different on the inside. You keep going because stopping feels like failure, because the story has become personal, or because changing course threatens your identity as a “serious” founder. The actions create motion, but they don’t create new information. A simple test is whether you
can name what would change your mind. If you can’t, you’re not persisting—you’re defending.
Two versions of the effort myth: pre-start and growth
For pre-start founders, the effort myth usually shows up as “work that avoids the market.” You might spend weeks polishing a brand, building a website, perfecting features, or writing a plan that never meets real customer friction.
he effort feels clean and controlled. Customer discovery feels messy and exposed. So the founder stays busy and tells themselves they’re being thorough.
For growth SMEs, the effort myth usually shows up as “work that avoids the constraint.” When revenue exists and delivery is real, the discomfort shifts. You might push sales harder when the offer is unclear, hire more people when the bottleneck is process, or keep taking custom work when pricing and scope control are the true margin killers. Everyone is working hard, but the business still feels heavy. That heaviness is often a signal that the system—not the team’s effort—is the limiting factor.
In both cases, the core error is the same: effort is responding to a symptom rather than solving a root cause. The founder presses the gas harder without confirming whether the car is pointed in the right direction.
The brain mechanics behind stubborn persistence
This isn’t about laziness or discipline. It’s about normal human cognition under uncertainty. Sunk cost makes past effort feel like a reason to continue, even when conditions have changed. Loss aversion makes changing course feel riskier than staying the same, even when the current path is quietly failing. Identity lock makes it emotionally expensive to say “I was wrong,” because the plan has become part of the founder’s self-image. Narrative certainty fills gaps with confident stories—especially when the data is thin.
These forces are powerful because they’re invisible in the moment. You don’t feel like you’re escalating commitment; you feel like you’re being resilient. That’s why we treat this as a mindset skill, not a productivity issue.
The antidote: attach effort to evidence
The goal isn’t to “try less.” The goal is to make effort earn its keep. Effort is an input; learning is the compounding asset. If your effort isn’t creating signal—customer signal, conversion signal, delivery signal, margin signal—you’re paying for comfort with time and energy.
A founder-friendly way to frame it is this: you’re allowed to be persistent, but you need a decision rule. You need to know what “working” looks like, what “not working” looks like,
and what you’ll do if the test fails. That’s not quitting. That’s professionalism under uncertainty.
A quick stage-specific lens you can use today
If you’re pre-start, ask yourself whether your effort is producing real customer evidence. Are you hearing the problem in the customer’s language? Are you getting commitments—time on calendar, referrals, pilots, pre-orders—anything that forces truth? If not, there’s a decent chance you’re building a story, not a business.
If you’re in growth mode, ask yourself whether your effort is relieving the true root cause that is constraining you success or are you just adding activity. Are you pushing throughput without fixing quality and rework? Are you selling more without tightening scope and pricing? Are you hiring to compensate for process debt? When the constraint is structural, effort alone becomes expensive.
CEED Mindset Gym: The 10-minute “Assumption to Test” sprint
Set a timer for 10 minutes. Grab a pen. Don’t overthink it.
In the first three minutes, write down the one area where you’re “trying harder” right now. Keep it specific: sales, content, product, hiring, delivery, fundraising, partnerships—whatever is taking the most energy.
In the next four minutes, complete these three sentences in full. First: “The result I want is ______.” Second: “The evidence I’m currently using is ______.” Third: “If this is the wrong path, I would know because ______.” That last line is your decision rule. If it’s hard to write, that’s your signal that effort has drifted away from evidence.
In the final three minutes, pre-commit one small action that creates signal within the next 7–10 days. Write it in calendar language: “On [day], at [time], I will [action] for [duration].” Then add one line beneath it: “I will call this a win if I see [measurable signal].” Keep it modest and real—something that forces learning, not something that simply creates more activity.
Let’s look an example,
A founder is building a scheduling app for independent physiotherapists. They’ve spent three weeks refining the UI and adding features because it feels productive and controllable, but they haven’t had many real conversations with physios.
Minute 1–3 (Where am I “trying harder”?)
“I’m trying harder on product build. I keep adding features and polishing screens.”
Minute 4–7 (Complete the three sentences)
- “The result I want is 10 physios willing to trial it within 30 days.”
- “The evidence I’m currently using is my own belief that the workflow is obvious, plus a few friends saying it ‘looks great’.”
- “If this is the wrong path, I would know because after 12 targeted conversations with physios, fewer than 3 agree to a 20-minute workflow walkthrough and a 2-week pilot at a defined price.”
Minute 8–10 (Pre-commit one action that creates signal)
“On Tuesday at 10:00am, I will call and email 15 local independent physio clinics for 45 minutes to book 5 discovery calls this week.”
“I will call this a win if I book 3+ discovery calls by end of day Wednesday, and at least 1 physiotherapist agrees to a pilot by next Friday.”
What changed: the founder didn’t “do less.” They redirected effort from building to evidence. The success condition isn’t “I worked hard”—it’s “I got signal that either confirms or challenges the assumption.”
If you do nothing else this week, do this: make your effort buy evidence. That’s how persistence stays productive, and how you avoid the quiet slide into stubbornness.
What’s next in the series
In the next post, “Feedback loops: turning critique into capability,” we’ll tackle a problem that quietly limits otherwise strong founders: not the lack of advice, but the lack of a system for using it. Customer comments, investor pushback, team friction, and mentor opinions can either sharpen your decision-making or scramble it—depending on how you process feedback under pressure. We’ll introduce a simple CEED-style feedback loop that separates signal from noise, reduces defensiveness, and turns critique into concrete experiments, changes in operating rhythm, and measurable capability. The goal isn’t to collect more input; it’s to build the habit of learning faster without losing conviction.