You finally hired someone, and now they are standing behind your counter on day one waiting to be told what to do. Most owners hand over a key, explain a few tasks between customers, and hope the rest gets absorbed along the way. That is how a promising hire quietly becomes a mediocre one — not because they were wrong for the job, but because nobody ever built the first thirty days.

Why This Matters

  • You stay the bottleneck. If every question routes back to you, hiring added a payroll line without buying back a single hour of your week.
  • People who are unsure default to doing nothing. A new hire who cannot tell whether a decision is theirs to make will stand still and wait, and you will read that as low initiative.
  • Early turnover is brutally expensive. Losing someone in month two means paying twice for recruiting, training, and the customer experience that suffered while they learned.
  • Correction feels personal when expectations were never written down. Without a standard on paper, every piece of feedback sounds like an opinion about them rather than a gap against the job.
  • You waste the one window where habits form easily. Whatever a new hire does for the first month is what they will keep doing for the next two years.

What Actually Works

Write the first week down before they walk in. Open a document and block out five days hour by hour: who they shadow, what they read, which system they get access to, and one small task they own by Friday. It takes about ninety minutes to build and you will reuse it for every hire after this one.

Teach one job at a time, then watch them do it. Demonstrate the task while narrating why each step exists, have them do it once while you stand there, then have them do it alone and check the result. Explaining a process verbally and walking away is not training — it is a coin flip.

Put four Friday check-ins on the calendar right now. Fifteen minutes, same time each week, three questions: what went well, where did you get stuck, and what are you still unclear about. Scheduled check-ins surface small confusions before they harden into habits, and they cost you an hour total across the whole month.

Define what good looks like in numbers or examples. "Be friendly with customers" is unmeasurable; "greet everyone within ten seconds of the door opening" is something a person can actually hit. Pick three or four standards for the role, write them on one page, and hand that page over on day one.

Is This Right for You?

If you have someone starting in the next month, or you have hired in the past year and it did not go the way you hoped, build this now. The same applies if you are paying someone part-time and quietly wondering whether they are worth the cost — nine times out of ten the problem is an undefined role rather than a bad person. An afternoon spent writing a first-week plan and a one-page standards sheet will pay for itself before their first paycheck clears.

If you are still a solo operator with no hire on the horizon, do not build a training program yet. Spend that time documenting how you do your three most repetitive tasks instead — those notes become your onboarding material later, and they are useful today. And if you are bringing on a seasoned specialist to do something you have never done yourself, flip the approach: skip the task training, spend the first thirty days aligning on outcomes, budget, and decision rights, and let them design their own process.

Frequently Asked Questions

How long should onboarding actually take?

Plan structured onboarding for thirty days and expect real independence somewhere between sixty and ninety. Front-load the first week heavily, then taper — by week four your new hire should be running most of their day without checking in on routine decisions.

What if I am too busy to train someone properly?

Then train them on one narrow thing and let the rest wait. Pick the single task that eats the most of your week, teach only that until they are genuinely good at it, and add the next responsibility in week three. A person who is excellent at one job beats a person who is shaky at six.

Do I need a written employee handbook for one employee?

A full handbook can wait, but you do need a few things in writing: pay rate and pay schedule, hours and time-off expectations, and your policies on attendance and confidentiality. Keep it to two pages, have them sign it, and file the copy — it protects both of you if a disagreement ever comes up.

Onboarding is not a corporate ritual you have earned the right to skip because you are small — it is the difference between a hire who gives you your time back and one who quietly costs you more of it, which is exactly why we spend time on it in LaunchWakeForest. Block out an afternoon this week and write the first five days down.