Onboarding takes weeks in most South African SMEs for one reason: the job has never been written down. The knowledge sits in the head of the owner or a long-timer, and the new person learns it by asking small questions whenever that person is free.
Why does onboarding take four weeks when the job is not that complex?
A new hire is rarely the problem. The process they are trained into is undocumented, so it can only be transferred person to person, in fragments, at the speed of the busiest person's diary.
The usual pattern:
- Day one is the tour: the building, the toilets, the stock room, the WhatsApp group.
- Real work starts in week two, and only once a trainer is free enough to watch.
- The trainer answers questions, then goes back to their own work.
- Everything unusual lives in the trainer's head and only surfaces under pressure: the supplier who answers only on a Friday, the machine that trips the breaker under load.
- By week four the new person is "fine". In month two, the trainer resigns and the knowledge leaves with them.
That is not a training failure. It is a documentation failure wearing a training costume.
How long does onboarding actually take in your business?
Do not estimate it. Ask your last three starters one question: how many days passed between their first day and the first time you were comfortable leaving them alone with the core of the job? Write the three numbers down.
Track it as one line per starter, because averages hide the slow ones:
| Starter | Start date | First unsupervised core task | Days to autonomy | What was missing |
|---|---|---|---|---|
| P. Naidoo | 03 Feb | 14 Feb | 11 | No written stocktake method |
| T. Botha | 19 Feb | 02 Mar | 11 | Same gap, no SOP to open |
| L. Mokoena | 04 Mar | 11 Mar | 7 | Buddy had a written checklist |
A steady number is more useful than a target, because you can now see which starter was slow and why.
What does a new person need to be able to do alone?
Write ten tasks, not fifty. For a fitter, a receptionist or a shop assistant the list is short, and almost always the same short list. Each item should be observable and end in a real result.
- Change a customer record and confirm the change stuck
- Issue a quote using the correct pricing tier
- Handle the three most common complaints without escalating
- Complete a stocktake or a service report correctly
- Reorder a fast-moving item at the right threshold
- Do a cash-up and a banking deposit
- Confirm a delivery against a purchase order
- Escalate a supplier problem to the correct person
- Send a proper handover message before leaving a site
- Restore one file from a backup
A person is onboarded when they can do all ten unaided, not when they have completed week one.
Why does "just show them how you do it" not work?
Because showing is not capturing. Shadowing teaches one sequence to one person on one day, and produces nothing the next person can read at 06:00 when the shop opens or at a depot at 05:30 in winter. It also teaches the wrong lesson, that the work is only learnable from a veteran. Six months later that veteran is the problem, not the resource.
The fix is not more training. It is a written process short enough to read in five minutes and a named person answerable for keeping it true.
How do you capture a process when nobody wants to sit down and write?
Do not ask for written procedures. Ask a good operator to walk you through one job, out loud, while doing it, and record it. Then type it up the same day in their words and send it back for correction. Thirty to 40 minutes per process.
Three rules make this work:
- One process per session. "How to do a stocktake" is captureable. "How the business works" is not.
- Write it as it is actually done, not as it should be done. Correct the process afterwards, deliberately, once it is visible.
- Include the exceptions. The reason people phone the owner is not the normal step. It is the step where something went wrong last time.
Photograph the actual machine in your actual workshop, with your actual labels. A generic picture from the internet tells a learner nothing.
How should onboarding work for field, shift and contract staff?
Most of the work does not happen at a desk, so onboarding cannot be a desk activity.
- Put the core list where it works on a cracked phone screen: a single PDF, a WhatsApp broadcast, a laminated card at the workstation.
- Design for interruptions. Load shedding and a half-charged phone are normal, not exceptions. Anything needing a live connection needs an offline fallback.
- Use shadowing in short shifts. Two hours watching beats a full day of being talked past.
- Plan for someone who leaves after eight weeks. Seasonal and contract staff need a condensed version: safety rules, five common tasks, and who to call.
- Have the buddy shadow on the same shift, not an adjacent one. Nothing destroys early momentum faster than a trainer who is not there.
What should a new starter be given on day one?
Keep it to a single page. Everything else lives in the written process.
| When | What they get | Who owns it |
|---|---|---|
| Day one | Safety and site rules, the ten-item core list, contacts, WhatsApp group | Manager |
| Week one | Buddy shadowing on the same shifts, first supervised run of each task | Buddy |
| Week two | Own tasks with a check, escalation paths, process open beside them | Manager |
| Day 30 | Run the ten items unaided, review gaps, agree the next ten | Manager |
How do you know whether onboarding is working?
Two measures you can calculate in an afternoon.
Time to autonomy = working days from start date to the first unsupervised completion of all ten core tasks. Compare it per starter, alongside how long the role sat idle before that person arrived.
Question load on your best people = hours per week your most experienced staff spend answering questions a written process should have answered. Above a couple of hours a week, you have found where the next four weeks are hiding.
At Midlands Berry Farm, a 60-person operations team, onboarding was reduced from four weeks to four hours — 3x faster onboarding, 40% more time saved, and answers available at any hour rather than only when one person was free.
What is the fastest way to fix this in the next 30 days?
- Write the ten core tasks for your most common role. One page, one session, this week.
- Ask your last three starters for their days-to-autonomy number, and write it down.
- Nominate one written process every new person must read in week one.
- Assign a named buddy to every starter, on matching shifts, and block their time.
- Put the core list where staff can reach it without asking a human.
- Start recording every repeated question. After a month you will have an SOP list already prioritised by how often it was asked.
If you would rather have someone outside the business look at how your onboarding works than work it out alone, book a free strategy session and we will walk through it with you.