I do like code reviews.
If my customer and teams let me spend time on it, I’m able to see issues in automation workflows, code quality and knowledge gaps in the teams or workflow issues in general.

• You can quickly see in code reviews if automated checks catched typos, code style or linting issues.
• You can find out the code quality level in the team and if your team members have equal knowledge or not (which can affect effectiveness of the team if too different)
• You can find workflow issues such as no clear UX/design requirements leading to unclear code implementations
• Not implemented edge-cases because it’s unclear who’s responsible in thinking about them (PO?, Dev?)
• Performance issues, Accessibility issues and others because the developers didn’t think or test when writing the code.

💡 The catch is, you need to spend time and thoughts into proper code reviews. Only then the world of seeing possible improvements opens up for you. Check out the code, not only look at it, open dev tools, use a screenreader and so on.

💌 If you need someone looking into your engineering department to improve the happiness of your people and effectiveness or work, send me a message. I still have time this year.