Two Registers
A capability a technical career builds too well — held in permanent, deliberate tension for the rest of your career.
Every other domain in this framework describes a capability a technical career fails to build. This one describes a capability a technical career builds too well, and then asks the executive to hold in permanent, deliberate tension for the rest of their career.
The technology executive has to operate simultaneously in two registers most people, reasonably, treat as mutually exclusive. The first is strategic enterprise leadership — direction, governance, influence, shaping what the organisation does. The second is sufficient technical grounding to personally know when something is actually true. Not mastery. Not depth across everything. Enough genuine engagement with technical reality to tell the difference between a sound answer and a confident one.
The two failure modes
- Lose the first register and you become an operational manager with a senior title: competent, busy, and invisible at the level where the role is actually judged.
- Lose the second and you become something worse: a strategic figurehead, present in every room and absent from the substance of all of them, dependent entirely on other people to tell you what is true in the one domain you are supposed to lead.
Neither failure is dramatic. Both are slow drifts, in opposite directions, that the executive rarely notices until the cost arrives.
The inversion at the heart of this domain is that the very depth of technical mastery a successful technologist brings to the role is what makes both drifts so easy — deep enough to be pulled toward the comfort of technical detail, credentialed enough that no one questions a slow drift away from it either.
Holding the tension deliberately
- Engage with technical detail selectively and purposefully, not compulsively. The goal is calibration — asking the right question at the right depth — not staying the most technical person in the room.
- Notice which direction you personally drift under pressure. Most people have a default failure mode; knowing yours makes it something you can actively correct for rather than discover after the fact.
- Treat technical currency as maintenance, not achievement. The register you neglect this month is the one that quietly goes first.