If new hires become fully productive by shadowing someone for a few weeks and picking things up as they go, that’s not really onboarding. It’s an informal apprenticeship that happens to work most of the time, and it gets more expensive every time you hire.
It ties onboarding capacity to whichever senior staff member has time that week, which doesn’t scale past a handful of hires a year. It’s also inconsistent: each new person picks up a slightly different version of the process depending on who trained them, which quietly compounds into a team that all does the same job in different ways.
A properly documented process (see our piece on documenting a process so it doesn’t live in one person’s head) turns tacit, undocumented knowledge into a checklist a new hire can follow with reasonable confidence on day one, instead of needing someone standing over their shoulder for weeks.
A slow ramp-up isn’t a one-time cost. Every week a new hire isn’t fully productive is a week of reduced output, and it repeats identically for every person you bring on. A business hiring 10 people a year at even one extra unproductive week each is losing 10 weeks of capacity annually to a fixable process gap.
In that same engagement, documenting the core workflows cut new-hire ramp-up time by 35%, and order handling errors dropped from roughly 1 in 20 to 1 in 60, because new hires were following the same accurate process instead of a slightly different version each time.
Onboarding still running on “ask around until someone shows you”? A Project Engagement builds documented SOPs around how your team actually works