# Why Write ADRs - Eli Perkins Synced: [[2023_11_30]] 6:03 AM Last Highlighted: [[2023_07_25]] Tags: [[software]]  ## Highlights [[2023_07_25]] [View Highlight](https://read.readwise.io/read/01h6630ecxsshsb0yyb8ybdjgv) > **ADRs capture the decision at the time it’s being made.** ADRs are the culmination of all those minutes and hours you spent in meetings, on Zoom, in Slack, or jamming through various proof-of-concepts in Xcode. All of the context that’s in your head has a chance to get out into words so that when you’re revisiting the architecture down the road, you can put that context right back into your head. [[2023_07_25]] [View Highlight](https://read.readwise.io/read/01h662xf3n1qwxn3ffv6e2szxv) > Writing ADRs allows for [“decision socialization”](https://www.ozimmer.ch/practices/2020/05/22/ADDefinitionOfDone.html), where your *team* comes to a decision that the *team* is responsible for maintaining, rather than decisions made in isolation. [[2023_07_25]] [View Highlight](https://read.readwise.io/read/01h662wqexa2xteezmwacye793) > ADRs *are* for helping onboard new teammates as they work to understand the codebase and how it has evolved over time