Copy the Reasoning, Not the Architecture

"We should use this." "Why?" "Because we used it in a previous life. Also, BigCorp uses it." If you've worked in software for long enough, you've probably been in some version of this meeting. A technical direction is proposed. Someone asks for the reasoning. Instead of a discussion about constraints, trade-offs, failure modes, operational burden, or team capability, the answer is some variation…