The standard small business onboarding is: follow someone around for a week, then start doing it, then ask questions when stuck.
That costs two people's time, produces inconsistent results, and takes as long as the new person's confidence takes to build. There is a better version and it is not complicated.
Why shadowing alone fails
It is not repeatable. Whatever they saw in that week is what they know. If the unusual case did not come up, they have never seen it.
It costs double. For that week, two people produce roughly one person's output.
It transmits habits, not reasons. They learn what the experienced person does, not why, so they cannot handle a variation.
It is invisible. Nobody knows what was actually covered. Six weeks later a gap appears and nobody can say whether it was taught.
What to have ready before day one
You do not need a training program. You need four things.
Written procedures for the most frequent work. Not everything — the handful of tasks they will do daily. See our note on writing your first SOP for the twenty-minute version.
A list of what they need access to, requested in advance so day one is not spent waiting for logins.
A first-week schedule, so somebody has thought about their time.
A named person to ask. Not "ask anyone," which means asking nobody. One person who expects the questions.
That is it. Preparing those four takes a day and saves a fortnight.
The sequence that works
Watch once. They observe the task done properly, with narration about the decisions.
Do it together. They perform it, with the experienced person present and not taking over.
Do it alone, checked. They do it independently and someone reviews the output before it goes anywhere.
Do it alone, sampled. Independent, with occasional review.
Four steps, per task, and it can be compressed into a couple of days for a simple one.
The step people skip is the third. Going from "we did it together" straight to "you're on your own" is where errors and anxiety both come from.
Give them the failure cases early
The main path is the easy part. What creates a confident new employee is knowing what to do when it does not go to plan.
Teach the exceptions explicitly. What goes wrong with this, what does it look like, what do you do, when do you escalate.
An employee who knows the boundary of their authority makes decisions. One who does not asks about everything, which puts the bottleneck straight back on you.
Let them write it down
The most useful documentation in most businesses is written by the person who just learned the job.
They notice everything the experienced person has stopped seeing. They know exactly which parts were confusing, because they were confused by them last week.
Have every new hire improve the procedures as they go. It costs them nothing extra, it makes the documents better, and it tells you where the gaps are.
Check in on a schedule, not on a feeling
Day three, end of week one, end of week two, end of month one. Short, specific, and initiated by you rather than waiting for them to raise something.
Ask what is unclear rather than whether they have questions. The second gets "no" from people who do not want to seem slow.
What good looks like
At the end of a month, a new person in a small business should be able to do the frequent work independently, know where the written answers live, know who to ask about what, and know the edges of their own authority.
That is achievable in a month with the structure above, and it routinely takes three without it.
Where this connects
Everything in this note depends on the processes being written down at all. If they are not, onboarding a new person is expensive every single time.
Write them once, and every hire after that is cheaper. That is the actual return on documentation, and it is why it is worth doing before you need it.