Feedback is only useful when an employee understands what it means for their work.
Comments such as “you need to be more proactive” or “your communication needs improvement” may sound clear to the manager giving them, but they leave an important question unanswered: what exactly needs to change?
When feedback is vague, employees are left to interpret the problem themselves. That can slow improvement and create frustration when the manager believes an issue has already been addressed.
Clear feedback is therefore an important part of effective Performance Management, particularly when an employee is expected to change a specific aspect of their performance.
Vague Feedback Describes the Problem Without Explaining It
Managers often use broad descriptions because they summarise the issue quickly.
Common examples include:
- “You need to communicate better.”
- “Be more proactive.”
- “You need to improve your attitude.”
- “Take more ownership.”
- “Your work needs more attention to detail.”
The problem is not necessarily that these observations are wrong. It is that they can mean different things to different people.
“Communicate better” might mean responding to emails sooner, providing project updates without being asked or escalating problems earlier. Unless the manager explains which behaviour is causing concern, the employee has to guess.
A useful test is simple: could the employee explain what they need to do differently after hearing the feedback?
If not, the feedback is probably too vague.
Turn General Feedback Into Something the Employee Can Act On
Specific feedback connects the manager’s concern to something that actually happened.
Compare these examples:
|
Vague feedback |
More actionable feedback |
|
“You need to communicate better.” |
“When a project is likely to miss its deadline, let me know as soon as the delay becomes clear rather than waiting until the due date.” |
|
“Be more proactive.” |
“For routine customer issues within your authority, I expect you to propose a solution before escalating them to me.” |
|
“Your attention to detail needs improvement.” |
“The last two client reports contained incorrect figures. Please check the source data against the final report before submission.” |
|
“You need to take more ownership.” |
“Once a task is assigned to you, I expect you to track the deadline and raise any obstacles before they affect delivery.” |
Specific examples make the gap visible. The employee can see both what happened and what should happen differently next time.
This does not mean managers need to prepare a detailed case every time they give feedback. One relevant example can often make a general concern much easier to understand.
Connect Feedback to the Expected Standard
Specific examples explain what went wrong, but employees also need to understand what acceptable performance looks like.
For example, telling an employee that three reports were submitted late identifies the problem. Telling them that weekly reports are expected by 3 pm every Friday gives them a clear standard to work towards.
This distinction matters because feedback should not leave employees trying to work out what “better” means.
Where expectations are already defined through role responsibilities, agreed goals or a formal Performance Appraisal process, feedback should connect back to those expectations rather than introduce a completely different standard during the conversation.
That also helps keep feedback focused on performance rather than personality. The conversation becomes about the gap between expected and actual performance, not whether the manager personally likes the employee’s working style.
Make the Next Step Clear
Even accurate feedback can have limited value if the conversation ends with the problem.
Consider:
“Your project updates haven’t been detailed enough.”
The employee understands the concern, but may still not know what a satisfactory update should contain.
A more useful conversation explains the next step:
“From next week, include the current status, outstanding issues and any risks to the deadline in each project update.”
The difference is practical. The employee knows what to change and the manager has something clear to review later.
Good feedback should therefore answer three basic questions:
What happened? → What was expected? → What needs to happen next?
This keeps the conversation focused without turning every piece of feedback into a formal performance process.
Vague Feedback Becomes a Bigger Problem When It Continues
One vague comment may simply result in a misunderstanding. Repeated vague feedback can create a much larger gap between the manager’s expectations and the employee’s understanding of their performance.
A manager may feel they have raised the same concern several times:
“I’ve told them repeatedly that they need to improve their communication.”
The employee may have heard those conversations very differently:
“I knew my manager wanted better communication, but nobody explained what I was doing wrong.”
That gap matters when the manager later decides the employee has failed to improve.
If a performance concern is important enough to raise repeatedly, the feedback should become more specific rather than simply more frequent. Repeating “you need to improve” does not create clarity.
Final Thoughts
Employees cannot reliably improve against feedback they have to interpret for themselves.
Useful feedback identifies the specific performance issue, connects it to a clear expectation and explains what should happen differently next time.
Managers do not need to make every conversation lengthy or formal. They do need to make the expected change clear enough that the employee knows what improvement actually looks like.
