Trade-off Surface
The set of achievable combinations of competing qualities, on which improving one attribute necessarily costs another.
Architecture has no best solutions, only positions on a surface where the axes pull against each other. Naming the surface is what converts an argument about preferences into a decision about priorities.
The recurring oppositions: consistency against availability and latency; performance against cost; flexibility against simplicity; security against usability; delivery speed against maintainability; isolation against utilisation.
Two properties of the surface that experienced practitioners use:
Some positions are strictly worse than others. A design that is slower and more expensive and more complex is not a trade-off — it is a mistake. A surprising amount of design review is identifying these rather than weighing genuine trade-offs.
The surface can sometimes be moved rather than traversed. Caching improves latency and cost together; a passkey is both more secure and faster than a password with TOTP; a smaller batch size improves both speed and safety. The highest-value engineering work is often the move that relaxes the constraint rather than the choice along it, and looking for one before accepting a trade-off is a habit worth having.
The discipline that keeps the conversation honest: state what is being given up in the audience's units, and say who bears the cost — users, operations, finance, or a future team.