A CTO is in three conversations in the same day. The first is with the board: should the company rebuild the platform on a new architecture, or invest in the existing one? The second is with the VP of Engineering: which of two senior engineers should be promoted to principal? The third is with the team: the payment service is down, and the team cannot agree on the root cause.
These are not three different kinds of problems. They are the same problem at three different altitudes. Each requires the same mental frameworks — but applied at a different level of abstraction, with different stakeholders, and with different consequences if the reasoning is wrong.
The CTO Decision Stack is not a title problem — it is a problem of applying technical depth at strategic altitude. The engineer who can do this is the one who earns the CTO role, or the principal role, or the architect role, before they have the title.
This chapter shows how the nine frameworks apply simultaneously at the CTO level — not sequentially as study material, but in parallel, as the lens through which every decision is evaluated.