Use ADRs for Thinking, Not Just Recording

Use ADRs for Thinking, Not Just Recording

Begin writing the ADR at the start of the decision-making process, not as an afterthought for documentation. Use its structure collaboratively as a tool to guide team discussion, explore options, and identify necessary research. The document becomes a guide for...
Use ADRs for Thinking, Not Just Recording

Guide Decisions, Do Not Dictate Solutions

Instead of providing direct answers, guide teams by asking probing questions and suggesting alternative perspectives. This fosters their decision-making skills and ownership without undermining their autonomy. The goal is to enable, not to command. Examples When a...
Use ADRs for Thinking, Not Just Recording

Treat Decisions as Immutable Historical Records

Document each decision as a distinct, immutable record, such as an Architectural Decision Record (ADR). A subsequent choice that alters a previous one should be a new, separate record that explicitly supersedes the original. This maintains a clear historical log and...
Use ADRs for Thinking, Not Just Recording

Be Explicit About Decision-Making Authority

Clearly communicate the decision-making process being used for any given choice. If a leader has already made a decision, they should state it directly rather than creating a false pretense of seeking input. This respects people's time and avoids breeding...