Giving and Receiving Feedback as a Leader

Feedback fails most often not because it's wrong, but because of how and when it's delivered. Vague praise or criticism ("great job" or "this needs work") gives someone nothing to act on. Specific feedback tied to a concrete example — what happened, its effect, and what a better version might look like — is far more useful and far less likely to be received as a personal attack. Timing matters almost as much as content. Feedback given days or weeks after the fact loses most of its power, because the person has moved on and the context has faded. Close-to-the-moment feedback, delivered privately for anything critical, tends to land better and change behavior faster. As a leader, framing feedback around growth rather than judgment — "here's what would make this even stronger" rather than "this is wrong" — changes how it's received without softening the substance. People can tell the difference between feedback meant to help them improve and feedback meant to make the giver feel superior. Receiving feedback well is its own skill, and arguably a harder one. The instinct to explain, justify, or defend in the moment usually shuts down the conversation before you've actually absorbed what was said. A simple "thank you, let me think about that" buys space to actually process the input instead of reacting to it. Leaders who ask for feedback regularly, and visibly act on some of it, build teams where feedback flows freely in both directions — which tends to catch small problems long before they become big ones.