Giving Feedback Like a Coach, Not a Critic
The default setting: critic
Most managers act as critics. They review the work, find the flaws, and point out what went wrong. That approach scales badly and wears down the team's capability over time. When the leader is the final quality filter, the team stops evaluating its own work and waits for corrections. If you want to stop creating that dependency, stop being the sole editor of your team's output.
When someone keeps missing the mark, the critic looks at the employee. The coach looks at the system first, then at themselves. Did they give the right context, the necessary resources, and a workable scope? Blaming the individual without checking the environment skips the leader's main responsibility. Assuming a team member lacks dedication is easier than admitting your onboarding or delegation process is broken.
Why the critic model fails teams under pressure
Where safety and precision matter, the critic model produces defensive teams. People who expect to be judged instead of developed hide mistakes. They optimize for avoiding blame instead of solving hard operational problems, which slows decisions and erodes trust across the organization. A team that conceals errors to dodge a reprimand is a safety risk, which is the whole case for a just culture instead of a blame culture. Teams that can't say it to your face will look for other routes, which is why anonymous feedback channels matter.
Moving to coaching
The best way to give feedback as a leader is to coach. A coach names the gap between current performance and the standard, then works with the employee to close it. The conversation moves from an accounting of what happened to a plan for the next challenge.
A critic says the report was late and the data was wrong. A coach asks what slowed the report down and how the team can check the data faster next time. That small change in phrasing moves the focus from personal failure to process improvement, and it tells the employee you care about their success as much as their grade. Doing it in small, regular doses works better than saving it up; see how daily feedback drives team performance.
Defending the time it takes to grow
Coaching depends on protecting the team's focus. You can't develop people who are drowning in shifting priorities and unmanaged workloads. Leaders who want to keep their top people have to be able to say no while sounding like yes: negotiating scope and holding boundaries without alienating stakeholders. We've written more on why protecting your team from distraction is a leadership job.
Firm boundaries create room for real development. Every time you jump on an unreasonable request or an after-hours message, you teach stakeholders they can bypass your systems. Holding the line on capacity keeps the team from exhausting itself and gives people the bandwidth to act on the feedback they get. Sustainable pacing is management's responsibility, because burnout is a leadership problem, not a personal failure. Coaching builds long-term capability, and it only survives when the leader defends the time learning requires. Our leadership workshops give managers practice running these conversations before they need them.
Kestryl Edge works with leaders and teams to put ideas like this into practice. See how we work at Kestryl Edge.
Dan Korus, Kestryl Edge founder, publishes The Updraft, a weekly newsletter on leadership, trust, and how teams actually perform. Subscribe here.