This content may be of interest to you
Resources
A manager sometimes knows that feedback is needed but puts off the conversation. He waits for the right moment, searches for the perfect wording, or fears triggering a defensive reaction. Feedback in management is most effective when it stems from a specific situation, describes observable facts, and opens a discussion about next steps. The method matters, but it’s not enough. The manager must also establish a framework, listen to the response, and monitor progress. This article focuses on the manager’s day-to-day practice.
Prepare your feedback based on a recent event. Before the conversation, write down what you saw or heard, without interpreting the person’s intentions.
Replace "you are unreliable" with a verifiable situation: "The report was supposed to be sent on Tuesday. It was sent on Thursday, with no mention of the delay."
This clarification provides a common starting point for the conversation. It also prevents the employee from looking for counterexamples to an accusation that is too broad.
Before you speak, clarify your intention. Do you want to acknowledge a behavior, correct a mistake, understand a challenge, or support someone’s progress? Your intention influences the tone and the course of the conversation.
The right time depends on the situation and the type of feedback.
Provide feedback shortly after the incident occurs, in an appropriate setting. Behavior that poses a risk to a client, a team, or a project should not be left until the annual review.
Prepare for a more relaxed conversation. Use a recent example, then ask the person how they see the situation and what they want to try out.
Stick as closely as possible to the observed behavior. A recognition made several weeks later loses some of its accuracy.
The same word, “feedback,” can refer to different types of conversations. A manager must decide on the objective before choosing how to phrase it.
Clear managerial feedback follows a simple structure: situation, behavior, impact, and next steps.
Example: "At Monday's committee meeting, you presented three options without recommending a specific choice. The group was unable to reach a decision. For the next meeting, prepare your recommendation before presenting the alternatives."
This phrasing describes what happened. It explains the resulting effect. Finally, it sets a concrete expectation.
Avoid words that judge the person: difficult, unmotivated, unprofessional, overly sensitive. Describe what you actually observe. Behavior can change. Labeling someone closes off the conversation.
To prepare feedback on a specific deliverable or situation, you can use the COIN method. The dedicated page details the context, observations, impact, and next steps.
Giving feedback doesn't mean talking all by yourself. After you give your feedback, allow time for the other person to respond. They may provide context, acknowledge a problem, or challenge your interpretation.
Listening doesn't mean automatically withdrawing your request. It means distinguishing between the facts, possible causes, and the next steps.
You can ask questions such as:
If the person defends themselves, bring the conversation back to the specific fact. Don't try to win the argument. Focus on establishing what happened and what needs to change.
Feedback that isn't followed up on remains just an observation. The conversation must lead to an action, a commitment, or a new follow-up point.
The next step can be simple: give another presentation, let people know sooner if you're running late, share a method with the team, or ask for feedback after dealing with a new situation.
Work out the next steps with the person when the situation allows. “What do you suggest for the next meeting?” fosters more accountability than a list of orders.
In an urgent or recurring situation, however, the manager must set clear expectations. Listening should not replace providing guidance.
Follow-up allows you to verify whether the feedback has led to an observable change. It’s not about monitoring every single action. It’s about revisiting the commitment that was made and seeing what has changed.
During a one-on-one check-in, ask: "What have you tried since our last conversation?" or "What's been most helpful to you in this area?"
Follow-up can also acknowledge progress. If the manager focuses only on shortcomings, feedback becomes associated with correction. A balanced management approach also highlights positive behaviors.
Feedback flows in both directions. An employee can report a conflicting priority, a decision that is difficult to implement, or a lack of information.
The manager sets the stage for this feedback by thanking the person, rephrasing their point, and explaining what they can do. They must also clearly state what cannot change and why.
Bottom-up feedback does not automatically mean challenging every decision. It provides insight into the reality on the ground and allows for necessary adjustments.
A meaningful conversation doesn't need to be perfectly worded. It needs a specific fact, a clear intention, and an appropriate setting.
Feedback that touches on punctuality, quality, attitude, and independence can be difficult to address. Choose the most important topic. Save the others for a separate discussion.
The "sandwich" feedback method can make the message unclear. To understand its limitations and alternatives, visit the page dedicated to "sandwich method".
Reflecting on a behavior should not lead to a judgment about the person. Focus on the facts and the impact it had.
Without follow-up, the manager won't know whether the discussion was understood and put into practice. Plan an observable next step.
The content of the feedback varies depending on what you’re trying to improve. A conversation about a deliverable isn’t conducted the same way as a discussion about behavior or a decision.
Stay true to the expectations defined at the outset. Describe what meets the need, what is missing, and the impact on the rest of the project.
Example: "The memo accurately reflects the decisions that were made. However, it does not include the people responsible for each action or the dates. The team is not yet able to track progress. Please add this information before the final version is shared."
In this way, the manager avoids commenting on the person or their level of commitment. Instead, they link the feedback to the expected quality of the work.
A behavior often relates to cooperation, communication, or attitude. It may be more subtle to pick up on. The manager should describe a specific, recognizable situation and avoid drawing general conclusions.
Example: "During the last two meetings, you responded before people had finished speaking. Several people were unable to finish their points. Let them finish their thoughts before you respond."
The wording focuses on what happened. It does not turn a habit into a personality flaw.
An initiative may produce an imperfect result while still demonstrating a useful capability. Feedback should acknowledge the person’s willingness to take responsibility and specify what needs to be adjusted.
Example: "You proposed a new division of tasks without waiting for the next committee meeting. The idea helped get the project back on track, but two people hadn't been informed. Next time, let the team know before changing the division of tasks."
In this way, the manager avoids discouraging initiative while maintaining a framework for coordination.
Feedback on a decision should distinguish between the decision itself and the way it was explained. A decision may be difficult to accept even if it was not the wrong one.
Ask yourself whether the problem stems from a lack of information, a delay, a decision, or a communication issue. This distinction makes feedback more precise and prevents you from challenging the entire decision when it’s only the framing of the decision that’s problematic.
Upward feedback should link a situation to its impact on work. Describe what you observed, then ask what might help the team.
Example: "Priorities have changed twice this week without any explicit criteria for deciding which to choose. The team has started several tasks without knowing which ones to finish. Could we set the top priority at the beginning of each week?"
Feedback remains professional when it focuses on working conditions rather than on the person’s worth.
A person may dispute the described fact, the stated impact, or the request made. This reaction does not necessarily mean that the person is refusing to engage in any discussion. It may indicate a disagreement, a missing context, or a different perception.
Start by distinguishing between what is observable and what is based on your interpretation. If you say , “You sent the document on Thursday instead of Tuesday, ” the person may explain the delay. If you say , “You never meet deadlines, ” they will first have to defend their reputation.
You can respond: “I’d like to hear more about the context. The point I’d like to address is still the announced deadline and how to notify the team in case of any issues.” This phrasing keeps the conversation on track without shutting it down.
If the impact is up for debate, focus on the concrete consequences. Who had to adjust their work? What decision was delayed? What information was missing? Avoid attributing a reaction to the entire team if you can’t back it up.
If the person acknowledges the problem but does not suggest any next steps, help them come up with a course of action. If the behavior continues despite several discussions, the matter may require a more formal intervention. The manager should then clarify expectations and possible consequences.
A feedback conversation doesn't have to turn into a full-fledged interview. Prepare a main topic and a next step.
Before the exchange, write:
Get right to the point: "I'd like to follow up on this morning's client meeting. I noticed something that could help us ensure the success of the next presentation."
Next, describe what happened. Give them a moment to respond. Paraphrase what you’ve understood, then move on.
If there are several issues, choose the one that has the greatest impact on your work. You can address the others separately. A conversation that covers too many topics can quickly come across as a general negative assessment.
Length does not guarantee quality. A short exchange may be sufficient if the message is clear, the person can respond, and the next steps are clear.
Feedback in management works best when it is specific, direct, and action-oriented. Set the stage, choose the appropriate tone, listen to the response, and follow up on the next steps.
Start with a single recent topic. Describe the situation without judgment. Then ask the other person how they see the next step. The quality of feedback is measured less by the elegance of the phrasing than by the clarity of the conversation and what changes as a result.
A manager sometimes knows that feedback is needed but puts off the conversation. He waits for the right moment, searches for the perfect wording, or fears triggering a defensive reaction. Feedback in management is most effective when it stems from a specific situation, describes observable facts, and opens a discussion about next steps. The method matters, but it’s not enough. The manager must also establish a framework, listen to the response, and monitor progress. This article focuses on the manager’s day-to-day practice.
Prepare your feedback based on a recent event. Before the conversation, write down what you saw or heard, without interpreting the person’s intentions.
Replace "you are unreliable" with a verifiable situation: "The report was supposed to be sent on Tuesday. It was sent on Thursday, with no mention of the delay."
This clarification provides a common starting point for the conversation. It also prevents the employee from looking for counterexamples to an accusation that is too broad.
Before you speak, clarify your intention. Do you want to acknowledge a behavior, correct a mistake, understand a challenge, or support someone’s progress? Your intention influences the tone and the course of the conversation.
The right time depends on the situation and the type of feedback.
Provide feedback shortly after the incident occurs, in an appropriate setting. Behavior that poses a risk to a client, a team, or a project should not be left until the annual review.
Prepare for a more relaxed conversation. Use a recent example, then ask the person how they see the situation and what they want to try out.
Stick as closely as possible to the observed behavior. A recognition made several weeks later loses some of its accuracy.
The same word, “feedback,” can refer to different types of conversations. A manager must decide on the objective before choosing how to phrase it.
Clear managerial feedback follows a simple structure: situation, behavior, impact, and next steps.
Example: "At Monday's committee meeting, you presented three options without recommending a specific choice. The group was unable to reach a decision. For the next meeting, prepare your recommendation before presenting the alternatives."
This phrasing describes what happened. It explains the resulting effect. Finally, it sets a concrete expectation.
Avoid words that judge the person: difficult, unmotivated, unprofessional, overly sensitive. Describe what you actually observe. Behavior can change. Labeling someone closes off the conversation.
To prepare feedback on a specific deliverable or situation, you can use the COIN method. The dedicated page details the context, observations, impact, and next steps.
Giving feedback doesn't mean talking all by yourself. After you give your feedback, allow time for the other person to respond. They may provide context, acknowledge a problem, or challenge your interpretation.
Listening doesn't mean automatically withdrawing your request. It means distinguishing between the facts, possible causes, and the next steps.
You can ask questions such as:
If the person defends themselves, bring the conversation back to the specific fact. Don't try to win the argument. Focus on establishing what happened and what needs to change.
Feedback that isn't followed up on remains just an observation. The conversation must lead to an action, a commitment, or a new follow-up point.
The next step can be simple: give another presentation, let people know sooner if you're running late, share a method with the team, or ask for feedback after dealing with a new situation.
Work out the next steps with the person when the situation allows. “What do you suggest for the next meeting?” fosters more accountability than a list of orders.
In an urgent or recurring situation, however, the manager must set clear expectations. Listening should not replace providing guidance.
Follow-up allows you to verify whether the feedback has led to an observable change. It’s not about monitoring every single action. It’s about revisiting the commitment that was made and seeing what has changed.
During a one-on-one check-in, ask: "What have you tried since our last conversation?" or "What's been most helpful to you in this area?"
Follow-up can also acknowledge progress. If the manager focuses only on shortcomings, feedback becomes associated with correction. A balanced management approach also highlights positive behaviors.
Feedback flows in both directions. An employee can report a conflicting priority, a decision that is difficult to implement, or a lack of information.
The manager sets the stage for this feedback by thanking the person, rephrasing their point, and explaining what they can do. They must also clearly state what cannot change and why.
Bottom-up feedback does not automatically mean challenging every decision. It provides insight into the reality on the ground and allows for necessary adjustments.
A meaningful conversation doesn't need to be perfectly worded. It needs a specific fact, a clear intention, and an appropriate setting.
Feedback that touches on punctuality, quality, attitude, and independence can be difficult to address. Choose the most important topic. Save the others for a separate discussion.
The "sandwich" feedback method can make the message unclear. To understand its limitations and alternatives, visit the page dedicated to "sandwich method".
Reflecting on a behavior should not lead to a judgment about the person. Focus on the facts and the impact it had.
Without follow-up, the manager won't know whether the discussion was understood and put into practice. Plan an observable next step.
The content of the feedback varies depending on what you’re trying to improve. A conversation about a deliverable isn’t conducted the same way as a discussion about behavior or a decision.
Stay true to the expectations defined at the outset. Describe what meets the need, what is missing, and the impact on the rest of the project.
Example: "The memo accurately reflects the decisions that were made. However, it does not include the people responsible for each action or the dates. The team is not yet able to track progress. Please add this information before the final version is shared."
In this way, the manager avoids commenting on the person or their level of commitment. Instead, they link the feedback to the expected quality of the work.
A behavior often relates to cooperation, communication, or attitude. It may be more subtle to pick up on. The manager should describe a specific, recognizable situation and avoid drawing general conclusions.
Example: "During the last two meetings, you responded before people had finished speaking. Several people were unable to finish their points. Let them finish their thoughts before you respond."
The wording focuses on what happened. It does not turn a habit into a personality flaw.
An initiative may produce an imperfect result while still demonstrating a useful capability. Feedback should acknowledge the person’s willingness to take responsibility and specify what needs to be adjusted.
Example: "You proposed a new division of tasks without waiting for the next committee meeting. The idea helped get the project back on track, but two people hadn't been informed. Next time, let the team know before changing the division of tasks."
In this way, the manager avoids discouraging initiative while maintaining a framework for coordination.
Feedback on a decision should distinguish between the decision itself and the way it was explained. A decision may be difficult to accept even if it was not the wrong one.
Ask yourself whether the problem stems from a lack of information, a delay, a decision, or a communication issue. This distinction makes feedback more precise and prevents you from challenging the entire decision when it’s only the framing of the decision that’s problematic.
Upward feedback should link a situation to its impact on work. Describe what you observed, then ask what might help the team.
Example: "Priorities have changed twice this week without any explicit criteria for deciding which to choose. The team has started several tasks without knowing which ones to finish. Could we set the top priority at the beginning of each week?"
Feedback remains professional when it focuses on working conditions rather than on the person’s worth.
A person may dispute the described fact, the stated impact, or the request made. This reaction does not necessarily mean that the person is refusing to engage in any discussion. It may indicate a disagreement, a missing context, or a different perception.
Start by distinguishing between what is observable and what is based on your interpretation. If you say , “You sent the document on Thursday instead of Tuesday, ” the person may explain the delay. If you say , “You never meet deadlines, ” they will first have to defend their reputation.
You can respond: “I’d like to hear more about the context. The point I’d like to address is still the announced deadline and how to notify the team in case of any issues.” This phrasing keeps the conversation on track without shutting it down.
If the impact is up for debate, focus on the concrete consequences. Who had to adjust their work? What decision was delayed? What information was missing? Avoid attributing a reaction to the entire team if you can’t back it up.
If the person acknowledges the problem but does not suggest any next steps, help them come up with a course of action. If the behavior continues despite several discussions, the matter may require a more formal intervention. The manager should then clarify expectations and possible consequences.
A feedback conversation doesn't have to turn into a full-fledged interview. Prepare a main topic and a next step.
Before the exchange, write:
Get right to the point: "I'd like to follow up on this morning's client meeting. I noticed something that could help us ensure the success of the next presentation."
Next, describe what happened. Give them a moment to respond. Paraphrase what you’ve understood, then move on.
If there are several issues, choose the one that has the greatest impact on your work. You can address the others separately. A conversation that covers too many topics can quickly come across as a general negative assessment.
Length does not guarantee quality. A short exchange may be sufficient if the message is clear, the person can respond, and the next steps are clear.
Feedback in management works best when it is specific, direct, and action-oriented. Set the stage, choose the appropriate tone, listen to the response, and follow up on the next steps.
Start with a single recent topic. Describe the situation without judgment. Then ask the other person how they see the next step. The quality of feedback is measured less by the elegance of the phrasing than by the clarity of the conversation and what changes as a result.
Discover all our courses and workshops to address the most critical management and leadership challenges.
Training organisation registered under the number 11755339875. This registration does not imply state approval.
.svg)
.png){kind=small}
.png){kind=small}
