Why week one is the highest-return week

Hiring gets the attention. The interview, the trial shift, the reference call — the full hiring process is worth doing properly.

Then the person arrives, and most restaurants stop trying.

They are put on the floor on day one because it is busy, told to "watch how it's done", corrected publicly for things nobody explained, and left to work out the table numbering by getting it wrong. Six weeks later they leave and the vacancy reopens.

Replacing an experienced captain costs roughly one and a half months of their salary once you count manager time, ramp-up, overtime absorbed by others and the errors along the way. Against that, a structured first week costs one person's partial attention for five days.

The first seven days decide retention more than the interview does. It is also the week restaurants staff worst, because it falls during service.

Before they arrive

Twenty minutes of preparation removes most of what goes wrong:

  • Name the trainer, and reduce that person's own load for the week. Not the most senior — the most patient person who does the job well and can explain why.
  • Have their access ready. Staff account created, role assigned, device charged. Someone standing around while a manager resets a password is a bad first hour.
  • Uniform ready in the right size.
  • Tell the team who is arriving, when, and in what role. Being introduced beats being noticed.
  • Write the week down. Even four lines. A plan that exists gets followed.

The seven days

Day Focus They carry
1 Orientation, menu, tools — before service Nothing
2–3 Shadowing an experienced person Nothing formally
4–5 Doing the job, trainer beside them A small section
6–7 Working independently with support A normal section

Day 1 — off the floor

The whole day happens with nobody waiting on them.

The room. Walk the floor and the kitchen. Table numbering — and make them find table 14 without help before the day ends. Where everything is kept. Where the exits and extinguishers are.

The team. Everyone by name and role. Who to ask about what. Who runs the pass.

The menu. Taste the top ten sellers. Not read about — taste. Someone who has eaten the dish recommends it differently. Cover the veg, Jain and allergen positions on the popular items, and the two or three dishes that take longest so they can set expectations at a table.

The tools. Whatever takes orders, on the real device, with the real menu. Ten practice orders end to end, including the awkward ones: a modification, a cancellation with a reason, adding a second round to an open order. This is the hour that decides whether they trust the system or quietly revert to a notepad in week three.

The rules that are not obvious. Break timings. Who to tell if they will be late, and how. What happens if a guest complains. What they are allowed to comp or fix themselves.

They should leave day one oriented and slightly bored, not exhausted and behind.

Days 2–3 — shadowing

They follow their trainer through real services carrying no formal responsibility.

The instruction that makes shadowing work: the trainer narrates. Not "watch me" but "I'm greeting table 6 first because they sat before 9, and I'm checking the biryani time because it takes forty minutes." A silent expert teaches almost nothing.

Give the new joiner one small owned task each shift — running water, clearing one section — so they are participating rather than trailing.

Days 4–5 — doing it, with a net

They take a small section. The trainer is physically nearby and free to step in.

Correct privately, always. A public correction on day four costs more confidence than the mistake cost service.

Debrief for five minutes at the end of each shift. Two things that went well, one to work on tomorrow. That order matters.

Days 6–7 — independent, supported

A normal section, with a named person to ask. By the end of day seven they should be able to run a shift; they will not be fast yet, and that is expected. Full speed is four to six weeks.

Train the why, not only the what

This is the difference between someone who follows rules and someone who makes good decisions.

  • Not "oldest ticket first" but "oldest ticket first, because otherwise an early table waits behind a late one for no reason they can see."
  • Not "mark items ready as they leave the pass" but "one at a time, so starters can go out before mains and the table's courses arrive in the right order."
  • Not "put notes on the item" but "on the item, not on the order, because that is where the line will actually read it."
  • Not "always greet within ninety seconds" but "guests wait much better once they have been seen — the greeting buys you the time the kitchen needs."

Rules cover the common cases. Reasons cover everything else, and restaurants are made of the everything else.

The check-in nobody does

Five minutes at the end of every shift for the first week, and again at day thirty.

Three questions:

  1. What went well today?
  2. What confused you?
  3. What did nobody explain?

Question three is the valuable one. New joiners see everything your team stopped noticing years ago, and that window closes after about a fortnight.

Most people who quit in month two had already decided in week one. A five-minute conversation is where you find that out while you can still do something about it.

Common mistakes

Training during a rush. The worst possible learning condition, and it teaches people that asking questions is an imposition.

"The team will show them." Unowned onboarding is no onboarding.

Menu training by handing over a printed menu. Have them taste the top sellers.

System training on the job. They will revert to paper at the first confusion and you will be running two systems.

Public correction in week one. Costs more than the error.

No day-thirty conversation. The point at which the initial goodwill has worn off and the real view has formed.

Assuming an experienced hire needs less. They need less on technique and just as much on your room — your table numbering, your menu, your way of running the pass. Skipping it because they have nine years' experience is how confident people develop wrong habits fast.

What to do before your next hire starts

  1. Write the seven days down. Four lines per day is enough.
  2. Name the trainer and reduce their load for that week.
  3. Prepare access, uniform and device before day one.
  4. Book the system and menu hour off the floor, before a live service.
  5. Put the five-minute debriefs in the diary, including day thirty.
  6. Write one page for the role — owned tasks, escalation, what good looks like. It doubles as the training outline. The wider structure is in restaurant staff management.

The short version

  • Week one decides retention more than the interview does, and it is usually the worst-staffed week.
  • Name one trainer and adjust their load. "The team will show them" means nobody will.
  • Day one is off the floor: the room, the team, the menu tasted, the tools practised with nobody waiting.
  • Train systems before a live service. Training during a rush is why people revert to paper.
  • Explain the why. Rules cover the common cases; reasons cover the rest.
  • Five-minute debriefs every shift, and again at day thirty. Most month-two leavers decided in week one.