Journal — Essay 03

What did I get wrong about stepping back as CEO?

2026

Most founders who are serious about stepping back have a version of the transition already scripted in their heads. The handover goes cleanly. The successor settles in. You stay involved in the ways that matter and disappear from the ways that don't. Within a few months, the calendar opens up, and you start working on whatever comes next with some combination of more freedom and more focus than you've had in years.

That's a reasonable thing to expect, because some version of it describes the external facts accurately. The handover does happen. The calendar does open. The business does continue without you.

What the script doesn't account for is what the role was doing for you that you didn't realize until it stopped.

The CEO role, especially in a company you built, provides an enormous amount of invisible structure. Your calendar isn't just full. It's full in ways that feel purposeful. Every meeting is connected to a problem you care about. Every decision carries real stakes. The work generates a continuous, low-level answer to the question of whether what you're doing matters. You don't notice this answer being generated because you're never in a position where the question goes unanswered.

When you step back, the question doesn't transfer to your successor. The machinery that was answering it shuts off.

The first few months are usually fine. There's genuine relief in them. Decisions you used to lose sleep over are someone else's problem now. Travel you used to dread is optional. The thousand things that needed your attention no longer need it. You feel lighter than you have in years, and you probably say that out loud, because it's true.

Somewhere around month four or five, depending on the person, something shifts.

Most founders I've talked to don't have a breakdown or a dramatic reckoning in this period. What they describe is subtler. A sense that the things they thought would fill the space haven't quite filled it. Board seats are interesting but thin. Advisory relationships feel like a fraction of what operating felt like. The new project, whatever it is, doesn't have the same pull yet.

There's a version of this I watched happen to myself. I had genuinely good things in my life during that period. Time with my family. Time to think. The ability to be somewhere fully instead of half-present. By every reasonable measure, things were better. And yet there was this persistent low-grade feeling that something was slightly off, that some dial that used to be turned up wasn't anymore. I spent quite a while treating it as a productivity problem. A structure problem. An accountability problem. I tried different approaches to filling the calendar. I signed up for things. I started things.

None of it resolved what I was actually dealing with, which took longer to name.

The CEO role, for most founders who've done it for a long time, becomes more than a job title. It becomes an answer. An answer to who you are, to whether you're competent, to whether what you're doing is worth doing. The company provides the evidence daily. Revenue moves or it doesn't. The team grows or it doesn't. Problems get solved or they don't. It's concrete, it's legible, and it's yours.

When you step back, you give up the role. What most founders don't realize is that you also give up the evidence.

The questions the role was answering don't get forwarded to your successor. They stay with you. But now you're answering them with less feedback, fewer stakes, and a much quieter environment than you've operated in for years. That's a significant adjustment. Actually, "adjustment" is probably too mild a word. It's closer to navigating without instruments you've been relying on for a decade, in conditions where the old landmarks are gone and the new ones aren't visible yet.

What I got wrong was assuming I was prepared for this because I'd thought about it in advance. I had thought about it. I'd planned the transition carefully, set up governance properly, chosen a capable successor. The operational part of stepping back was reasonably smooth. The identity part had nothing to do with operational preparation.

This is the part of stepping back that almost nobody talks about before it happens, because the framing around founder transitions tends to focus on the business. The structure question. The succession question. The board question. Those are real and worth getting right. They're also the easier part.

What most founders are less equipped for is the question that opens up once the operational work is done: who you are when you're not the person building the thing.

That question doesn't have a clean answer, and it doesn't resolve on a schedule. Some founders find it more disorienting than anything they dealt with while running the company. Some find it clarifying in ways they didn't expect. Most find it to be both, at different points, without much warning about which is coming.

The first year after stepping back is mostly an encounter with that question.