Understanding a 'Meets Expectations' Rating

A 'meets expectations' rating stings most when you walked in expecting 'exceeds.' It isn't a bad rating on paper, which is exactly why it's hard to know what to do with the disappointment. These are the principles for processing it and turning it into something useful, without treating it as a fight you need to win.

The principles

These aren't steps to complete in order - they're the things worth checking yourself against, before and during the work. Read them once, then keep this page open while you go.

1. Check what 'meets' actually means here before reacting to it

   The label carries wildly different weight company to company. At some orgs it's the default, solid outcome for most of the team; at others it's genuinely a signal of concern. Know which one you're in before you decide how to feel about it.

   • What share of the team typically lands at 'meets' versus 'exceeds' in a normal year?
   • Is 'meets' associated with any real consequence here (bonus tier, eligibility for promotion, PIP risk), or is it neutral?
   • Has anyone on your team gone from 'meets' to promoted without an intervening 'exceeds' cycle?

2. Test whether this was actually a surprise

   A fair process means you should have heard, mid-cycle, whether you were tracking toward the higher rating. If this is the first time 'exceeds' has been mentioned as something you fell short of, that's a feedback timing problem worth naming calmly, separate from the rating itself.

   • Did your manager flag at any point mid-year that you were tracking toward 'meets' rather than 'exceeds'?
   • If not, was that a gap in your visibility into your own standing, or a gap in how they managed the cycle?
   • Are you naming this as information for next cycle, or turning it into an argument about this one? Only the first is productive here.

3. Get the gap defined in concrete terms

   'Go above and beyond' is not something you can act on. The actual distance between 'meets' and 'exceeds' is almost always about scope, ownership, or visibility, not raw effort, and it's worth making your manager say exactly what that looks like.

   • Ask directly: what would have needed to be different about this specific work to land at the next rating up?
   • Ask for one concrete example from this cycle, if one exists, of work that would have crossed the line.
   • Confirm whether the gap is about doing more, or about doing something qualitatively different (owning a project end to end, influencing beyond your immediate team).

4. Don't let a prior promotion reset your baseline unnoticed

   If you were recently promoted or took on more scope, what used to read as exceptional can quietly become the new baseline expectation without anyone saying so out loud. Worth checking directly rather than assuming the bar stayed still.

   • Has your scope or level changed in the last 12 to 18 months?
   • If so, does this rating reflect the old bar or the new one, and does your manager think you've clearly cleared the new one yet?
   • Is what got you the last promotion now simply table stakes for your current level?

5. Turn the conversation into a plan, not a rebuttal

   Because this isn't a formal dispute, the highest-value move is walking out with something specific to aim at next cycle, not relitigating this one. That's also the version of this conversation your manager will engage with most openly.

   • Leave with two or three specific, measurable things that would move the needle next cycle.
   • Get agreement on how progress toward those will be checked before the next review, not just at it - logging evidence as you go in something like Perform Review's Achievement Log makes that check-in a lot easier than trying to remember it cold.
   • Put the agreed targets in writing yourself and send them, so there's no ambiguity in six months.

6. Know the difference between disappointed and actually disputing

   Feeling short-changed by a fair rating and believing the rating itself was wrong are different situations that call for different responses. Confusing them either turns a normal conversation into an unnecessary fight, or lets a real problem go unaddressed.

   • Do you have specific evidence the rating ignored, or do you simply feel you worked hard and expected more for it?
   • If it's the former, that's worth a real follow-up conversation focused on the evidence, not this one.
   • If it's the latter, the better use of your energy is the plan for next cycle, not arguing this one's number.

That's the whole playbook

None of this replaces judgement. It is the checklist for catching the moments where judgement quietly turns into habit, or into bias.