Technical decisions fade when they're undocumented, unfindable, or made without involving the right people. The key is matching documentation weight to decision importance: verbal agreement for small reversible choices, written summaries for multi-person decisions, ADRs for architecture-limiting choices, and RFCs for
Table of contents
Why Decisions Don’t StickMatch documentation to the decision’s weightADRs work because they’re simpleRFCs fail when they’re theatreInvolvement determines whether decisions stickDecisions need visible attention, not rulesKeep decisions close to the codeShared understanding, not bureaucracySort: