Why new joiners copy workarounds, and how to induct them properly

A new joiner is handed a login and seated next to a busy colleague. Within an hour they are watching, copying and asking small questions. That colleague teaches whatever they do, including the odd detour. This is how bad habits spread.

Nobody means harm. The colleague learned from the person before, who learned from the person before that. Somewhere in the chain a step was invented to get round a fault, and it outlived the fault. The habit is invisible.

You can see the result in reports. Two clerks produce different numbers from the same task, because one learned the old route. A joiner copying a clerk who exports to a spreadsheet at every close will do the same for years, long after the report was fixed.

Before building an induction, collect the habits. Sit beside three experienced users for an hour each and note every step that the official method does not contain. Ask why they do it. The answers are often fair. Do not argue during these visits.

Sort what you find into two piles. Some steps cover a real gap, such as a missing field, and the software needs fixing. Others are leftovers from an old version and can simply be dropped. Write it all down.

Only after this sort can you write down what new staff should do. Otherwise the induction teaches the habit you are trying to remove. Write the steps only when the pile is sorted.

Keep it to the first two weeks. Day one covers login, the screen layout and the three tasks the role does most. A named buddy, trained for the purpose, sits with the joiner for the first live entries. Fixed length. Fixed content. No improvising.

Week one adds the next tasks and a practice session in a training copy of the system, with sample customers and sample stock. Week two ends with a short check where the joiner performs each task while someone watches. Build the practice data once, with a few awkward customers and one cancelled order, so every joiner meets the same traps in the same order.

Choose buddies who follow the current method, not simply the fastest typists. A buddy who cuts corners passes them on. Buddies matter.

The checklist lists each task the role must be able to do, with a date and a signature once it has been seen done correctly. It turns vague confidence into a record the supervisor can read in a minute. Keep one master copy per role, stored where the supervisor can edit it.

Pair it with a one page reference card for the three commonest tasks, placed beside the screen. When the joiner is unsure, the card answers before the neighbour does. Both stay on the desk.

Update both whenever the software changes. An out of date checklist teaches an out of date method, with a signature on it. Stale paper misleads.

Thirty days after joining, review a sample of the new person’s entries against the checklist. Look for the old workarounds. If one appears, trace it back and ask the buddy, not the joiner. Ask what they were told, who showed them and which screen confused them.

Feed what you learn into the pack. A recurring error means a card needs a clearer step, or the screen itself needs changing. Treat the joiner as a free audit of how clear your method is. Over a year, those notes make the best map of where your method is unclear, and they cost nothing to collect beyond a short conversation.

This week, write the checklist for one role. List its ten tasks and mark which ones have no written steps yet. Start small.