How much code review you need is going to vary based on the kind of change. When my team has a large design decision, we anticipate that we&#x27;re going to have to create some exploratory code that won&#x27;t ever reach production. We review &quot;spike&quot; pull requests--maybe several generations, depending on the scope of the change. And if needed we have on and offline discussions about our alternative, the tradeoffs, etc.<p>I think this works a lot better than trying to impose design reviews on every change. Most changes shouldn&#x27;t require this kind of scrutiny; you don&#x27;t want to slow down 95% of code reviews for the sake of the difficult 5%.