Succession Handover

He agreed to hand over his role. Weeks in, the handover is still going. He answers questions, attends meetings, and stays close. The successor has the title. He still has the job.

What Happens

• He stays “available for questions.” This replaces written documentation.
• The successor gets tasks. Decisions still run through him.
• Critical context lives in his head: why supplier X, why the workaround in system Y, why the deadline always moves to Thursday.
• He joins calls to “support the transition.” He ends up running them.
• He waits nearby during a client call. The successor hesitates. He steps in. The client thanks him.
• He says he wants the handover to succeed. He also volunteers his view on every decision.

Why It Happens

Handing over a role means handing over relevance. For someone whose identity is tied to this work, that is a real loss. Legacy Reflex is the pull to stay connected to what he built. Slowing the handover keeps that connection alive.

He also believes the successor is not yet ready. This is The Expert at work. He sees every gap. He fills each one. The successor learns to wait for him rather than figure it out alone.

Handing over also means becoming replaceable. Authority Preservation is the drive to stay the person others need. Giving the successor tasks feels safe. Giving the successor the authority to decide without him does not.

Some of what he knows was never written down. He is the only person who knows why things work the way they do. This is Knowledge Hoarding in its most passive form. He does not withhold information on purpose. He just answers questions as they arrive instead of documenting the answers.

The Need for Relevance runs underneath all of this. If the handover completes, his daily purpose changes. Staying in the handover keeps him needed. “Ask me anytime” is not generosity. It is a way of staying in the room.

What You Can Do

Set a hard end date and say what happens after it. The date must be specific. “When he’s ready” is not a date. Set a calendar date, and name the next role: a formal advisory arrangement, a new project, or an exit. Without this, “ongoing transition” becomes permanent. You can say: “Your last day in this role is [date]. After that, the successor owns it.”

Give him a job inside the handover. Fade-out does not work. A defined role does. Assign him as the official documenter. His task is to write down everything he knows: supplier contacts, system workarounds, the reason behind each non-obvious decision. This gives him something concrete to do. It does not involve running meetings he no longer owns.

Transfer authority, not just tasks. Track decisions at each review. Ask: what did the successor decide this week without him? If the answer is very few, the handover is not moving. Name this directly and ask what is blocking it.

Quick Tip

Ask the successor to keep a running log of questions they cannot answer without him. Review it weekly. The list should shrink. If it does not, the knowledge transfer is stalled and you need to find out why.

Replace open availability with fixed sessions. Two hours per week. The successor brings questions. He answers them. Outside those sessions, questions go to the documentation first. This ends “ask me anytime” without removing him too fast.

Name what you see when the dynamic stalls. Say it plainly: “The goal is a successor who does not need you. That is what success looks like here.” He will need to hear this more than once. Say it without apology.

If you are the successor, say this directly. You do not need permission to take the role. Tell him: “I appreciate that you are available. I need to make this decision myself. I will come to you if I find something I cannot work out.” Then do not circle back unless you genuinely cannot work it out.

See also: Documenting Institutional Knowledge