Why Most Expectations Go Unmet

By Ty Sutherland

When someone on your team misses the mark, the instinct is to assume they didn’t care enough or didn’t try hard enough. But in most cases, the real problem is simpler and more fixable: they didn’t have a clear picture of what success actually looked like.

Unclear expectations are one of the most common and costly mistakes new managers make. You assume people know what you mean. They assume they understand what you want. Then deliverables come back wrong, deadlines slip, and frustration builds on both sides.

Setting Performance expectations well isn’t about being demanding or micromanaging. It’s about giving your team the information they need to do their best work—and removing the guesswork that gets in the way.

What “Setting Expectations” Actually Means

A lot of managers confuse expectations with instructions. Instructions tell someone what to do. Expectations define what good looks like when it’s done.

Strong performance expectations cover three things:

• The outcome: What does success look like? What should exist, happen, or change as a result of this person’s work?
• The standard: How good does it need to be? What level of quality, accuracy, speed, or completeness is required?
• The context: Why does this matter? How does this work connect to team or business goals?

When you cover all three, people can make better decisions on their own, ask smarter questions, and course-correct without waiting for your input at every step.

Start With Outcomes, Not Activities

One of the most common expectation-setting mistakes is describing activity instead of outcome. “I want you to work on the client onboarding process” tells someone what to do. “I want the average onboarding time reduced from 14 days to 8 days by end of quarter” tells them what to achieve.

Outcome-focused expectations are easier to measure, easier to evaluate, and much easier for your team member to own. When people understand the destination, they can figure out the best route. When you only give them the route, you’ve taken ownership of the result yourself.

Ask yourself before any expectations conversation: If this person does their job perfectly, what will be different? That answer is your outcome.

Use the “So That” Test

A simple technique for sharpening expectations is to finish every goal with “so that.” This forces you to connect the task to a real result.

• “Respond to customer inquiries within 4 hours so that customers feel supported and we reduce escalations.”
• “Prepare the weekly report by Thursday at noon so that the leadership team has time to review before Friday’s meeting.”
• “Document your process for each new client setup so that anyone on the team can cover your workload if needed.”

The “so that” makes the expectation feel meaningful instead of arbitrary. When people understand the reason behind a standard, they’re far more likely to hold themselves to it—especially when you’re not watching.

Make Standards Explicit and Specific

The word “good” is useless in a performance conversation. So are “thorough,” “professional,” “timely,” and “high quality.” These words mean something different to every person in the room.

Replace vague language with specific, observable criteria. Instead of “I want you to produce high-quality reports,” try: “Reports should be free of data errors, use the standard template, and include an executive summary that can stand alone without the supporting data.”

Some useful questions to help you define standards:

• What would a reviewer notice if this were done well versus done poorly?
• What has gone wrong in the past that you want to avoid this time?
• If someone new joined the team tomorrow, what would they need to know to meet this standard?

The more concrete your standard, the less room there is for a well-meaning person to miss it without realizing they have.

Involve the Person in Setting the Expectation

Expectations that are handed down without conversation tend to land poorly—even when they’re reasonable. People feel managed rather than trusted, and they have no stake in the outcome.

A better approach is to share the outcome you need and then invite the person into the conversation about how to get there. Ask questions like:

• “Does this feel achievable given what’s on your plate right now?”
• “What would you need to hit this target consistently?”
• “Is there anything about this that feels unclear or unrealistic?”

This isn’t about letting people opt out of accountability. It’s about building shared understanding and surfacing obstacles early, before they become missed targets. When someone helps shape how an expectation is defined, they’re more committed to meeting it.

Set Expectations at the Right Time

Many expectation conversations happen too late—after something has already gone wrong. At that point, you’re no longer setting an expectation, you’re delivering feedback on a failure. Both conversations need to happen, but they’re different, and conflating them is confusing for everyone.

The right time to set a performance expectation is:

• When someone joins your team or moves into a new role
• When a project kicks off or a new responsibility is assigned
• At the start of a new review cycle or planning period
• When standards have changed or a past pattern needs to shift

Don’t wait until the quarterly review to tell someone what you expect from them in that quarter. Expectations set in advance give people a chance to succeed. Expectations revealed after the fact just demoralize.

Write It Down

Verbal expectations fade. People remember what they want to remember, and two people can walk out of the same conversation with completely different understandings of what was agreed.

After any expectations conversation, send a short written summary. This doesn’t need to be formal or lengthy. A few bullet points in an email is enough. Cover:

• What the goal or expectation is
• The standard that defines success
• Any timeline or checkpoint that matters
• What support or resources are available

This creates a shared reference point that both you and your team member can return to. It also signals that you’re serious about this—and that seriousness is contagious.

Create Checkpoints, Not Surveillance

Once you’ve set an expectation, the job isn’t done. People need to know that you’re paying attention and that there’s a safe way to raise problems before they become disasters.

Build in regular checkpoints—not to monitor people, but to give them a structured place to say “I’m off track” or “I need help.” Weekly one-on-ones work well for this. So do brief progress check-ins at the halfway point of a longer project.

The key is to make it normal to surface problems early. If people are afraid to tell you they’re behind, they’ll hide it until it’s too late to fix. Your job is to create an environment where early honesty is rewarded, not punished.

When you check in, ask open questions: “How is this going?” “What’s getting in the way?” “Are we still on track for the deadline?” These questions do more to surface reality than a status update email ever will.

When Expectations Aren’t Met

Even well-set expectations sometimes go unmet. When that happens, the first question to ask is whether the expectation was actually clear. Before you address the performance gap, rule out the communication gap.

Ask yourself:

• Did they know exactly what was expected?
• Did they have the resources and authority to deliver it?
• Did they have a chance to flag obstacles before the deadline passed?

If the answer to any of these is no, the conversation is about clarification and support, not accountability. If the answer is yes to all three, then you have a genuine performance issue to address directly—and you now have a clear, documented expectation to reference when you do.

Either way, you’re in a much stronger position than you would be if the expectation had never been clearly defined.

Common Mistakes to Avoid

Even managers who understand expectation-setting in theory make some predictable mistakes in practice. Watch out for these:

• Setting too many expectations at once. Three clear priorities beat ten vague ones. If everything is important, nothing is.
• Assuming past employees set the standard. “The last person in this role always did X” is not a useful expectation. Define it freshly for the person in front of you.
• Confusing effort with outcome. “I need you to really put in the effort on this” is not an expectation. Define what effort produces, not effort itself.
• Changing the standard mid-task without saying so. If priorities shift, say so explicitly and reset expectations in real time.
• Skipping the conversation for experienced team members. Tenure doesn’t eliminate the need for clarity. Experienced people still benefit from knowing what success looks like in this context, on this project, for this manager.

The Foundation of a High-Performing Team

Performance expectations aren’t a bureaucratic formality. They’re the foundation that everything else on your team is built on. When people know what’s expected of them, they can focus their energy instead of spending it wondering whether they’re on track. When they understand why it matters, they bring more of themselves to the work.

The managers who build the most capable teams aren’t the ones who set the hardest expectations. They’re the ones who set the clearest ones—and then do the work of supporting their people to meet them.

Start with one conversation this week. Pick one role, one project, or one recurring deliverable where expectations could be sharper. Define the outcome, set the standard, explain the context, and write it down. That single conversation could be the difference between a team that struggles and a team that delivers.