A board decides it is time for serious technology leadership. A vacancy goes out for a CIO. Strong candidates apply — people who are genuinely good at making IT available, reliable and controllable. Two years later it turns out the real problem was that the company cannot renew its services fast enough. That was never the question that was asked.
This is not a hiring mistake. It is a definition mistake, and it is made before the first candidate appears.
Four emphases, not four jobs
In large enterprises, CIO, CTO, CDO and Chief Architect are different people with different budgets. In a company of 250 to 1,500 employees they rarely are. There is one technology leader, and all four questions land on that desk. The difference is not the job but the emphasis — and the emphasis decides where the energy goes.
The CIO emphasis is about making things available and usable. The systems that keep the company running do what they should, at acceptable cost and risk. This is the side that becomes visible the moment it fails and stays invisible as long as it works.
The CTO emphasis is about what you sell. Technology in products and services, and whether the company makes money from it. This is the revenue side of technology.
The CDO emphasis is the same as the CTO emphasis, applied to data and information. What does the company know, what can it do with that, and what is it allowed to do — the last of those increasingly loudly.
The architecture emphasis is the least understood and often the most decisive. It asks whether any of the above is possible at all. Whether a decision can actually be executed. Whether the landscape permits change or blocks it. Without this emphasis the other three become a collection of separate initiatives that get in each other's way.
The question that settles it
The useful question is not "which title suits us". It is this:
Where does our next twenty percent of value come from?
- From running what we already do better, cheaper or more reliably — then the CIO emphasis leads.
- From what we sell — a new product, a different service, a proposition that does not exist without technology — then the CTO emphasis leads.
- From what we know — better decisions, information as a product, or simply being able to evidence what we do — then the CDO emphasis leads.
- From being able to change at all — if every initiative stalls on what is already there — then the architecture emphasis leads, and the other three are secondary for now.
You can put that question to your own board this week, without a consultant. The answer is rarely unanimous, and the disagreement is the informative part: if the board does not agree on where value comes from, the vacancy is not your first problem.
Why the wrong choice is expensive and surfaces late
A technology leader with the wrong emphasis does not do bad work. They do good work on the wrong question. That is precisely what makes it surface so late.
The cost runs along three lines. There is direct waste: investments that succeed technically and deliver nothing commercially. There is delay: the question that actually mattered has gone unanswered for two years, and the market has moved in those two years. And there is confidence: a board that has lived through one disappointing technology programme becomes cautious about the next — usually at exactly the moment the next one is genuinely urgent.
With interim appointments there is an additional trap. An interim is selected on their last title, not on the emphasis you need. "Was CIO at X" is easy screening. Whether that person commands the emphasis that will define your next two years is a different question, and it rarely appears in the assignment description.
What you can do concretely
Three things, in order.
Decide the emphasis before you decide the title. The vacancy is an outcome, not a starting point. Ask the value question above first, then write the role.
Write down what must be different in two years. Not in systems, but in what the company will then be able to do that it cannot do now. If that does not fit in five lines, the assignment is not yet sharp enough to hold someone accountable to — or to attract them with.
Test for the emphasis, not the title. Do not ask a candidate what they were. Ask which decision they made that cost money, and why. The answer shows immediately where their centre of gravity sits. Someone with an architecture emphasis talks about dependencies and sequence; someone with a CTO emphasis talks about market and margin. Both can be excellent. But you will know which one is in front of you.
And then?
This piece is about the choice, not the execution. How you then deliver on the emphasis — how to set up an architecture function that speeds decisions up rather than slowing them down, how to judge whether a technology investment is defensible, what governance looks like when it is more than paper — that is the other side of the same question.
That side is worked out at delfen.ai, where the same subjects are treated at the level of execution: which instruments, which failure modes, what you do on Monday morning.
The choice is a board matter. The execution is a craft. They belong together, and most organisations are only ever offered one of the two at a time.