To tactfully address a team member consistently brushing off code review feedback, start by having a private, respectful conversation. Emphasize the importance of code reviews as a learning and quality improvement tool, not a critique of their skills. Explain how feedback helps maintain code consistency, prevent bugs, and ensure team collaboration. Encourage them to view it as a growth opportunity and a chance to improve the project’s overall success. Ask if there are any barriers to implementing the feedback and offer support. Reinforce a culture of openness and learning, where everyone benefits from shared insights.

When a team member disregards code review feedback, I start by emphasizing the value of code reviews during a team meeting—highlighting their role in quality assurance and knowledge sharing. Setting clear expectations for how feedback should be addressed is key, along with a follow-up process to ensure changes are made. Offering one-on-one mentorship or pairing sessions also helps the team member better understand the feedback.

Escalate. It's not your job to ensure that feedback is incorporated, it's theirs. If they're not doing that, their management needs to know. We often fear escalation because we treat it as about winning. It's not, it's about clarity. If you think your feedback has value, and the other person doesn't, you might talk to them, but the reason you have a code review process is that management expects it'll result in better code, and it's not.