Much of the common advice on founder mental health is wrong.
This article looks at founder mental health: what tends to work, what usually fails, and how to start.
What I've Learned From 98 Companies
A few patterns in founder mental health come up again and again.
The founders who handle founder mental health well understand that timing is everything in this game.
The Counterintuitive Truth
In founder mental health, the best practitioners often do less, not more.
Trying to do everything at once is one of the most common ways to fail: even a team with strong technology and talent can spread itself too thin.
The lesson: your team matters more than your technology. It sounds simple. It's incredibly hard to execute.
Real Talk: What Actually Matters
Here is what actually matters in founder mental health.
First, execution speed beats perfection. Every time. Companies rarely fail because they moved too fast on founder mental health. Many fail because they moved too slowly.
Second, measure everything. If you can't measure it, you can't improve it. Set up tracking from day one, even if it's basic.
Third, talk to your users. It sounds obvious, but many founders make decisions about founder mental health in a vacuum. Get out of the building. Talk to real people.
This connects to broader themes around founder depression, burnout prevention, work-life balance that I've been thinking about a lot lately.
Wrapping Up
I've shared a lot here, and I know it can feel overwhelming. But you don't need to get founder mental health right on day one. You just need to get started and keep improving.
Founders who do well at founder mental health tend to share one trait: they're relentlessly practical. They don't chase perfection. They chase progress.
That's the mindset I'd encourage you to adopt. Start where you are. Use what you have. Do what you can. And keep pushing forward.
As always, I'm rooting for you.
Frequently Asked Questions
Q:How can I apply this thinking to my own situation?
Start by identifying the core principle behind the opinion, not the specific example. Then ask yourself: does this principle apply to my context? If yes, test it in a small, low-risk way before going all in.
Q:What's the most common pushback you get on this?
People often push back by citing exceptions or edge cases. And they're usually right that exceptions exist. But building a strategy around exceptions rather than patterns is a losing game for most founders.
Q:What experience informs this perspective?
This perspective comes from over a decade of building companies in Silicon Valley, two successful exits (RemoteTeam to Gusto, MovieLaLa to Gfycat), and investing in 234 startups including Anthropic, OpenAI, and Scale AI. I write about what I've lived.