Trade-off Framing
Presenting a decision as a choice between named costs rather than as a search for a best option, so the audience can exercise the judgement that is properly theirs.
The most common failure in architecture communication is presenting a recommendation as though it were free. Every architectural choice gives something up, and an audience that is not told what will discover it later — usually at the moment it hurts, and with the credibility cost that follows.
The framing that works: "we can have A or B, not both. A costs us X; B costs us Y. Here is which I recommend and why."
What makes it land:
Name what is being given up, in the audience's units. "Strong consistency means every write waits 80 milliseconds and the second region becomes a dependency of the write path" is concrete. "There is a consistency trade-off" is not.
Say who bears the cost — users, the operations team, the finance line, a future team. Trade-offs are frequently between different people's interests, and making that visible is what allows the right person to decide.
Distinguish reversible from irreversible. A cheaply reversible choice does not warrant the same scrutiny as a data model that will hold years of records, and saying so shortens the conversation.
Give a recommendation. An analysis without one hands the work back to the audience, who have less information than you do.