Feedback is only useful when it changes outcomes.

Vague praise and vague criticism feel like communication, but they rarely change behavior. “Great job” does not tell someone what to repeat. “This needs to be better” without a referent leaves people guessing, or defensive. The feedback that actually moves work forward is specific, close to the event, and tied to something the person can control.

That does not mean micromanaging. It means being clear enough that the next attempt is not a lottery.

Be specific and timely

Specific means observable: what was said, built, or decided; what effect it had; what you would like to see differently (or the same) next time. Compare “your communication could improve” with “in yesterday’s review, when X asked for risks, the answer skipped Y. I need that surfaced early so we do not surprise stakeholders.”

Timely means close enough that memory and context are fresh. Waiting for a quarterly review to mention a pattern that showed up in January is how resentment compounds. A short conversation the same week, even ten minutes, often lands better than a formal “feedback session” loaded with months of backlog.

If you only give feedback when you are frustrated, people will associate feedback with danger. If you also notice and name what is working, the channel stays open for the harder conversations.

Tie feedback to standards

Grounding feedback in agreed expectations helps teams improve without unnecessary personal friction. The question is not “are you a good person?” It is “does this meet the bar we said we would hold?”

That requires bars worth naming: definition of done, team norms, security or quality gates, how you run meetings, how you escalate. When those exist in writing or in repeated practice, feedback becomes a calibration exercise, not a character judgment.

When standards are missing, your job is sometimes to create them first, then give feedback. Otherwise you are asking people to read your mind.

Close the loop

Feedback that drives forward ends with clarity about what happens next: a behavior to try, a resource to use, a check-in date, or an explicit “I trust you to adjust; come back if this is unclear.”

If you deliver feedback and disappear, you have added anxiety without support. If you deliver it and follow through (recognizing improvement, or addressing drift), you show that the standard was real.

Done well, feedback is not a ritual. It is how a team learns faster than process documents alone ever could.