Giving tough feedback is one of the most important and most avoided responsibilities of an engineering manager. Done well, it accelerates growth and builds trust. Done poorly — or not at all — it allows problems to compound and signals that you do not care enough to be honest. This guide equips you with the skills to have these conversations effectively.
Why Tough Feedback Matters
Avoiding difficult feedback is one of the most common management failures. It feels compassionate in the moment — you do not want to hurt someone's feelings or damage the relationship. But in reality, withholding feedback that could help someone improve is not kindness; it is cowardice that prioritises your comfort over their growth.
Engineers who do not receive honest feedback are denied the opportunity to improve. They may be blindsided at performance review time, passed over for promotions without understanding why, or left to develop habits that limit their career. The most respected managers are those who care enough to be direct.
Tough feedback also serves the team. When one person's behaviour is affecting team dynamics — dominating discussions, writing careless code, missing commitments — addressing it privately prevents the rest of the team from becoming frustrated and disengaged. Your team watches how you handle these situations, and your willingness to act shapes their trust in your leadership.
Preparing for the Conversation
Never deliver tough feedback off the cuff. Preparation is what separates a productive conversation from one that causes harm. Start by clarifying the specific behaviour you want to address, the impact it is having, and the change you want to see.
Use the Situation-Behaviour-Impact (SBI) framework to structure your feedback. 'In yesterday's sprint planning (situation), you dismissed Sarah's estimate without explaining your reasoning (behaviour), which made her reluctant to contribute for the rest of the meeting (impact).' This specificity makes the feedback concrete and actionable rather than vague and personal.
Anticipate the engineer's likely response. Will they be defensive? Emotional? Will they disagree with your assessment? Prepare for each possibility so you can respond calmly and redirect the conversation productively. If you are nervous about the conversation, rehearse it — with a trusted peer, your own manager, or even alone. The goal is to deliver the feedback clearly and kindly, not to perform perfectly.
Delivering the Feedback
Choose the right moment. Tough feedback should be delivered in a private, one-on-one setting — never in front of the team. Schedule enough time for a real conversation, not a five-minute drive-by. Avoid delivering feedback when either of you is upset, rushed, or distracted.
Lead with care. Start by expressing your commitment to the engineer's success: 'I want to share some feedback because I care about your growth and I think this is important.' This framing sets the tone for a developmental conversation rather than a punitive one.
Be direct and specific. State the feedback clearly using the SBI framework you prepared. Resist the temptation to soften the message with excessive praise (the 'feedback sandwich' often dilutes the core message and feels manipulative). After delivering the feedback, pause and let the engineer respond. Do not rush to fill the silence.
Listen to their perspective. They may have context you lack, or they may need time to process. If they become defensive, do not match their energy — stay calm and redirect: 'I understand this is hard to hear. I am sharing this because I believe you can address it, and I want to help.' If they disagree with your assessment, acknowledge their perspective while maintaining your own: 'I hear your point, and I would like you to consider mine as well.'
Following Up After Tough Feedback
The conversation does not end when the meeting does. Follow up with a brief written summary of what was discussed and any agreed actions. This ensures alignment and creates a reference point for future conversations.
Check in during your next one-on-one. Ask how the engineer has been processing the feedback and whether they need any support. Acknowledge any improvements you have observed — reinforcing positive change is as important as flagging the original issue.
If the behaviour persists, have the conversation again with increased directness. Reference the previous discussion: 'We talked about this two weeks ago, and I have noticed the same pattern continuing. Can you help me understand what is making it difficult to change?' Persistent issues may require a more formal approach, but always give the engineer a genuine opportunity to respond to informal feedback first.
Building a Feedback Culture on Your Team
The best teams do not rely solely on the manager for feedback — they give and receive feedback directly from each other. Your job is to model this behaviour and create the conditions for it to thrive.
Ask for feedback on your own performance regularly and visibly. 'What is one thing I could do differently to support you better?' When someone gives you constructive feedback, thank them genuinely and act on it. This demonstrates that feedback is valued, not punished.
Create structured opportunities for peer feedback. Retrospectives, code review discussions, and quarterly peer reviews all provide channels for constructive input. Normalise the language of feedback so it becomes part of how the team communicates, not something reserved for performance review season.
Key Takeaways
- Avoiding tough feedback is not kindness — it denies people the information they need to grow
- Prepare using the Situation-Behaviour-Impact framework to make feedback specific and actionable
- Deliver feedback privately, lead with care, be direct, and then listen
- Follow up with written summaries, check-ins, and recognition of improvement
- Build a team culture where feedback flows in all directions, not just from manager to report
Frequently Asked Questions
- How do I give tough feedback to someone more senior or experienced than me?
- The same principles apply, but you may need to adjust your framing. Acknowledge their experience while being clear about the behaviour and its impact. 'I know you have more experience with distributed systems than I do, and I value your expertise. The concern I want to raise is about how the architecture discussion played out yesterday, not about the technical direction itself.' Senior engineers generally respect directness more than hedging, so do not let the seniority gap dilute your message.
- What if the engineer gets emotional during the conversation?
- This is normal and does not mean you have done something wrong. Give them space to process — offer a pause if needed. Say something like 'I can see this is upsetting, and that is completely understandable. Would you like to take a few minutes, or would you prefer we continue?' Do not withdraw the feedback because of an emotional reaction, but do adjust the pace and tone of the conversation. If the emotion is overwhelming, it is perfectly acceptable to schedule a follow-up conversation after they have had time to process.
- How often should I give tough feedback versus positive feedback?
- There is no universal ratio, but a useful guideline is that positive feedback should significantly outweigh corrective feedback in your overall communication. This is not because you should manufacture compliments — it is because there are usually many more things going right than going wrong, and recognising those things builds the trust that makes tough feedback land effectively. If you find that most of your feedback is negative, examine whether your expectations are unreasonable or whether you have fallen into the habit of noticing only problems.
Get Feedback Conversation Templates
Download structured templates for one-on-ones, performance conversations, and feedback delivery designed for engineering managers.
Learn More