Busting the Myth of "Meets Expectations": Why This Rating is Actually the Performance Problem
The Myth Everyone Believes
Your employee got a "meets expectations" rating. You breathe a sigh of relief. They're fine. They're doing their job. No performance issues.
That's the myth. And it's costing your company millions.
Here's the truth: "Meets expectations" is the performance management equivalent of a credit score of 650. It's not good. It's not bad. It's dangerously in-between—and it's hiding a serious problem.
Most companies think it's a neutral, acceptable rating. It's not. It's a warning sign that nobody's treating as one.
What "Meets Expectations" Actually Means
Let's be specific about what this rating typically signals in most organizations:
The official definition: "Employee consistently delivers required tasks on time, meets core job responsibilities, and performs at an acceptable level."
What it usually masks:
- No new value created.
- No growth or development.
- Minimal initiative or problem-solving.
- Basic execution. Nothing more.
- No strategic contribution.
- They'll be doing this job in 5 years, unchanged.
That's not "fine." That's rot.
Why This Rating Survives (When It Shouldn't)
"Meets expectations" is the coward's rating. Here's why it lives:
1. It avoids hard conversations
Managers use it to punt on feedback. "They're not bad, they're just... fine." Except "fine" tells them nothing. No direction. No warning. No hope.
2. It protects against legal risk (it doesn't)
HR thinks middle ratings shield them. Wrong. Clear feedback defends you. Vague feedback doesn't.
3. It's lazy
Bell curves need a middle. So managers dump everyone there. Convenient. Accurate? No.
4. It requires no follow-up
"Meets expectations"? No PIP. No plan. No money. No urgency. Just a 2% raise and see you next year.
The Real Cost
"Meets expectations" ratings cost money in ways most companies don't track:
Wasted potential: You've identified someone isn't excelling. Then do nothing. They stay in a role they're mediocre at. They don't grow. Neither does the company.
Your top performers defect: They see "meets expectations" ratings, reasonable raises, and no differentiation for effort. They leave.
Broken promotions: You promote "meets expectations" people into big roles. They weren't ready. They fail. You lose them and the role.
The talent bench is empty: High performers left. "Meets" people never leveled up. When you need someone for a critical role, you have nobody.
Obsolescence: After 4 years of "meets expectations," someone hasn't learned anything new. They've become dead weight, and you're shocked.
The Rating Your Company Actually Needs
The problem isn't "meets expectations." The problem is that it's too vague to be useful.
Here's what companies doing this right do: They split the middle.
Instead of one nebulous "meets expectations," they distinguish:
- Below Expectations — Performance problem. Needs improvement plan. Clear timeline for change.
- Approaching Expectations — Not there yet. Newer hire, in learning phase, or growth area. Development focused.
- Solidly Meets Expectations — Actually meeting the role. Stable performer. Likely long-term in this position.
- Exceeds Expectations — Going beyond what the role requires. Creating new value. Promotion-track potential.
- Far Exceeds Expectations — Exceptional. Building company strategy, mentoring others, driving revenue or critical processes.
Now "meets expectations" actually means something. And it's clear: this person is exactly where they need to be, or they're not.
The Conversation That Should Happen
When someone gets "meets expectations," the conversation needs to change:
Bad version:
"You met your goals this year. You're doing fine. Here's your raise. See you next year."
Real version:
"You're solid at what you do. And that's the problem. After [X years/months], I need to know: are you staying in this role long-term? Are you working toward the next level? Or are you plateaued? Because if you're staying, we can stop pretending there's growth here and manage accordingly. If you're aiming higher, here's what the gap is and what we're investing in to close it. But we can't keep saying 'you're fine' while doing nothing."
That conversation is uncomfortable. It's also the one that matters.
What This Means for Your Performance Cycle
If your company uses "meets expectations," here's what needs to happen:
Redefine the rating. Not "acceptable," but specifically: "This person is stable in this role, not developing further, and we believe they'll be here in 3 years doing roughly the same thing." That reframe is honest.
Require an action for every non-exceed rating. If someone's not exceeding expectations:
- Are they new/learning? Structured onboarding + development plan.
- Approaching? Clear skill gaps + coaching timeline.
- Solidly meeting? Explicit conversation: staying or moving up? Both are fine, but decide.
Build a feedback loop. "Meets expectations" can't be a surprise in November. If someone's not exceeding, you should both have known in March.
Stop hiding behind the middle. The conversation is hard. The rating is accurate. But accuracy without action is just data collection.
The Uncomfortable Truth
"Meets expectations" works great for employees who are exactly where they want to be—coasting, safe, no desire for more.
It's catastrophic for employees with potential. They get no feedback that says "you're capable of more," so they assume you don't see it. They leave. You lose them.
It's also bad for companies, because you end up promoting someone who "meets expectations" into a role requiring someone who "exceeds" them. They fail. You now have a failed promotion and an empty senior role.
How High-Performing Teams Handle This
Companies with the best talent do something different: they make "meets expectations" a decision point, not a default category.
- New hire or learning? Approaching expectations (intentional, not permanent).
- Veteran doing solid work, wants to stay? Explicitly confirmed role fit. No growth expectation. Clear.
- Good performer with potential? Moved to development track. "Exceeding" work identified. Investment made.
- Problem performer? Below expectations (not a surprise to them).
No ambiguity. No accidental stagnation.
What This Means Right Now
If you're a manager:
- Pull your "meets expectations" list. For each person, ask: "Is this because they're new/learning, or because they're genuinely stable in this role?" Different people, different actions.
- Have explicit conversations. Not "you're fine"—"here's where you are, here's what comes next if you choose it."
- Stop using it as a default. If half your team gets "meets," your rating system isn't working.
If you're an employee:
- Don't accept "meets expectations" without clarity. Ask: "What does that mean for my role next year? My growth? My career here?"
- If you want more, say it. "Meets expectations" isn't a development environment. Push for either clarity (you're staying as-is) or investment (growth path).
If you're building a performance system:
- Split the middle. One rating for "stable" and one for "learning" tells different stories.
- Require action. Every non-exceptional rating needs a conversation and a next step.
- Make exceeding the expectation. If "meets" is 60% of your company, you're not creating incentives for growth.
FAQ
Is "meets expectations" actually a bad rating?
Not inherently, but it's usually used badly. The rating itself is fine—it's the lack of clarity and action around it that's the problem. If you're saying "You're at exactly the right level for this role, and we've explicitly decided that together," that's honest and healthy. If you're saying "You're fine, I guess," it's broken.
What if someone is happy doing a "meets expectations" job?
That's completely valid. But it needs to be an explicit choice, not a default. Some people want stability and clear expectations. Give them exactly that: transparent conversation about the role, the future (or lack thereof), and the value exchange.
Doesn't this make it harder to let people go?
No. Actually, it makes it easier and more defensible. If someone is below expectations and has had clear feedback with a timeline to improve, you have documentation. If someone is "meets" but you later say you need to let them go, you look arbitrary. Clarity protects both parties.
How often should we revisit ratings?
At minimum, quarterly check-ins on trajectory. Annual formal ratings. If someone's trajectory changes (promoted role, new project), reassess immediately.
Can someone move from "meets" to "exceeds"?
Absolutely. The rating should reflect current performance against current role. New responsibilities, new expectations. People grow, or they don't. The rating should track that.
The Bottom Line
"Meets expectations" is the performance management cop-out. It's comfortable, vague, and actionless.
High-performing teams don't use it as a default. They use it as a decision point: Is this person developing or stable? Growing or staying? We're investing or we're not.
Then they act accordingly.
Everything else is just theater.
Performance ratings only work when managers know how to use them. Confirm helps companies build fair, calibrated performance systems — with tools that make it easy to identify high performers, have honest development conversations, and create consistency across teams. Learn more at getconfirm.com.
