Rehiring the same knowledge twice

When a role is backfilled, the cost that gets budgeted is the salary and the recruitment fee. The cost that rarely gets budgeted, because it's invisible until it happens, is the months the new hire spends rediscovering things the previous person already knew — the same mistakes, the same false starts, the same slow accumulation of judgement, paid for a second time.

The hidden line item

Call it relearning cost, and it shows up predictably in any role with real judgement attached: which suppliers are reliable and which need chasing, which customers' complaints are urgent and which are routine, which numbers in a weekly report usually mean nothing and which are worth a second look.

None of that transfers with the job description. A new hire arrives with the required skills and none of the specific, hard-won context that made their predecessor efficient. They rebuild it the only way it can be rebuilt without help — by making the mistakes the previous person already made, and learning from them the same slow way.

Why this is easy to underestimate

Because it doesn't appear as a single cost anywhere. It's distributed across months of slightly-worse decisions, slightly-slower judgement calls, and the general friction of someone still figuring out the unwritten rules. Nobody puts a number on it, so nobody notices the business is effectively paying twice for knowledge it already owned once.

It's most visible in hindsight, when a new hire eventually says something like "I wish someone had told me this three months ago" about a piece of context that existed, fully formed, in someone else's head the entire time they were struggling.

Where it compounds

High-turnover roles pay this cost repeatedly. If a position turns over every year or two, and nothing is captured between departures, the business is perpetually funding the same learning curve on a loop, with no reduction over time despite having "learned" the lesson multiple times already.

Roles with a lot of tacit exception-handling suffer most. Customer service, procurement, and frontline operations roles are dense with judgement calls that never made it into a manual — see what leaves with an employee that the ERP never had.

Growing businesses feel it hardest, because growth means hiring into roles for the first time, at exactly the moment the business can least afford a new hire operating at reduced effectiveness for months.

Why a job description and SOP aren't enough

A job description covers what the role is responsible for. An SOP covers the standard process, step by step. Neither covers the judgement layer sitting on top of both — what to do when the standard process doesn't quite fit the situation in front of you, which is precisely the moment a new hire most needs guidance and least has it.

This is the same gap this cluster keeps returning to from different angles: structured documents capture structure well and judgement not at all — see transactions are not decisions.

Reducing the relearning tax

Capture judgement calls as they're made, continuously, not as a one-time knowledge-transfer exercise when someone announces they're leaving. By the time departure is announced, much of the most valuable, hardest-won context is already too routine for the departing person to think to mention it.

Pair new hires with someone who's done the role, even briefly, rather than relying entirely on written material. A few weeks of shadowing surfaces the judgement calls that a document never would, because the new hire can ask "why" in the moment instead of guessing later.

Track how long it actually takes new hires to reach full effectiveness, and treat a long ramp-up as a symptom worth investigating, not just a normal cost of hiring. If the same role keeps taking six months to get someone productive, the knowledge transfer process — not the hire — is usually where the fix belongs.

Common questions

Why does a replacement hire cost more than their salary?

Because a new hire typically lacks the accumulated judgement their predecessor built up over time — which suppliers to trust, which exceptions are routine, which numbers deserve scrutiny. Rebuilding that judgement takes months of reduced effectiveness, an invisible cost that never gets itemised the way salary does.

Why don't job descriptions and SOPs prevent this?

Because they document the standard process, not the judgement calls needed when a situation doesn't quite fit that process. Most of what makes an experienced employee efficient is exactly that judgement layer, which documentation of the standard process was never designed to capture.

Which kinds of roles suffer most from this problem?

Roles dense with exception-handling and tacit judgement — customer service, procurement, frontline operations — where a large share of daily decisions depend on context nobody wrote down. High-turnover versions of these roles pay the relearning cost repeatedly, with no reduction over time.

What's the most effective way to reduce this cost?

Capture judgement calls continuously as they happen, rather than trying to extract knowledge only when someone announces they're leaving. Pairing new hires with someone experienced, even briefly, also transfers far more than written material alone, because it allows real-time "why" questions.

Related: what leaves with an employee that the erp never had · transactions are not decisions · onboarding a new staff member