Our median code review time was two days. Developers would start something new, forget the context, and the review became homework. Three changes fixed it. First, nothing above four hundred lines. If it is bigger, split it. Second, the author writes the review guide: what changed, why, where to look. Third, review blocks on the calendar, twice a day, every day. Reviews are meetings you have with code. Treat them like meetings. Two days became four hours and throughput nearly doubled.