What do you do if you're a software engineer struggling to assert your ideas during code reviews?

2 Speak Confidently

Confidence in your speech is key when asserting your ideas. Practice articulating your thoughts clearly and concisely. If you're naturally introverted or anxious, consider rehearsing your points beforehand. During the review, speak at a measured pace and maintain eye contact with your peers. This non-verbal communication can reinforce the strength of your convictions and help ensure that your ideas are taken seriously.

4 Be Persuasive

Being persuasive involves more than just having good ideas; it's about how you sell them to your team. Use logic and evidence to make your case, and relate your suggestions to the team's goals. For example, if you advocate for a new testing framework, explain how it could speed up development cycles or improve code reliability. By aligning your ideas with shared objectives, you increase the chances of them being embraced.

5 Seek Allies

Sometimes, having an ally in the room can help amplify your voice. If you know someone on the team shares your viewpoint, discuss your ideas with them beforehand. They can provide support during the review, making it more likely that your ideas will gain traction. Additionally, having multiple people articulate the same perspective can signal to others that the idea is worth considering.

6 Follow Up

After the code review, follow up on the discussion. If your ideas were accepted, work diligently to implement them and show their value. If they were not, seek feedback to understand why. Use this as a learning opportunity to refine your approach for next time. Persistence and a willingness to adapt are crucial in ensuring that your ideas will eventually find their place in future projects.

7 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?