The Art of Giving Feedback That Actually Changes Behaviour

Most feedback in manufacturing environments is either too soft or too blunt. Too soft, and the message does not land; the person walks away thinking they are doing fine when they are not. Too blunt, and the message lands but damages the relationship; the person hears the criticism but becomes defensive and disengaged.

I have given thousands of pieces of feedback over 23 years. I have watched leaders give feedback that transformed performance and feedback that destroyed morale. The difference is never the content. It is almost always the method, structure, timing, framing, and follow-through.

The most important reframe I ever made about feedback is this: the goal is not to communicate an observation. The goal is to produce a change in behavior. These are not the same thing.

When you evaluate your feedback, ask yourself: “Did I say it clearly?” You are measuring the wrong thing. The right question is: did it produce a change? If you gave clear, well-intentioned feedback and the behavior did not change, something in the method failed, regardless of how clearly you communicated.

This reframe shifts accountability from the receiver to the sender. The feedback giver is responsible not just for the content but for the impact. That is a harder standard, but it is the only one that produces results.

Feedback given too long after the event loses its connection to the behavior. Feedback given at the wrong moment, when the person is stressed, in front of colleagues, or at the end of a difficult shift, activates defensiveness before the message has a chance to land.

The ideal window for corrective feedback is within 24 hours of the event, in private, when neither party is in an elevated emotional state. For positive feedback, the window is immediate, in-the-moment, specific, and visible.

In my experience, most feedback failures are timing failures. The leader waits for a formal review to address an ongoing behaviour, delivers it under pressure, or gives it in a group setting that triggers embarrassment. None of these conditions are favourable to the behaviour change the feedback is supposed to produce.

Over the years I have refined a feedback structure that works consistently in manufacturing environments. It has 4 components:

• Observation: State specifically what you saw or heard. Not an interpretation. Not a judgement. The observable fact. “In this morning’s safety briefing, I noticed you did not address the near-miss from yesterday’s afternoon shift.”
• Impact: Explain the consequences of the behavior on the team, the process, safety, or quality. “When near-misses are not discussed in the briefing, the team does not have the information to prevent a repeat incident.”
• Expectation: State clearly what the expected behavior is. Not what you hope they might consider doing. What the standard is. “Every near-miss reported in the previous 24 hours must be addressed in the morning briefing.”
• Support: Ask what support they need to meet the expectation. “What would help you make sure this is covered consistently?”

This structure removes ambiguity, connects the behavior to consequences, and closes with a question that invites the person into the solution rather than positioning them as the problem.

Many technical leaders in manufacturing are comfortable giving corrective feedback but are uncomfortable giving positive feedback. They treat praise as unnecessary or even something soft that risks making people complacent.

This is a costly mistake. Positive feedback serves multiple functions that corrective feedback cannot: it identifies and reinforces the specific behaviors you want to see more of; it builds the psychological safety that makes corrective feedback more receivable; and it signals to the team that the leader notices good performance, not just gaps.

The rule I use: for every piece of corrective feedback, there should be at least three pieces of specific, genuine positive feedback in the same period. Not generic praise. Specific recognition of a specific action. “The way you managed that changeover this morning, pre-staging the tooling the previous evening, cut fifteen minutes off our setup time. That is exactly the kind of forward thinking we need more of.”

Feedback without follow-through is just venting. The most effective feedback loop has 3 stages:

• the feedback conversation
• a specific commitment about what will change
• and a follow-up observation.

The follow-up is the most frequently skipped step. Leaders give the feedback, the person agrees to change, and two weeks later, nobody has checked whether the change happened. The person learns that the feedback was not serious enough to track. The behavior returns.

Schedule the follow-up at the end of the feedback conversation. “I will check in with you on this in 10 days. I want to see how it is going.” That simple commitment changes the nature of the feedback from a one-off comment to a structured development interaction.

If you have given clear, well-structured feedback multiple times and the behavior has not changed, the problem is no longer a feedback problem. It is a performance management problem or a fit problem, and it needs to be addressed through a different process.

Persisting with feedback when feedback has failed is a kindness to no one, not to the leader, not to the team, and not to the person whose development is being poorly served by a process that is not working.

Feedback is the most direct tool a leader has for developing their team. Used well, it accelerates performance, builds trust, and creates a culture where improvement is the norm.

Used poorly, it damages relationships, entrenches defensiveness, and produces the opposite of its intended effect.

Master the method. The content will follow.