Feedback Is the Most Underused Lever in Your Building

If you asked most leaders to rank the instructional practices with the strongest evidence behind them, few would guess how consistently feedback tops the list. It doesn't have the appeal of a new curriculum or the visibility of a technology rollout. It's just people telling other people, specifically and promptly, how what they did compares to what was needed — and it's one of the most reliably powerful levers available, precisely because it's so rarely done well.

Why feedback underperforms its potential so often

The gap isn't usually a lack of feedback. Most organizations are drowning in it — comments on work, notes after observations, responses to emails. The gap is in the quality of what gets delivered, and the quality failures tend to cluster around a few recognizable patterns.

Feedback that's too vague to act on. "Good job" and "this needs work" both fail the same test: neither tells the recipient what to do differently next time. Feedback that doesn't specify the gap between current performance and the target performance isn't really feedback — it's a verdict.

Feedback that arrives too late to matter. The value of feedback decays quickly. A comment on work from three weeks ago competes with everything that's happened since, and by the time it arrives, the person receiving it may not even remember the reasoning behind the choice being critiqued.

Feedback aimed at the person instead of the work. "You're not a strong communicator" invites defensiveness because it's an identity claim. "This message buried the ask in the third paragraph" invites a fix, because it's about the artifact, not the person. The distinction sounds small. In practice, it's the difference between feedback that gets acted on and feedback that gets absorbed as a wound.

The three questions good feedback answers

A useful frame treats effective feedback as an answer to three questions, in order: Where am I going? (what does success actually look like here), How am I doing? (specifically, relative to that target, not relative to a vague sense of effort), and Where to next? (the actual, concrete next step). Feedback that only answers the middle question — a rating, a grade, a general impression — leaves the recipient without a path forward, which is exactly the part that determines whether the feedback changes anything.

Feedback is also a two-way tool

Leaders often think of feedback as something delivered downward — from leader to team member, from teacher to student. The practice loses most of its power in that framing. The same three questions apply just as usefully upward: does a team member have a clear channel to tell a leader where a system, a decision, or a piece of guidance missed the mark? Organizations with strong feedback cultures build that channel deliberately, because leaders are just as capable of misjudging their own performance as anyone else, and just as unlikely to find out unless someone tells them clearly and specifically.

A practical standard

A workable test for whether feedback is likely to land: could the person receiving it, immediately after hearing it, describe one specific thing they'll do differently next time? If the answer is no, the feedback was probably too vague, too delayed, or too aimed at identity rather than action, regardless of how well-intentioned it was.

What this means for a leader's calendar

If feedback is genuinely one of the highest-leverage tools available, it deserves the calendar protection that high-leverage work usually doesn't get. That means treating a short, specific, prompt piece of feedback as more valuable than a longer, delayed, comprehensive one — frequency and speed usually beat thoroughness, because feedback that arrives while the work is still fresh gets used, and feedback that arrives once a year in a formal review mostly gets filed.

The leaders who build strongest cultures of improvement aren't necessarily the ones with the most rigorous evaluation systems. They're the ones who've made specific, prompt, growth-oriented feedback an ordinary part of how the team talks to each other — not an event, but a habit.

An example of the shift in practice

Consider the difference between two responses to the same piece of work. The first: 'This is solid, nice work.' The second: 'The opening paragraph clearly states the problem, which makes the rest easy to follow — the one thing I'd change is moving the recommendation earlier, since right now a reader has to get through three paragraphs of context before finding out what you're actually proposing.' Both are positive in tone. Only the second gives the recipient anything to act on the next time, because it answers all three of the questions good feedback needs to answer — what's working, specifically why, and what the next concrete move would be. The first costs less time to deliver and produces almost no change in future work. The second costs slightly more time and is far more likely to actually shift what happens next, which is the entire point of giving feedback at all.

A final habit worth building

One small practice makes feedback more likely to stick regardless of how well it was delivered: asking the recipient to restate, in their own words, what they're going to do differently. This isn't about testing them — it's about catching the gap, which shows up surprisingly often, between what was said and what was actually heard, while there's still time to close it before the next attempt happens.