Let me add here something that was maybe not mentioned clearly in the comments: Time is an important ingredient of good code reviews. If the team members have

Let me add here something that was maybe not mentioned clearly in the comments: Time is an important ingredient of good code reviews. If the team members have their capacity allocated fully then there is no time to do proper code review. Thus code review is ignored as much as possible or it is seen as time lost from the project. Will also transfom the code review into an action that will be superficial. Before fixing everything else you must first understand if the team has time to do code review. That means that the expectation is not that they should produce the same output but also do code reviews. If this is the case then the team does not have time for Code Review. And only after there is time for this, you should go into fixing/improving the process.