What onboarding actually measures

Businesses track time-to-productivity for new hires as if it primarily measures the hire — their aptitude, their prior experience, their fit for the role. It's a reasonable enough proxy on average, but it obscures something more useful: time-to-productivity is at least as much a measure of how much of the role's actual knowledge exists somewhere accessible, versus how much lives only in the heads of the people currently doing it.

Two roles, same difficulty, very different ramp-up times

Imagine two equally demanding roles. In the first, the process is well documented, exceptions are explained, and a new hire has a genuine reference for the judgement calls they'll encounter. In the second, the process exists mostly as tribal knowledge, and a new hire learns almost entirely through direct experience and asking colleagues.

A capable new hire in the first role reaches full effectiveness measurably faster than an equally capable hire in the second — not because the first role is easier, but because the first role has externalised more of its knowledge into a form a newcomer can actually access. If a business only tracks the outcome — time-to-productivity — without asking why it differs between roles, it risks concluding something about hiring quality when the real driver is documentation quality.

Why this matters for how a business interprets its own onboarding data

A role with a consistently long ramp-up time is usually treated as a hiring problem — are we recruiting the wrong profile, is training insufficient, does the role need better screening. Sometimes that's the right diagnosis. Often, the more accurate diagnosis is that the role depends heavily on tacit knowledge that was never captured, and no amount of better recruiting will fix a gap that's actually about documentation — see why a new hire's first three months are spent asking why.

Misdiagnosing this leads to the wrong fix. A business that responds to a slow-ramping role by tightening its hiring criteria, when the actual problem is an undocumented judgement gap, will keep experiencing the same slow ramp-up with every future hire, regardless of how carefully they're selected.

A more useful way to read onboarding data

Compare ramp-up times across roles with similar seniority and complexity. If one role consistently takes longer than comparable roles, that's a signal worth investigating specifically as a knowledge gap, not automatically as a hiring or training issue.

Ask new hires directly what surprised them or what they wish had been explained sooner. Their answers are a direct, first-hand measure of what wasn't captured anywhere accessible, collected at exactly the point where the gap is freshest and most visible to them.

Track the specific questions new hires ask repeatedly across different individuals. If several different new hires independently ask the same question in their first few months, that's not a training gap specific to any one of them — it's a documentation gap in the role itself, and it's worth fixing once rather than answering informally every time someone new joins.

What this reframing changes in practice

Once ramp-up time is understood partly as a documentation metric, investing in capturing reasoning and judgement stops being a vague, hard-to-justify good practice and becomes something with a measurable target: shortening a specific, trackable number for a specific role. That's a much easier case to make than an abstract argument about the value of institutional knowledge — see a decision log is cheaper than the mistake it prevents.

Common questions

Why is time-to-productivity not purely a measure of a new hire's ability?

Because it's also heavily influenced by how much of the role's knowledge is externally accessible versus locked in the heads of current staff. Two equally capable hires can ramp up at very different speeds depending entirely on how well the role's judgement calls and exceptions have been documented, independent of their own skill.

What happens if a business misreads a slow ramp-up as a hiring problem?

It tends to respond by tightening recruiting criteria or increasing formal training, when the actual issue may be an undocumented judgement gap in the role itself. This fix doesn't address the real cause, so the same slow ramp-up recurs with every future hire regardless of how carefully they were selected.

How can a business tell whether a slow ramp-up is a documentation problem?

Compare ramp-up times across similarly complex roles — a consistent outlier is worth investigating as a knowledge gap. Also track whether multiple different new hires independently ask the same questions in their first few months; a repeated question across different individuals points to a gap in the role's documentation, not in any one person's onboarding.

How does reframing onboarding data this way help a business act on it?

It turns an abstract argument about the value of institutional knowledge into something measurable — a specific ramp-up time for a specific role that can be tracked and targeted for improvement, which is a far easier case to justify investing in than a general appeal to documentation best practice.

Related: why a new hire's first three months are spent asking why · a decision log is cheaper than the mistake it prevents · rehiring the same knowledge twice