Ask any engineering manager what separates the leaders they admire from the ones they don't, and "gives great feedback" comes up almost every time. Yet feedback is one of the most consistently mishandled parts of the job — not because managers don't care, but because most of us were never taught how to do it well.
Feedback fails for predictable reasons: it's vague, it's late, it's wrapped in so much cushioning the message disappears, or it's delivered in a way that puts the other person on the defensive. The good news is that effective feedback is a skill, not a personality trait. It can be learned, practised, and measured.
Why most feedback doesn't change behaviour
The single biggest mistake is confusing feedback with venting. When you wait until you're frustrated, the feedback carries your frustration with it. The engineer hears the emotion, not the content — and spends the conversation managing your mood instead of absorbing the point.
The second mistake is abstraction. "You need to communicate better" gives the recipient nothing to act on. Better at what? With whom? In what situation? Feedback that can't be turned into a specific next action is just a complaint.
The third is timing. Feedback delivered weeks after the fact, in a performance review, lands as an ambush. By then the context is gone and the message feels like a verdict rather than a course-correction.
A model that works: situation, behaviour, impact
The most reliable feedback structure separates what happened from what it meant:
- Situation — anchor it in a specific moment. "In yesterday's design review…"
- Behaviour — describe what you observed, not what you inferred. "…you interrupted Priya twice before she finished her proposal."
- Impact — explain the consequence. "…and she stopped contributing for the rest of the meeting, so we lost her perspective on the caching approach."
Notice what this avoids: it doesn't diagnose character ("you're dismissive"), it doesn't generalise ("you always do this"), and it doesn't guess at intent. It describes observable reality and its effect. That's much harder to argue with — and much easier to act on.
For positive feedback, the same structure works and is just as underused. "Great job" is forgettable. "When you paired with the new hire on the migration instead of just reviewing their PR, they shipped their next three changes without help — that's exactly the kind of leverage I want to see" is something an engineer will remember and repeat.
Make it a habit, not an event
The teams with the healthiest feedback culture don't save it for review season. They normalise small, frequent corrections so that feedback stops feeling like a big deal. A few practices that help:
- Use your 1:1s. Reserve part of every 1:1 for two-way feedback. Ask "what's one thing I could do differently?" and sit with the silence until you get a real answer.
- Separate coaching from evaluation. When someone is learning, they need a coach, not a judge. Be explicit about which mode you're in.
- Close the loop. When someone acts on your feedback, acknowledge it. Nothing reinforces behaviour faster than being seen.
When feedback is hard
Some conversations are genuinely difficult — a talented engineer whose behaviour is hurting the team, or a performance problem that isn't improving. The temptation is to soften the message until it's unrecognisable. Resist it. Clarity is a kindness. People can handle the truth far better than they can handle ambiguity about where they stand.
What they can't handle is feeling disrespected. Deliver hard feedback privately, directly, and with genuine belief that the person can improve. The goal is never to win the conversation — it's to leave the other person with a clear picture of the gap and a real path to closing it.
Feedback is a measurable capability
Giving feedback well is one of the competencies the EMA Competency Framework assesses under People Leadership — precisely because it's a learnable skill that separates effective engineering leaders from the rest. If you can anchor feedback in specific behaviour, tie it to impact, and deliver it with respect and frequency, you've already got one of the highest-leverage habits in management.
Want to know where your leadership judgment stands? Take EMA-I — a scenario-based exam that tests how you'd actually handle situations like these, not whether you can recite a model.