How to Read Between the Lines of Vague Performance Feedback

"Needs more polish." "Not quite senior-level yet." "Could be more proactive." Vague feedback is common because it's genuinely easier to give than specific feedback, not because there's nothing specific behind it. Most of the time there is something concrete underneath, and it's worth the work of getting to it.

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. Notice which words are doing the work

   Certain phrases show up constantly in vague feedback, and each one usually maps to something more specific underneath.

   • "Needs more polish" often means specific gaps in execution, communication, or attention to detail on a particular piece of work.
   • "Not quite senior-level yet" usually points to a specific gap against a leveling criterion, not a vague sense of readiness.
   • "Could be more proactive" often means a specific instance where something was expected but not initiated.

2. Ask for one concrete example on the spot

   This single question does more work than almost anything else in this situation, and it's easy to ask.

   • Ask: "Can you give me a specific example of when that showed up?"
   • If the first example is still vague, ask for a second - the pattern usually becomes clear by then.
   • Write the example down as it's given, not your interpretation of it - the exact words matter later.

3. Translate vague praise the same way you translate vague criticism

   "Great year" feels good to hear and gives you almost nothing to build on. It's worth the same treatment as a vague criticism.

   • Ask what specifically stood out, not just that the year went well overall.
   • Find out if the praise maps to something you should keep doing exactly as is, or something you could do even more of.
   • Don't let positive feedback go unexamined just because it's pleasant to hear.

4. Watch for feedback that's really about visibility, not skill

   Some vague feedback isn't about the quality of your work at all - it's about your manager not having seen enough of it.

   • If the feedback surprises you given what you know you delivered, consider whether it's a visibility gap rather than a skill gap.
   • Ask directly whether your manager saw the work in question, or heard about it secondhand.
   • If it's a visibility problem, the fix is different - see Staying Visible as a Remote or Hybrid Employee.

5. Write down the vague version, then your best guess at the real one

   Putting both versions side by side, in writing, makes the gap between them obvious and easier to close.

   • Write the exact vague phrase used.
   • Write your best guess at what it specifically means, based on the examples you got.
   • Keep both versions to check against as you follow up or work on it over the following weeks.

6. Follow up in writing if the meeting didn't clear it up

   Some managers give a more specific answer in writing, with time to think, than they do live in a review meeting.

   • Send a short follow-up naming the feedback and asking for one specific example if you didn't get one in the room.
   • Frame it as wanting to act on the feedback well, not as pushing back on it.
   • If the follow-up is still vague, that's useful information on its own about how specific this feedback ever was.

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.