You Trained Your New Hire for a Job Nobody Has

Onboarding teaches the calm version of a role. The person arrives into the actual week, notices the gap around month two, and reads it as their own failure rather than as the condition everyone around them already adjusted to.

Think about the last person you brought into your unit. Their first two weeks were probably well organized. They read the position description, sat through the systems training, met the people they would work with, learned the approval routes and the reporting lines, and left that stretch with a clear picture of what the job involves.

Now think about what that person was actually doing in week nine. Somebody had gone out on leave, a deadline had moved, two of the approval routes turned out to run through the same overloaded person, and the work in front of them looked almost nothing like the version they were trained on. They did not tell you that. They kept adjusting, quietly, and somewhere in there they started to suspect they were not as good at this as they had been at their last job.

They were trained for a role that exists in the position description and in no particular week. The gap between that role and the one they hold is not a training defect you can fix by adding modules. It is the ordinary distance between how work is described and how it actually runs, and the only real question is whether a new person has to discover it alone.

The part of the job that never gets written down

Every unit runs on two bodies of knowledge. The first is the documented one: procedures, systems, deadlines, who signs what. That is the part onboarding covers well, because it is written down already and someone can hand it over in an afternoon.

The second body of knowledge is what your unit does when the first one does not hold. Which deadlines are real and which ones move every year. Which approval you can start work before receiving and which one you genuinely cannot. Who to call when the official route is blocked, and what it costs you the third time you call them. What counts as an emergency here as opposed to what everyone calls an emergency.

Nobody hands that over, and the reason is not carelessness. The people who hold it stopped experiencing it as information years ago. Ask an experienced member of your team how they knew to route something around a particular office and they will struggle to answer, because to them it is not a decision. It is just how the work goes. Knowledge that has become that automatic is nearly impossible to notice you have, which means the people best positioned to teach it are the least likely to think of it.

So the new person assembles it themselves, from fragments, over about six months, at whatever price the mistakes happen to carry.

What you will see instead of the real problem

A confident start followed by a quiet month. The first weeks look strong because the documented job is the one being performed. Somewhere between weeks six and twelve the undocumented job starts to dominate, and the person's output gets slower and more hedged. From where you sit, that reads as a plateau, or as someone who interviewed better than they perform. What it usually is is someone doing two jobs at once, the work itself and the reconstruction of how the work actually happens here.

Norms transmitted by whoever happened to be nearby. A new person will get the second body of knowledge from someone. If you have not decided who, it will come from the colleague with the most availability, which in a busy unit often means the person with the least to do or the most to complain about. Six months later you notice your new hire has inherited a set of workarounds and a view of the organization that you would not have chosen to teach, and there was never a moment when anyone taught it deliberately.

A good person leaving at eight months for a reason that is not the reason. The exit conversation will produce something clean and unarguable: an opportunity came up, the commute, a partner's job. Underneath it is often a person who spent most of a year privately concluding they were failing at something everyone else found manageable, and who never learned that the thing they were failing at is not written down anywhere and took their colleagues three years to work out.

Three ways to close the gap

Write down what the unit does when the plan does not hold. Not a policy document. Two pages, in plain language, covering the exceptions: which deadlines actually move, which approvals can be started in parallel, who to go to when the ordinary route is blocked, and what your unit treats as a real emergency. The fastest way to produce it is to ask two experienced people what they wish they had known in their first six months and to write down their answers rather than summarizing them.

Tell the new person the gap exists, and tell them when it will show up. Say plainly in the first week that the job as described and the job as lived are different, that the difference tends to become obvious around month two, and that noticing it is a sign they are paying attention rather than a sign they are behind. That one sentence does more than any document, because it removes the private conclusion the person would otherwise reach on their own.

Give the second body of knowledge an owner, and ask a specific question at week six. Name one experienced person whose job for six months is the unwritten half, and make it an actual expectation rather than a favor. Then, at around week six, ask the new person a question narrow enough to get a real answer. Not how things are going. Ask what has surprised them, or what they have already had to work around. The answers will tell you what your onboarding leaves out, and they will only be honest while the person still remembers being new.

The part of this that is yours

You learned your own unit the same way, by absorption, over a period you probably remember as harder than it needed to be. What makes this difficult to see now is that you succeeded at it. The knowledge you fought to assemble has settled into the background where you cannot easily point at it, and the fact that you got through it without help makes it feel like something a capable person simply picks up.

Your team has adjusted to conditions you have stopped registering as conditions. Every one of those adjustments is something a new person has to reconstruct from nothing, without knowing there is anything to reconstruct. You cannot list what you no longer notice. You can ask the person who is still new enough to see it.

Three questions

Take your most recent hire. What have they already had to work around that nobody told them about, and would you know if you had not asked?

If a capable person joined next month and the two people who hold most of your unit's practical knowledge were unavailable, how long would it take that person to become useful, and who would carry the difference?

Think of the last good hire who left inside a year. What reason did they give, and what would you have had to know in month two for that reason to have been avoidable?