Part IV — The Relationships
How do I operate across the executive system?
The CTO does not operate in isolation. Every structural decision the CTO makes — about platforms, capital, sequencing, and architectural governance — is made within an executive system that has its own priorities, its own logic, and its own pressure points.
Understanding that system is not a political skill. It is part of how the system is operated.
The five relationships covered in this section are not equally weighted and they are not equally difficult. Each one has a different dynamic, a different failure mode, and a different kind of leverage. What they share is this: each one sits at a boundary — between technology and something else: strategy, capital, operations, product, governance.
At every boundary, there is a version of the CTO that is too accommodating and a version that is too rigid. Neither works.
The CTO who is too accommodating becomes a service provider — technically capable, organizationally invisible, structurally reactive. The CTO who is too rigid becomes an obstacle — structurally correct, organizationally isolated, unable to move anything that requires alignment.
The operating posture required is neither. It is the posture of a CTO who understands what each relationship requires, what each one risks, and how to hold structural authority without losing the room.
These are not relationship management techniques. They are structural operating principles — the difference between a CTO who shapes the system and one who is managed by it.