Post Twelve Tradeoff Principles Where Your Team Argues
The Tradeoff Principles for CTOs, condensed to one page
Companion to The Code Takes Care of Itself · Updated 2026-09-29
The Tradeoff Principles for CTOs condense “Every Real Decision Gives Something Up” into the version that fits on a wall. Print this page and post it where your leadership team argues. The principles aren’t complicated; the middle of a heated architecture debate is simply when everyone forgets them.
- There are no solutions, only tradeoffs. Every decision buys one future by giving up another. If nobody can name what you’re giving up, you haven’t found the tradeoff yet, and you don’t understand the decision.
- The longest arguments run between two people who are both right. When a debate won’t converge, stop asking who’s correct and ask what each side is optimizing. Facts end arguments; unstated goals extend them indefinitely.
- Every seat optimizes something different, and none is wrong. The CFO optimizes capital, the CTO optionality, the CISO tail risk, engineering its own productivity, support simplicity, customers their outcomes, and compliance its evidence. Price your proposal in the other seat’s currency or expect to hold the meeting again.
- Ask which failure you can afford. The best architecture is unknowable; the affordable failure is discoverable. Choose your weaknesses deliberately, in writing, while the choice is still cheap.
- The real cost of anything is what you gave up to get it. Opportunity cost appears on no dashboard, no diagram, no balance sheet. See the missing line item anyway.
- Constraints decide, so name the binding one. Time, money, talent, attention, trust, patience: only one usually binds this quarter. Optimizing anywhere else wastes the effort.
- Write a ledger, because a verdict invites relitigation. A verdict says why the choice was good. A ledger says what you gained, what you gave up, who pays, and what would reverse it, and it closes the argument honestly.
- Assumptions expire, so schedule the re-examination. A decision that looks wrong two years later was either wrong, or right about a world that ended. Different failures, different lessons. A reversal trigger with a named owner is how you tell them apart.
- Whoever bears the cost should hear it priced out loud. The decisions that do the most damage are the ones where the beneficiary and the bill-payer are different people and nobody said so. Say so.
- Uncertainty tells you how big to make the bet. Decide reversibly where reversal is cheap, decisively where it isn’t, and size every bet so that being wrong is survivable. Deferral without an owner and a trigger is Decision Debt.
- Stated tradeoffs compound into trust. A board told the price before the bill arrives extends credit; a team told “best practice” when the truth was “we chose your pain over their delay” withdraws it. Everyone hears the difference.
- Engineering maturity isn’t knowing the right answers. It’s knowing that every answer carries a bill someone eventually pays. The best CTOs don’t eliminate tradeoffs; they make them deliberately, transparently, and in line with what the organization is trying to become.
