7 Strategies for Setting Expectations That Actually Stick

I once worked on a technical training team for a large software rollout (cough... don't Google Cover Oregon, software, fail... cough). Our job was to take the contractor's step-by-step documentation and turn it into training for the whole organization.

There was just one problem. The documentation was wrong.

Buttons that didn't exist. Pages that didn't appear when you clicked next. Workflows that led nowhere. We flagged it immediately. The response? The people who update the documents are in India. You'll need to call them during their business hours.

For context: their business hours and ours did not overlap. We are like 12 hours apart...

The contractor had handed us a set of expectations; follow this guide, teach this process, without checking whether those expectations were actually achievable.

There was no two-way street. No mechanism for feedback. No acknowledgment that the people doing the work might have information worth hearing.

We were set up to fail before we started.

I'm pretty sure that managers don't do this on purpose. But unclear, inequitable, or one-directional expectations subtly (or sometimes not so subtly) undermine performance, erode trust, and create the exact problems they were meant to prevent. Here are seven strategies to make sure your expectations actually do what you intend them to do (gasp!)

1. Start With Yourself

Before you can set a clear expectation, you have to have one. That means knowing the difference between the written policy and your actual threshold and being honest about both.

If the attendance policy says tardiness is unacceptable, but you personally don't mind occasional traffic delays, that's fine. But you need to know that, name it, and apply it consistently. The more dangerous question is whether you're applying your standards equitably to everyone, regardless of how long they've been there, how much you like them, or how much they remind you of yourself.

Unconscious bias lives in the small daily decisions. Whose lateness gets a pass and whose gets a conversation is one of them. If you can't clearly answer "what does meeting this expectation actually look like," you're not ready to set it yet.

2. Set Expectations Early and Revisit Often

Expectations should be proactive, not reactive. If the first time someone hears a standard is when they've already violated it, you've already lost ground... and trust.

Onboarding is the obvious moment, but it's not the only one. New project, new role, new season, new policy, all of these are moments to reset. The one thing managers miss most often is when things change. Roles evolve. Priorities shift. If you don't explicitly reset the expectation, people are still operating on the old one and have no idea.

The unspoken expectation is the most dangerous one. It feels obvious to you and invisible to them.

3. Share the Why

Remember being a teenager and asking permission for something, only to be told "no" and "because I said so"? Remember how much that inspired your wholehearted cooperation?

People follow expectations better when they understand the reason behind them. Connect the standard to something bigger. A policy, mission, values, compliance, and client impact. The why also helps people make good judgment calls in situations you didn't anticipate. If they understand the purpose, they can extrapolate.

This is especially important in compliance-heavy environments. "We document every client interaction" lands differently than "We document every client interaction because if something goes wrong six months from now, that documentation protects you, the client, and the organization."

Same expectation. Completely different relationship to it.

4. Don't Assume They Know

Never assume the email was read. Never assume the policy was understood just because it was distributed. Never assume that because something is obvious to you, it's obvious to them.

Written documentation is the floor, not the ceiling. New employees, especially, are navigating an enormous amount of information and trying to figure out what's actually important versus what's technically in the handbook. They can't possibly remember everything.

And unwritten rules are the most dangerous of all. Every workplace has them. Nobody thinks to mention them until someone violates one. Go find yours and say them out loud.

5. Make It a Two-Way Street

This is where the software story comes back around.

When we flagged that the documentation was wrong, there was no real mechanism to address it. The expectation had been set, handed down, and locked. Our experience, the people actually doing the work, had no path back to the people who created the standard.

Setting an expectation should not be the final word on the subject. After you've communicated a standard, check for understanding, and not "does that make sense?" (everyone says yes) but "what questions do you have?" and "what might get in the way of this for you?"

The person receiving the expectation probably has information you don't. Surfacing barriers before they become problems is significantly easier than addressing them after something goes wrong. And sometimes the conversation reveals a problem with the expectation itself, which is information you need.

6. Follow Up in Writing

After a verbal conversation about expectations, send a short written summary. An email works perfectly — "Just wanted to recap what we discussed…" followed by two sentences.

This does two things. First, it confirms you're actually on the same page. You probably wouldn't be surprised how often people walk away from the same conversation with different understandings. Second, it creates documentation if things escalate later.

This isn't about being punitive or building a case. It is about clarity. And as Brené Brown says — clear is kind.

7. Celebrate When Expectations Are Met

Most managers only talk about expectations when something goes wrong. If the only time you reference a standard is when someone has violated it, expectations become associated with trouble — and that creates the exact threat response that makes future conversations harder.

Specific, genuine recognition when expectations are met reinforces the standard, builds the relationship, and signals to the whole team what right looks like. Public recognition of best practice is free training for everyone watching. (Caveat: If your person hates public recognition, keep that trust and don't do it.)

Not "good job", but "I noticed you've been submitting your reports by Thursday consistently for the last month, and it's making a real difference to how smoothly Friday goes. Thank you."

If people are doing what you asked them to do, they deserve to know you noticed. Don't assume they know (see Strategy 4).

Okay, so…

Most performance problems aren't really performance problems, but expectation problems: unclear standards, inconsistent application, assumptions that never got named out loud, or feedback that only flows one direction.

You can't hold people accountable to expectations you haven't clearly defined, equitably applied, proactively communicated, and genuinely listened to.

The software contractor handed us a broken guide and wondered why the training failed (and not just the training, but the whole darn project). Don't be the contractor.

Set the expectation. Share the why. Make it a conversation. Follow up. Celebrate when people get it right.

Clarity before accountability. Every time.