The best solution for speeding up code reviews is to not do them at all.<p>Have tests, have a ci system and pipelines, empower the team to deploy and rollback (especially non-technical folks). Any green build should be deployable by your PM or whoever. If your system does not support frequent change and encourage shared ownership of the code then fix your system.<p>If you really want to get “drastic” encourage or mandate your programmers to pair and encourage frequent pair rotation.<p>We run into this over and over again with clients who cling to the PR process and inevitable we burry them in PR and progress grinds to a halt compared to other projects that get on board with above.