A handover is not a date
One day the founder decides that a professional manager will run the company. The reasons are usually good ones — growth has outrun what one person can hold in a day, partners want a governed structure, or the founder no longer wants to spend every morning on the same work. A name is found, a date is set, an announcement is made. From that date the handover is assumed to be complete.
The assumption is almost always early. The morning after the announcement the org chart has changed; the company's reflexes have not. People still knock on the same door, call the same number, wait for the same approval. This is not loyalty. It is a behaviour that was correct for years being made wrong by an announcement, and nobody knows exactly when it changed.
Not a day but an interval
So a handover is an interval rather than a day. At the start of it the founder has formally stepped back; at the end of it the founder has actually stepped back; and in most companies the distance between those two points is longer than a year. The hard part of a handover is not the new manager learning the business. It is the company relearning who it looks at.
What the founder goes through in that interval rarely gets named. From outside, a burden has been put down. From inside, an identity has been suspended. Being the founder of the company and running the company were two halves of one sentence for years, and they are coming apart for the first time.
What changes hands is not authority
Handover plans are almost always written in terms of authority: which decisions sit with whom, which limits, where the signature lives. That work is necessary and it is the easy part. An authority matrix is written in an afternoon and takes effect the next day.
The hard part is invisible in the matrix. What the founder is actually handing over is the habit of being the person who says the last word when something is stuck. That habit does not live in the founder; it lives in the company, embedded in how dozens of people work each day. No clause removes it, because it is not a written rule but a learned shortcut.
- Authority sits in a document and changes in a day.
Three things move at different speeds
- Knowledge sits in the founder's head and transfers over months; much of it never transfers at all, because the founder does not know it is knowledge.
- Standing sits in what the company does, and it changes only when it is tested: someone objects to the new manager's decision, goes to the founder, and what the founder does in that moment settles where standing actually is.
A handover happens not when authority is delegated but when the first objection reaches the founder and the founder sends it back. That moment is usually not in the plan, arrives unprepared for, and is the real beginning.
It is the most expensive form of the discipline in every yes is a no. The no the founder gives here is not to a piece of work but to a reflex, and reflexes change far more slowly than decisions do.
A handover happens when the first objection reaches the founder and the founder sends it back.
Where the room looks
The plainest way to see where a handover has got to is to watch people's eyes rather than the org chart. When a difficult subject opens in a meeting, who does the room turn to. The answer tells the truth regardless of what the matrix says.
The direction the room turns
That turn is gratifying, which is exactly what makes it dangerous. Having been needed for years makes not being needed feel like a loss. What founders struggle with most in a handover is not letting go of authority but getting used to being unnecessary, and when that sentence is not said aloud it is replaced by more acceptable reasons: not ready yet, the client asked for me, this decision is critical.
There is a symmetric difficulty on the manager's side. A manager whose founder is still in the building can trim decisions in advance against the founder's likely reaction. Nobody wants this and nobody says it, and the result is that the company's bravest decisions are never taken.
Together the two produce a quiet equilibrium: the founder formally does not interfere, the manager is not in practice fully in charge, and the company follows a cautious line between them. The equilibrium lasts because it is comfortable. A crisis usually breaks it, and what the founder does in that crisis matters more than two years of handover planning.
The moments it is taken back
In every handover there are a few moments where the founder gets the chance to take the work back. They are not dramatic: a customer complaint, a seat emptied by a resignation, a quarter that lands worse than forecast. The founder steps in, solves it, and nobody objects, because the solution worked.
The price of well-meant intervention
The problem is that the intervention works. Because it works it is repeated; because it is repeated the company comes to expect it; and because it is expected the new manager takes less initiative in the next difficult situation. Every successful intervention by a founder moves the handover one step backwards, and does it without leaving visible damage.
So the most important line in a handover plan is not what the founder will do but what the founder will not do. Written abstractly it does nothing. "I will stay out of operations" is an intention. "Operational matters that reach me go to the manager and I do not ask how they ended" is a behaviour; it can be tested, and when it is tested it can be seen.
There is a real exception: situations that threaten the company's existence. But founders tend to hold that exception widely, because for a long time everything genuinely was critical. When its boundary is not set in writing at the start, in practice the boundary becomes whatever patience the founder has that day.
The observation in direction is what a company refuses applies here without translation: a company's real direction is shown not by the document but by what it does when it is stuck. A handover is the same.
From the field
What the successful handovers have in common is not a better plan. It is a question the founder asked early: what will take my place in this company. The question is about the founder's own week rather than about the company.
The vacated place needs a name
When a responsibility that filled six days a week is put down, what remains is an undescribed emptiness, and undescribed emptiness fills with the nearest habit — which is usually the company. The founders who finish a handover fastest are the ones who knew what would replace the role before they left it. Another business, an investing role, a board seat, sometimes something long postponed.
A second observation: most founders whose handover went badly had built it not too fast but too vaguely. A clear handover completed in six months costs both the company and the founder less than an ambiguous one stretched over three years. Vagueness looks considerate, and the company pays for it.
How we work follows that order: first the name of what the founder is putting down, then the calendar. Reversed, it produces a date rather than a handover.
The observation the field keeps returning is this: a company has been handed over when its founder no longer needs it.