That's it! Just replace let! with let_it_be. That's equal to the before_all approach but requires less refactoring.

Refactor ruthlessly. Rewrite bravely.

Refactoring at scale is challenging and a significant investment, so communicating the progress is important both from a business perspective but also as a motivational effect to developers. In this case we used a combination of complexity trend visualizations and Code Health Metric as shown in the preceding example.