Building a culture of architectural decision records (ADRs)

our team recently adopted architectural decision records (adrs), and it's been surprisingly transformative. initially, there was some pushback and skepticism, but now it's becoming a natural part of our development process. getting buy-in meant starting with a lightweight template and emphasizing that it's for *future us* to understand 'why' decisions were made, not just 'what' was done. we integrated it into our pr process, making a simple adr a requirement for anything deemed 'architecturally significant.' the trick was defining what qualifies as architectural; we settled on anything that involves significant trade-offs, introduces new technologies, or changes core system behaviors. it's reduced endless debates, helped onboard new engineers, and provided a clear historical context for past choices. for those who've also implemented adrs, what were your biggest wins or challenges? how do you keep them lightweight and useful without becoming another bureaucratic hurdle? any tips for fostering a culture where adrs are seen as valuable documentation rather than just more paperwork?