Name your successor before the bus does
If you vanished for six months, who runs the company? Most founders can't answer, and the cost is daily, not disaster.
Marcus had run his company for over seven years when we sat down for coffee. I asked him a plain question: if he vanished for 30 days, who signs off on our biggest calls? He named his head of operations, with caveats. I asked about six months. He thought longer, then said he didn't know. I asked about permanently. He changed the subject.
The avoidance is common, and it is not strategic. Most founders can't answer this even privately, because answering forces two admissions. First, the company can run without them. Second, one specific person, not them, would hold the decisions that have defined the company since they started it. Both are uncomfortable, and the discomfort is why the question stays buried.
The real cost is not the disaster. A founder getting hit by a bus is rare. The everyday cost is the bottleneck. A founder who has never named a successor, even informally, runs a company where no second has the standing to make founder-level calls. Every one of those decisions routes back through one desk. The founder becomes the single point of failure for a whole class of choices the company should already be able to make on its own. That is a delegation failure wearing a succession mask.
Naming a successor fixes decision quality now, not only in an emergency. The named person knows the role exists. They ask sharper questions, build relationships across the leadership team that match the authority they will inherit, and start absorbing calls that used to wait for the founder. The relationship shifts from senior report to partner in training.
The conversation that starts this is small. The founder tells the person, privately and without ceremony, that they are the successor. The founder tells the board, so the contingency is on record. The founder tells the head of HR, so the systems can support the role as it grows. No public announcement required. The answer needs to live in three heads besides the founder's.
Most founders stall here because naming a successor feels like betting against themselves. The bet runs the other way. It bets on the company's ability to survive a transition, on the team's ability to absorb one, and on the founder's ability to build a partner instead of staying the only adult in the room. Founders who have already worked through their own fear of being replaceable make this call faster.
The harder case is when no successor exists. The current team has nobody who could plausibly run the company. Then the succession plan is to hire one. Most searches like that run 6 to 12 months, and the ramp runs a year beyond that. Start it before the emergency, not during.
Answer the question, even if only to yourself. Name the person, even if only informally. The bus is unlikely. The bottleneck bills you every day.