A Full Onboarding Calendar Is a Warning Sign
Four weeks, 23 calendar invites, a buddy program, an eleven-section Notion page. By week five she still couldn't name who owned the function next to hers.
Four weeks of onboarding. 23 calendar invites across them: orientation, team intros, product walkthroughs, tooling setup. A buddy program with weekly check-ins. A 30/60/90 plan in Notion. An onboarding hub with eleven sections covering company history, values, the stack, and an org chart current to the week the new hire started.
By week five, she still couldn't name who owned the function next to hers. Four weeks had produced an exhausted employee who absorbed the artifacts of onboarding and not the job.
This is the standard failure of growth-stage onboarding. The program optimizes for what can be designed: calendar invites, documentation, structured introductions. It skips what matters, which is whether the new hire can do the work by week five. Artifacts feel like onboarding because artifacts can be tracked. Job-readiness is harder to track, so it gets less design attention than it deserves.
The reason is structural. A new hire in week one is firehose-receptive. They'll absorb whatever you put in front of them, so the temptation is to put everything there: every meeting, every system, every name. The result is four weeks of cognitive overload and a new hire who recognizes every name on the org chart and can operate none of the systems those names own.
The better shape is apprenticeship-first. Week one: shadow a senior person doing the actual job. Week two: pair on real work, the new hire running about a third of it. Week three: the new hire does most of the work with the senior person on standby. Week four: the new hire owns it, with one weekly review.
That shape drops most of the calendar. The orientation material still lands, but in context: the values surface when a real decision tests them, the company history when a customer brings it up, the tooling when the new hire has to use the tool. The same logic explains why a new hire who asks no questions in week one is already drifting, and why the long-term success of a new hire is set by what they do, not what they attend.
The week-five test is unsentimental. Can the new hire do the work? Can they name the three relationships they need? Can they answer a plausible how-would-you-handle-X question without a tab open? If yes, onboarding worked. If no, the program graduated someone from orientation, not into the job.
Most companies grade onboarding on whether the program ran. The real question is narrower: is the new hire shipping in week five?