Tradeoff Vocabulary
Why this chapter matters
Architects need precise language for disagreement. Without shared vocabulary, teams argue through preferences: "cleaner", "modern", "simple", "scalable", "fast". Those words hide the real tradeoff.
Core tradeoff dimensions
| Dimension | Useful question |
|---|---|
| reversibility | How expensive is it to change this later? |
| coupling | Which teams, modules, services, or release trains become linked? |
| cohesion | Does the design keep related behavior together? |
| latency | Which user-visible step becomes slower or faster? |
| throughput | Can the system handle more users, data, or interactions? |
| complexity | Who pays the mental and operational cost? |
| blast radius | What breaks if this fails? |
| optionality | Does this keep future choices open or close them? |
| governance | Who can change this safely? |
| cost | Which compute, bandwidth, vendor, and maintenance costs grow? |
Tradeoff phrases architects should use
| Weak phrase | Stronger phrase |
|---|---|
| This is cleaner. | This reduces local implementation complexity but increases shared package coupling. |
| This scales better. | This handles independent team release pressure at the cost of duplicated runtime assets. |
| This is faster. | This improves first paint by shifting compute to the server and adds hydration risk. |
| This is simpler. | This is simpler for feature teams but adds platform ownership requirements. |
| This is future-proof. | This preserves optionality for route-level rendering changes. |
Tradeoff map
Decision conversation pattern
Use this pattern in reviews:
- Name the outcome.
- Name the constraint.
- Name the accepted cost.
- Name the mitigation.
- Name the review trigger.
Example:
We are choosing cached SSR for this route to improve first content for anonymous users. We accept higher server/cache complexity. We mitigate it with explicit cache keys, RUM monitoring, and a rollback to static fallback if origin latency regresses.
Review checklist
- Is the tradeoff stated in concrete dimensions?
- Is the accepted cost explicit?
- Is the cost assigned to a team or system owner?
- Is the mitigation credible?
- Is the review trigger measurable?
Exercises
- Rewrite five "best practice" statements as tradeoff statements.
- Pick a current architecture decision and name its blast radius.
- Place three team decisions on the quadrant chart.
Source lens
Use this vocabulary across ADRs, system-design answers, capstone reviews, and architecture portfolio narratives.