Shared Vocabulary & Options-Plus-Recommendation

Beyond naming the tradeoff itself, an architect needs two complementary communication tools: a shared vocabulary calibrated to the audience, and a way of presenting choices that invites alignment rather than passive acceptance.

Calibrating Vocabulary to the Audience

Concepts like context engineering, retrieval, and model tiers give technical stakeholders precise mental models -- use them directly with an engineering counterpart. For non-technical audiences, translate the same concepts into outcomes and costs: not "we're adding a reranking step," but "this adds a small delay to improve answer accuracy."

Options With a Recommendation

Offer options with a recommendation, not just a verdict: "here are two designs, here's the tradeoff, here's what I recommend and why." This structure does two things a single verdict cannot:

1. It shows the stakeholder the alternative that was considered and rejected, and why
2. It gives the stakeholder a genuine decision point, not just a rubber stamp

Translating for a Non-Technical Executive

The best way to communicate a model-tier tradeoff to a non-technical executive is to translate it into outcome, cost, and risk, and give a recommendation with the tradeoff named -- not to show raw token-cost formulas, tell them to trust engineering, or avoid mentioning tradeoffs at all. Avoiding tradeoffs to "keep it simple" is not simplification; it hides the decision the stakeholder is entitled to weigh in on.