The written side of architecture: when to write an RFC versus an ADR, how to compare options with explicit criteria, run a review that reaches a decision, and keep a decision log that new engineers actually read.
As an engineer you make decisions in code. As an architect, most of your leverage comes from decisions that other people implement over months or years: which state library, how micro-frontends communicate, when to adopt Server Components.
Those decisions fail in predictable ways when they're not written down:
Two complementary documents solve this:
| RFC (Request for Comments) | ADR (Architecture Decision Record) | |
|---|---|---|
| When | Before deciding, for significant or cross-team changes | When a decision is made, big or small |
| Purpose | Explore options, gather feedback, build agreement | Record what was decided and why |
| Length | 2–10 pages | Half a page to a page |
| Lifetime | Closes when decided | Permanent; superseded, never edited away |
A typical flow: an RFC proposes and debates, the review reaches a decision, and an ADR records it in the repo next to the code it affects.