Technical leaders who use tradeoff language well do something specific in design conversations: they wait for the moment when two engineers are talking past each other, name the tradeoff both are implicitly optimising for, and ask which tradeoff is right for this context. That intervention — naming, not judging — resets the conversation from argument to analysis.
They also write ADRs that include the condition for reversal. Not “we chose AT5” but “we chose AT5 because team size and operational overhead of distributed auth exceeded the availability benefit at our current scale; if availability SLO drops below 99.9% or team doubles, revisit.” The reversibility condition makes the ADR a living decision rather than a historical artifact.
The best technical leaders use F8 vocabulary publicly. When they name AT5 in an all-hands or a review, they are teaching the vocabulary by modelling it, not by training. Within six months, the engineers around them start using the vocabulary in their own design documents.