Decision Records are a pivotal part of successful software design. They are key to spreading the understanding of why decisions were made to all stakeholders. Without access to the understanding and reasoning behind a decision you risk wasting time and money on revisiting decisions and even making changes that cause costly problems that had been avoided in the original design.

Discover:
– how to avoid the pain and cost caused by not understanding past decisions
– which decisions you should be documenting in a decision record
– how to effectively construct ADRs (Architecture Decision Records) that can be used by all those that need them
– where and how to store ADRs and other decision records
– how to encourage a decision recording culture in your team and company

Once you get your decision records working for you, you’ll never want to go back.