Journal — Essay 04
2026
There's a specific version of this that shows up around year seven or eight, sometimes earlier, sometimes later. The company is working. Revenue is consistent or growing. The team is capable. You've built what you set out to build, or close enough to it that the gap is minor. By every external measure, you're succeeding.
And you're bored.
Not burned out. Not tired. Not in need of a vacation. The word most founders use, quietly, is bored. Which is embarrassing, because bored sounds ungrateful. It sounds like a problem rich people have. It sounds like something you're not allowed to say when the thing you built is still standing and people still depend on it.
But there it is.
The standard explanation is that the early stage is exciting and the later stage is operational, and most founders are wired for the former. Some truth there. But it doesn't explain why the boredom lands the way it does — not as restlessness exactly, but as a kind of flatness. Like the signal got turned off.
Here's a more useful way to think about it.
In the early years, the company is generating a continuous stream of genuine uncertainty. Will this work? Can we make payroll? Will this customer renew? Will this hire work out? That uncertainty produces engagement, not because uncertainty is fun, but because your judgment is constantly being tested and refined against real stakes. Every week contains multiple moments where you don't know the answer and have to figure it out.
By year seven or eight, most of that uncertainty has been resolved. You know the business. You know the patterns. You know which problems are actually problems and which ones resolve on their own. The stakes are real but the questions are familiar. And somewhere in there, the signal that was keeping you sharp and engaged stopped arriving at the same frequency.
What founders call boredom is often the experience of running out of new problems to solve.
The instinct is to find a new project. Add a product line. Make an acquisition. Start something on the side. The boredom reads like a resource allocation problem — you have capacity left over, and something needs to absorb it.
Sometimes that's right. Some founders genuinely need more complexity, more stakes, more surface area. They're built for scale and they've been operating below their threshold.
But a lot of the time, the new project doesn't fix it. It produces a few months of engagement and then flattens out again. The pattern repeats. The founder starts another project. Or they start to wonder if something is wrong with them.
What's worth looking at in those cases is what exactly the original company was producing that the boredom signals the absence of. Because it probably wasn't just problem-solving. It was also a daily, concrete answer to a question about who you are and whether what you're doing matters. The company was providing proof. Revenue, headcount, growth, recognition — these are all forms of evidence. Evidence that you're competent, that you're building something real, that your judgment is sound.
When the company stabilizes, the evidence machine stabilizes with it. Consistent performance stops being proof of anything, because you're no longer earning it against uncertainty. It's just there.
The boredom might not be about novelty. It might be about the evidence having stopped arriving.
This matters because the two problems have different responses.
If you're genuinely under-challenged, a new project probably helps. More complexity, more stakes, more surface area for your skills to work against. That's a reasonable diagnosis and a reasonable solution.
If what's missing is the sense that what you're doing matters — the evidence of your own worth arriving on a daily basis through the work — a new project doesn't fix it. It delays it. You'll be engaged for six months and then you'll be back here, wondering why the thing you started isn't doing it for you either.
The second version is more common than founders tend to admit, because admitting it requires acknowledging that the work was doing something for you that had nothing to do with the work. That the motivation wasn't purely about building something good. That some part of what drove you was the daily answer to a question you didn't fully recognize you were asking.
That's not a character flaw. It's how the thing works. The problem is treating a new project as the answer when the question is actually about something else.
The boredom, in that case, is worth sitting with before reaching for a solution. Not because sitting with it is comfortable, but because what it surfaces tends to be more clarifying than anything the next project will produce.
Most founders who do this work — who actually look at what the company was providing that the boredom signals the absence of — describe the same experience: disorienting at first, then useful. Not because they find an answer, but because they find the actual question.
Which is different from the one they started with.