Feedback can feel substantial while leaving the recipient unsure what to do. A description such as be more strategic may express a manager’s concern without identifying the behavior behind it. CIPD’s performance-management guidance provides background on expectations, support and feedback. The practical task is to connect an observation about work with a change the person can understand and attempt.
Begin with an identifiable situation
A hypothetical manager might describe a proposal that omitted an implementation dependency, rather than telling an employee that they lack judgment. The specific example creates a basis for discussion. The employee can explain the context, identify missing information and assess whether the interpretation is fair.
Separating observation from inference matters. What happened is different from what the manager believes it means. Treating the inference as a fact can turn a useful conversation into an argument about identity or intent.
Agree on the next opportunity
A clear next step might involve a review checklist, an earlier consultation or a different way to present options. It should fit the person’s role and the resources available. Asking for a change without providing the necessary authority, time or information can make the feedback impossible to act on.
The conversation also needs a chance to revisit the result. A manager should not assume that delivering the message completes the process. Follow-up can show whether the change helped and whether the original explanation of the problem was correct.
Keep the exchange two-way
The recipient may know something the manager does not. Listening can reveal a process problem, conflicting priorities or an unclear expectation. Useful feedback improves the work and the shared understanding around it. Its value comes from the action it enables, rather than the force with which it is delivered.
