What should happen when an employee gets a new manager (and usually doesn't)

An internal transfer or reorg gets treated very differently from an external hire. When someone new joins the company, everyone accepts that onboarding takes real effort. When an existing employee simply moves to a new manager, the assumption is that almost none of that effort is needed. They already work here. They already know the systems. What's left to hand off?

Quite a lot, as it turns out. The parts that actually matter in a manager relationship, what's been promised, what's been struggled with, what's already been tried and didn't work, rarely live in any system that automatically follows the employee to their new manager. They live in the old manager's head, and reorgs don't come with a built-in mechanism for getting that context to transfer along with the reporting line.

Why this kind of knowledge loss is so easy to miss

The financial cost of this gap is measurable even if nobody's tracking it directly. Roughly 42 percent of organizational knowledge exists only in employees' heads, and the average employee spends around 200 hours a year simply searching for information that a departed or transferred colleague took with them. A large majority of knowledge transfer happens informally, through hallway conversations and shared meetings, rather than through any documented process at all.

Most organizations at least attempt a structured handoff when someone leaves the company entirely. Far fewer apply that same rigor to an internal move, even though the receiving manager is arguably in a worse position: they can't even ask the departing person's replacement questions, because there often isn't one. The knowledge just has to come from the previous manager, if anyone thinks to ask.

An external hire gets ninety days of structured onboarding. An internal transfer often gets a Slack message and a new reporting line, even though the new manager knows just as little about how to manage this specific person.

What actually needs to make the trip

Internal transfer guidance consistently points to a handful of things a receiving manager needs and rarely gets automatically: clarity on expectations, introductions to the new team, context on current work, and a plan for regular check-ins during the first stretch in the new role, treating the transition with the same onboarding rigor as an external hire rather than assuming the person will simply figure it out.

A better way to run the actual handoff

One well-documented approach to this problem is a short, structured three-way conversation involving the outgoing manager, the incoming manager, and the employee together. The meeting opens with the goals of the transition restated clearly, giving the employee a chance to clarify or even push back on anything being said, before the outgoing manager shares their context directly with the incoming one, in front of the employee rather than behind their back.

Doing this in front of the employee, rather than as a private conversation between the two managers, matters more than it might seem. It requires everyone in the room to be mindful of power dynamics, and it means the context being transferred is something the employee has actually heard and can correct if it doesn't match their own sense of things. A handoff conducted entirely behind closed doors leaves the employee wondering exactly what was said about them, with no way to know if it was accurate.

Why a written record beats a single handoff conversation

Even a well-run handoff conversation has a real limitation: it's a single moment, filtered through one person's memory of a relationship that might span years. A manager trying to summarize everything worth knowing about an employee in a thirty-minute conversation will inevitably compress, generalize, or simply forget details that would have mattered.

A running written record doesn't have that limitation. If notes have been kept consistently throughout the relationship, the receiving manager doesn't have to rely on the outgoing manager's summary at all, or at least not exclusively. They can read the actual history: the specific project that went well in March, the specific frustration raised in June, the specific commitment made in August. That's a fundamentally more complete transfer than any single conversation can achieve, no matter how well the conversation is run.

Why this matters especially for who gets to move

There's a cultural dimension here too. Sending managers are sometimes tempted to view an employee's transfer as a personal loss rather than a leadership success, which can quietly discourage transfers or make them messier than they need to be. A clean, well-documented handoff process removes some of that friction. When context transfers smoothly and completely, a transfer feels like exactly what it should be: evidence that someone was developed well enough to be ready for something new, not a scramble that leaves everyone, including the employee, feeling like something got lost along the way.