Setting Expectations in the First Week, Not the First Review

Why this matters

The single most common source of a soured new hire relationship is not a skill gap, it is a standard nobody stated out loud until a review meeting made it official. A new hire who is corrected for the first time at 30 or 60 days reasonably feels ambushed: nobody told them, and now it counts against them. The fix is not a better review process. It is moving the expectation-setting to the first week, before any performance has happened to judge.

Why the first review is too late

By the time a formal review arrives, one of two things has already happened, and both are expensive.

• The new hire has been doing it wrong for weeks, building a habit that is now harder to unwind than it would have been on day three.
• The new hire has been quietly guessing at what "good" looks like, second-guessing themselves, and possibly underperforming out of caution rather than incapacity, because nobody told them the actual bar.

Either way, the review becomes the moment you introduce a standard for the first time and simultaneously judge someone against it. That combination reads as unfair even when your intent is constructive, and it damages trust right when trust is most fragile.

What "expectations" actually covers

Expectations is a broader category than most owners initially name. Cover all of these explicitly in the first week, not just the technical ones.

• Quality standard. What does a finished job look like when it is done right? Show an example, not just a description.
• Pace and productivity. What is a reasonable number of jobs, calls, or tasks in a day at their experience level? Vague pace expectations are the number one source of a new hire feeling like they are constantly falling short of an invisible bar.
• Communication norms. How and when do they update you on a job, a delay, a problem? What channel, what frequency.
• Customer treatment. Tone, professionalism, how disputes get handled, what they can decide on their own versus what needs to come back to you.
• Safety non-negotiables. The handful of rules that have zero flexibility, stated as absolute, not as general guidance.
• Attendance and reliability basics. Start time, what "on time" actually means at your shop, the call-out procedure.

Most owners cover the technical and safety pieces well because those feel obviously important. Pace, communication norms, and customer-treatment expectations get skipped because they feel like common sense. They are not common; they are specific to your shop, and a hire from a different shop has a different common sense.

Say it, then show it, then have them say it back

Stating an expectation once in a rushed orientation does not make it stick. Use a three-step pass:

1. Say it plainly, out loud, in a specific sentence, not a vague value statement. "We call the customer if we're running more than fifteen minutes late" beats "we value communication."
2. Show it in action. Point to a real example, a job done right, a message sent the way you want it sent. Abstract standards become concrete the moment they see a real instance.
3. Have them restate it in their own words. "So if I'm running behind, what do I do?" This surfaces misunderstanding while it costs nothing, instead of finding out three weeks later that they heard something different than what you said.

Put the load-bearing expectations in writing

Verbal expectations fade and get misremembered, by both sides. The handful that matter most, the ones you would actually cite in a correction conversation later, should exist somewhere the new hire can look back at: a written standard, a one-page summary, a note in their onboarding record. This is not about building a legal file, it is about making sure "I told you that in week one" is actually true and checkable, not a memory you are both relying on.

Revisit early, not just once

Expectations set once in a rushed first week rarely land completely the first time. Build in a short check at the end of week one and again at day 30: "here's what I told you when you started, how's it matching what you're actually experiencing day to day?" This catches the gap between what you said and what they understood while it is still cheap to close.

The standard to hold yourself to

If a correction at day 60 would surprise the new hire, that is a sign the expectation was never actually set, not a sign the new hire failed to meet it. Before you judge performance against a standard, confirm you stated that standard clearly enough that a reasonable person would have known it. That discipline protects the new hire from an unfair ambush and protects you from a review conversation that goes sideways because it is really the first time the topic came up.

References

• Society for Human Resource Management (SHRM), setting new-employee performance expectations
• U.S. Small Business Administration (SBA), onboarding and employee expectations guidance
• See related: New Hire Week One: Set Up to Succeed
• See related: The 30-Day Check-In Goes Badly: Decision Tree