Unpopular opinion:
Working harder is the default founders reach for under pressure.
But it rarely fixes anything.
I have watched this happen on every team I have been part of, including my own.
Something slows.
A client is unhappy.
A launch gets missed.
A number comes in off.
Whatever it may be...
The first move is almost always the same:
Work more hours, answer faster, do more yourself.
Of course, that instinct comes from a good place.
I've done it more times than I can count, and probably will again 🥲
And that's because, like me, founders care.
So they push harder instead of stepping back.
But here is what that response usually covers up:
❌ A decision that was never made, just delayed
❌ A process nobody agreed on, so everyone improvises
❌ An owner that was never assigned, so the founder becomes the owner by default
More hours can carry a team through one bad week.
But they won't fix what caused it.
I learned this running Fluency.
There were stretches where I worked longer instead of asking why the same problem kept coming back.
The problem never left.
I was just tired enough to stop noticing it.
That's the part that costs you most, not the hours.
Here's what changes it instead:
✅ Ask why this keeps happening before you ask how to move faster
✅ Protect the hours you already have instead of adding more
✅ Name the decision that's stuck before you work around it
✅ Assign one owner, even if that's uncomfortable
Working hard was never the issue for me.
Using hours to avoid a harder conversation was.
I don't think I'm the only founder who does this.
Chances are you've been in that same stretch.
But all you need to do is pause before you reach for more hours,
and ask what's stuck instead.
What's your default move when something breaks under pressure?
♻️ Repost for the founder about to work on their weekend.
And follow me, Jacob Rokeach, for more on growth, judgment, and building without burning out.
Founder Burnout: Why Working Harder Isn't the Solution
Previous
Previous
7 storytelling techniques every marketer should know
Next
Next
