How to stop training new hires differently at every location

For two sites to train a new hire the same way, you need a shared path: the list of skills expected for the role, a real situation that validates each one, and a designated reference who signs off. The manager keeps the freedom to coach in their own way, but no longer decides alone what "trained" means.

Two commis, one week, two outcomes

A fictional example. A commis starts on Monday at the first site. The manager pairs her with the sous chef, who shows her how to strain stocks, how to rotate stock first in, first out, and how to clean down the station. Another commis starts the same Monday at the second site. His manager, short-staffed, has him peel vegetables and then clear dishes until Thursday.

End of the week: she can strain a stock, date a container and close her station. He has seen carrots. It is not a question of talent. One site has a reference person available and a training routine, the other does not. If you assess them afterward, you will be assessing the training, not the people.

Why every manager trains in their own way

• There is no list of what a new hire must know. Everyone decides on the fly, depending on how much time they have that day.
• Managers teach what they themselves received. They reproduce their own onboarding.
• The site constrains the training. On a rush day, the new hire goes wherever they get in the way least.
• Nothing measures the result. With no shared exit point, nobody knows who is trained.

The table: what is shared, what is free

Element	Shared across all sites	Free for the manager
Expected skills per role	Yes	No
Validation situation for each skill	Yes	No
Order of learning	Recommended	Yes, depending on the site
How to demonstrate, pace, mentoring	No	Yes
Reference who signs off	One per site, designated	Manager's choice
End date of the path	Set	Adjustable to the team

Seven steps to build the shared path

1. Choose a role. The one you hire for most often.
2. Bring the managers together for half a day. Each one lists what a new hire must be able to do alone by the end of the first week, then the first month.
3. Merge into a short list of skills. Five to eight. What divides the managers is exactly what needs to be settled.
4. Attach a validation situation to each skill. Not "has read the sheet" but "strained a stock alone in front of the reference."
5. Designate a reference at each site, responsible for signing off the validation. It is not necessarily the manager.
6. Link each skill to a short piece of content (a sheet, a video shot on site, a reference photo) that the new hire looks at during the lulls in service.
7. Review after three new arrivals. Each new hire says what they were missing. The path moves, the exit standard stays.

If the path changes nothing because instructions live elsewhere, start again from how to keep a standard alive. To avoid overloading your best team members, read training without turning your best employee into a full-time trainer. And for the end point, how to know when a new employee is actually ready.

What a validation in a real situation looks like

A fictional example for the skill "strain a stock." The site's reference watches the commis while she strains alone: choice of fine-mesh strainer, passing the liquid without pressing, container labeled and dated, station cleaned. He does not comment during the task, except for a risk. Afterward he says what is solid and what needs another go, then signs with the date if all four points are met.

The same task, checked against the same four points at the second site, earns the same signature. That is what "trained" means in your group: not a number of hours spent with someone, but a task observed, against a criterion known in advance. One manager may have taught the task in their own words, another in theirs. The criterion stayed the same.

Common mistakes

• Imposing the path without consulting the managers. They work around it.
• Producing ten modules before fixing the skills. Time passes, nothing is validated.
• Validating with an attendance signature. Being present is not knowing how to do it.
• Penalizing a manager whose new hire fails. You will get validations given out of kindness. Look instead for what the path was missing.

What to measure

• The number of skills validated per role at the end of the first week, by site. To spot where the path stalls, not to rank people.
• The number of questions new hires ask about the same instruction from one site to another.
• The reference's time spent on the new hire, over the length of the path.

Where Tsuno comes in

Tsuno carries the expected skills for each role and the job modules (recipes, food safety, service, culture) and links them to checklists and tasks. The new hire gets the same path whichever site they join; the reference validates skills with the date, and you can ask where each new hire stands. Tsuno connects the facts: it does not rank employees or rate a person. A training gap points back to the path, the schedule or the reference. Page to see: the Tsuno solution.

Key takeaways

Align the outcome, not the method. A shared path fixes what "trained" means, a validation in a real situation proves it, and each manager keeps the freedom to coach.