Setting Expectations With New Hires: What to Do Before Day One 

For the past two weeks, we’ve walked through when to hire and how to hire. If you followed those lessons, you figured out who you needed for the role and ran a real process instead of grabbing the first resume that looked decent. You welcome your new team member. 

Then, six weeks in, the new hire isn’t performing the way you expected. And you start wondering if you picked wrong. You probably didn’t.  

I’m Stephanie Everett, founder of Lawyerist Lab where we help law firm owners build better businesses. In our work with small firm owners, the pattern shows up constantly: the hire was solid. What was missing were clear, explicit expectations before day one. Not an assumption that “they’ll figure it out.” An actual, written, standard for what good looks like. 

When you miss that step, it can result in working getting redone and the owner slowly picking the task back up themselves. This week, we’re breaking down what we mean by setting expectations, what it costs you when you skip it, and how to build it into your hiring process starting now. 

Why Expectations Matter, and the Many Kinds You’re Actually Setting 

Here’s what makes this step easy to skip: expectations feel obvious to you. You’ve been doing this work, running this firm, and living inside these norms for years. Of course, the deadline is Thursday. Obviously, you flag a problem before it becomes a crisis. There’s no question you need to be ready to stay late the night before a trial starts. 

None of that is obvious to someone who started three weeks ago. What’s obvious to you is invisible to them, and the gap between those two things is where redone work, missed deadlines, and quiet resentment all come from. Expectations matter because they’re the only thing standing between a new hire’s best guess and your actual standard. Skip them, and you’re not really delegating. You’re hoping. 

And “expectations” is doing a lot of work in that sentence, because it’s not one thing. Most owners think they’ve covered it once they’ve named the task and the deadline. That’s a fraction of what a new hire needs to know: 

Performance expectations. What level of output counts as meeting the bar. Completing the task and completing it the way you’d have done it are two different deliverables. 

Quality expectations. The specific standard for how the work looks and reads, tone, formatting, and level of detail. 

Timeline expectations. Not just the deadline, but how far in advance you expect to hear if that deadline is at risk. 

Communication expectations. Response times, preferred channels, how much detail you want in a status update versus a quick heads-up. 

Availability expectations. Whether nights and weekends are ever part of the job, and exactly when, so nobody’s guessing about a boundary that was never stated. 

Decision-making expectations. What they’re empowered to decide on their own, and what needs to come to you first. Nothing erodes trust faster than a new hire getting corrected for a decision they had no way of knowing wasn’t theirs to make. 

Feedback expectations. How and when you’ll tell them how they’re doing, so silence doesn’t get read as approval. 

Cultural expectations. The unwritten norms about how people behave here, speaking up, disagreeing, asking for help, that never make it into a job description but get enforced anyway. 

Miss any of these categories and you haven’t set expectations. You’ve set a task list and left the actual standard to chance. 

Three Signs You Skipped This Step  1. You’re Redoing Their Work 

This is the most expensive version. A new paralegal drafts a client letter. It’s not wrong exactly, it’s just not how the firm does it. You rewrite it. Then you rewrite the next one. Three months in, you’re spending more time fixing their work than you would have spent doing it yourself. 

If that’s costing you even four hours a week at $150 an hour in your own time, that’s $2,400 a month. Over a year, that’s close to $29,000 in redone work, on top of what you’re already paying them in salary. 

That’s not a performance problem. That’s a gap in the standard you never actually communicated. 

2. You’re Avoiding the Conversation 

Six weeks in, something isn’t clicking, and instead of naming it, you keep hoping it self-corrects. Meanwhile, the new hire has no idea anything is wrong. They think they’re doing fine because nobody’s told them otherwise. 

This is the “no news is good news” trap, and it’s expensive in a different currency: trust. By the time you finally raise it, three months of misaligned work have piled up, and the conversation that could have been a five-minute course correction in week two is now a performance conversation that feels like an ambush to them and a confrontation to you. 

3. You’re the Bottleneck by Default 

Because expectations were never set clearly, everything routes back through you. Every question, every judgment call, every piece of work that needs a second look. You hired someone to take work off your plate, and instead you’ve added a layer of review to your week. 

Firm owners we work with in Lawyerist Lab often describe this moment the same way: they hired someone specifically to get their time back, and six months later they’re spending as much time managing the new hire as they used to spend doing the work themselves. The math never improves, because the missing piece was never the person. It was the absence of a standard anyone could be held to. The new hire is missing their operating instructions. 

