Introducing Architecture Decision Records (ADRs) to a team takes time and dedicated practice. In our experience, ADRs help teams improve their design practices and eventually learn how to distribute design authority.
Teams who use mob programming can improve the effectiveness of their mobs by reflecting on how the mob naturally operates and harvesting patterns that can be intentionally applied in the future.
Teams that plan to redesign later nearly always face business, technical, and social forces--headwinds that prevent them from initiating a redesign effort.
Running scientific experiments is an inexpensive and effective way to resolve team disagreements and drive process improvements. Also, pair programming is an absolute super power (and we learned this by running an experiment).