How to Onboard a New Production Worker in a 50-Person Factory (And why it usually goes wrong)
A new worker starts on Monday. By Friday, you'll know if it's working.
Most factory owners wing this. Not because they're careless — because nobody ever sat down and built a proper onboarding process. There's always something more urgent. So the new person follows someone around for a day, gets thrown in, and either figures it out or doesn't.
Here's what onboarding actually looks like in most factories — and what it could look like instead.
Without a system
Week 1 — The shadow
The new worker follows Marko. Marko is your best operator. He also has his own work to do, a deadline on Thursday, and zero patience for repeating himself. He shows the new person the machine, the process, the unwritten rules. Some of it sticks. Most of it doesn't. Nobody checks.
Week 2 — The questions
The new worker starts alone. The questions start immediately. Where's the tolerance sheet? What do I do when the material does this? Who do I ask about that? They interrupt Marko. They interrupt you. They make a mistake that costs two hours of rework because nobody told them about the exception to the standard procedure.
Week 3 — The verdict
You decide whether to keep them. But you're not really judging the worker — you're judging how well they survived a process that was never designed to work. Half the time the problem isn't the person. It's that nobody gave them what they needed to succeed.
The cost nobody calculates:
Marko lost 3–4 days of productive work
You had at least one quality mistake
The new worker is still not fully confident
If they leave in month two, you start over
With a system (using Train)
Before day one
You have a workbook for each station. Not a 40-page manual nobody reads — a short, structured guide with photos of the actual machine, the actual steps, the actual things that go wrong. Marko built it in an afternoon, six months ago. It took him three hours. He never has to do it again.
The new worker gets access before they arrive. They read it on Sunday night if they're motivated. They walk in on Monday already knowing what the machine looks like and what their first task is.
Day one — orientation, not guessing
You walk them through the factory. They already have context. The questions they ask are better — specific, practical, not "wait, what do I do first?" Marko spends one hour with them, not two days. He shows them the things the workbook can't show — the feel of the material, the sound the machine makes when something's off. The stuff that actually requires a human.
Week one — guided, not lost
The new worker follows the workbook at their station. Each step is there. The tolerances are written down. The exceptions are documented. When they have a question, they check the workbook first. Half the time the answer is already there. The other half they come to you or Marko — but with a specific question, not a general panic.
Week two — productive, not surviving
By day eight, they're doing the job. Not perfectly — but correctly. The mistakes they make are normal new-worker mistakes, not "nobody told me" mistakes. You can see it in the rework numbers.
Month two — they become the system
When something isn't in the workbook, they add it. A small note. A photo. A clarification. The workbook gets better over time. When the next person starts, the onboarding is already slightly improved.
The difference:
Marko lost 3–4 hours, not 3–4 days
Zero "nobody told me" quality mistakes in week one
The new worker is confident faster
If they leave in month two, the knowledge stays
What you actually need to build this
You don't need Train to do this. You can build it in Word documents, Google Docs, or a shared drive. The system matters more than the tool.
What you need:
A workbook per station — not a general factory handbook. One document, one machine, one process. Short enough that someone actually reads it.
Photos of the real thing — not stock images, not diagrams. A photo of your machine, your setup, your workspace. The new worker needs to recognize what they're looking at.
The exceptions written down — every process has a "but when X happens, do Y instead." These are the things that live in Marko's head. Get them out.
A short check at the end of each week — five questions. Did they understand the safety procedure? Can they set up the machine without help? Do they know who to ask when something breaks? Not a test — a conversation starter.
Someone responsible for keeping it current — not a committee. One person. When the process changes, they update the document. This takes ten minutes if you do it immediately and three hours if you wait six months.
Where Train helps
If you're doing this in Word docs and shared drives, you'll hit a few walls:
Finding the right document is harder than it sounds when you have twelve of them and three people have saved their own versions. Version control becomes a job. And getting a new worker to actually open and follow a document on a shared drive — without you standing over them — is harder than it should be.
Train puts everything in one place. Each workbook is structured the same way. The new worker opens the app, finds their station, follows the steps. You can see how far they've gotten. You can add a short quiz at the end to confirm they understood the critical steps. And when Marko updates a procedure, everyone gets the current version automatically.
It doesn't replace the human part of onboarding. It handles everything that doesn't need to be human.
The point
Onboarding fails in most small factories not because owners don't care, but because the knowledge that makes someone good at the job was never written down. It's in Marko's head. It's in your head. It's in the habits of people who've been there for years.
Getting that knowledge out of people's heads and into a format a new worker can actually use — that's the work. Do it once, properly, and every hire after that gets easier.