Notice that none of this requires more hiring skill. It requires a different habit: writing the standard down before the person needs it, instead of discovering the standard in your own head the first time someone misses it. That’s a fixable gap, and it’s a smaller lift than most owners assume. 

How to Actually Set Expectations  Start With the Last Time It Went Right 

Don’t start by imagining the perfect hire. Start by remembering a piece of work from that role that landed well. What made it good? Tone, turnaround time, level of detail, who got looped in and when? That description, in plain language, is your starting standard. It doesn’t need to be polished. It needs to exist somewhere other than your head, and it needs to reach the new hire before their first assignment, not after their third mistake. 

Write It Down Before Day One 

A standard you’ve only said out loud once, in passing, during a busy week, isn’t a standard the new hire can refer to. Instead, build your operations manual. You don’t have to write the entire thing in a week. But do start capturing processes and details as you go. Generative AI is a big friend here and can help you capture your processes and expectations.   

Say the Unwritten Rules Out Loud 

This is the step almost everyone skips, because the unwritten rules don’t feel like rules to you. They feel like common sense. Say them anyway. How fast you expect a reply after hours. Whether you want to be told about a problem the moment it happens or once it’s solved. Whether pushing back on a partner’s draft is welcome or overstepping. None of this is instinctive. All of it gets enforced the first time someone breaks a rule they didn’t know existed. 

Match the Delegation to the Person, Not the Task 

A brand-new hire needs explicit, step-by-step direction: what to do, in what order, checked at each stage. Someone who’s been in the role six months needs less of that and more autonomy in everyday tasks for their role, checked in at milestones instead of every step. Delegating the same way to both people is its own version of skipping expectations. You either micromanage someone who’s ready for more, or hand full autonomy to someone who was never told what full autonomy looks like here. 

Put the Check-In on the Calendar Before They Start 

Don’t wait to see how it goes. Schedule several reviews of their work before their first day, not after you’ve already noticed something’s off. A short, specific check-in weekly for the first 2 months will catch misaligned standards while they are still five-minute conversations. The same gaps caught in month four are performance problems. Bottom line: don’t stay quiet.  

Confirm They Heard What You Meant 

Setting an expectation and having it land aren’t the same event. After you walk through the standard, ask them to repeat back what they heard in their own words. This takes two minutes and catches the gap between what you said and what they understood. 

The Foundation of Every Good Working Relationship 

None of this is complicated. It’s just easy to skip, because the standard already lives in your head and it feels obvious there. The work is getting it out of your head and into a conversation your new hire gets to have, before the first assignment, not after the third mistake. 

Do that, and you’ve given them something most new hires never get: a clear sense of what’s expected. This is the foundation the whole working relationship gets built on. Everything that comes after, trust, feedback, the freedom to eventually hand off bigger things without a second look, starts here. 

Do I need a formal onboarding document for a part-time or contract hire? Yes, at a smaller scale. Even a one-page version covering the standard, the check-in date, and the escalation path prevents the same guessing problem, regardless of hours worked. 

What if I don’t know exactly what “good” looks like myself? That’s common, and it’s a great realization. Start by describing the last time a piece of work from that role went right, and work backward from what made it right. Generative AI is a great help here, too. 

How is this different from a job description? A job description lists duties. Expectation-setting defines the standard for how those duties get done, on what timeline, and what happens when something goes sideways. 

Should I set expectations differently for an experienced hire versus a first-year hire? Yes. An experienced hire may need less step-by-step instruction but still needs the standard and the escalation path spelled out. Skipping it because “they’ve done this before” is one of the more common mistakes we see. 

What if I set expectations and the new hire still isn’t meeting them? That’s the point of the check-in cadence. A missed expectation caught in week two is a course correction. The same miss caught in month four is a performance problem. 

Can Lawyerist Lab help even if I’m not currently hiring? Yes. Most owners build their expectation-setting frameworks in Lab before they need them, so the next hire isn’t the first time they’re figuring this out. 

Does this apply to attorneys as well as staff hires? Yes, and it’s often more overlooked with attorney hires because owners assume law school and bar admission are proof enough that the standard is already understood. It isn’t. Your firm’s standard for client communication, billing narratives, or file management is specific to your firm, not something a new associate absorbs by osmosis. 

What if the new hire pushes back on the expectations I’ve set? That’s useful information, not a problem. It’s a chance to find out whether they disagree with the standard itself or don’t yet understand why it exists. Either way, that conversation is far cheaper to have in week two than to avoid until it shows up as a performance issue in month four.