Moving from Head of Tech to CTO

The first thing that changes when you become CTO is not your calendar, your remit, or even your inbox. Instead, it’s the assumption that you already know why everything is broken.

Not how it failed. Not when it failed. Rather, why it failed in a way that can be summarised neatly in a board paper without causing discomfort. As Head of Tech, you could still say, “it’s complicated,” and be rewarded for honesty. As CTO, the same sentence now sounds like a confession.

That is the trick of the promotion. The job description barely shifts. However, the expectations do. Immediately. Quietly. Without anyone feeling the need to explain themselves.

The title change is administrative. The role change is existential.

Previously, success as Head of Tech showed up in delivery. Systems shipped. Incidents avoided. Teams retained. A general sense that the platform had not collapsed and the engineers had not started updating their CVs during stand-ups.

Once the CTO title appears, delivery becomes the minimum requirement. At that point, you become accountable for meaning. Why this system exists at all. Why this architecture still makes sense. Why the cost base aligns with a strategy agreed in a meeting you were never invited to.

Consequently, the technology estate stops being a set of pragmatic trade-offs and starts acting as evidence. Evidence of intent, confusion, or long-standing disagreements that were never resolved, merely deferred.

None of this is spelled out. Instead, it emerges during your first board meeting, usually when someone asks why the platform cannot support the revenue plan and looks faintly offended when you pause before answering.

The illusion of continuity

Most organisations treat the move from Head of Tech to CTO as a straight line. Same individual. Bigger chair. Possibly a different colour lanyard. The comforting assumption is that nothing material needs to change because “they already know the tech”.

That assumption is wrong.

Knowing the technology is no longer the point. What matters instead is understanding how the organisation talks about the technology, particularly when it is nervous.

As Head of Tech, you dealt in facts. As CTO, you deal in interpretations of facts. Ideally, these interpretations survive contact with a spreadsheet and a non-executive who skimmed half a Gartner report between stations.

Over time, you also learn to suppress the urge to correct people. Boards do not enjoy being technically right. They enjoy being strategically reassured. The gap between the two is where most new CTOs quietly come unstuck.

From advocate to proxy

In the previous role, you advocated for technology. You argued for budget, headcount, and time to fix the system everyone agreed was dangerous but nobody wanted to pay for.

After the promotion, you become a proxy for the technology itself. When delivery slips, the issue is no longer an optimistic roadmap. Instead, “technology is struggling”. When margins compress, it isn’t pricing pressure. Instead, “the platform is expensive”.

This shift is rarely personal. Organisational gravity does the work.

At that point, you become the acceptable human surface for abstract complexity. The system cannot attend the meeting. You can. Therefore, you do.

As a result, the job becomes lonelier than advertised. You defend decisions you did not make, architectures you inherited, and trade-offs that were rational at the time but have since become unfashionable. You are also expected to do this calmly, preferably without visible frustration.

Strategy theatre and the CTO as set dressing

Sooner or later, a strategy cycle begins. Slides appear. Words like “platform”, “leverage”, and “optionality” surface with a confidence that suggests someone once attended a conference.

At this stage, your role is often misunderstood.

Many first-time CTOs assume they are there to define technology strategy. In reality, the organisation has already decided what it wants to believe. Your job is to make the technology narrative compatible with that belief, without lying outright.

This requires restraint. Push too hard and you become “not aligned”. Agree too quickly and you inherit accountability for a future that was never technically plausible.

The practical move is to translate ambition into constraints early, quietly, and repeatedly. Ideally, this happens before the ambition solidifies into a KPI with your name next to it.

The meeting after the meeting

Earlier in your career, meetings ended when they ended. As CTO, the real work often starts afterwards.

A board meeting closes with nods and polite summaries. Shortly afterwards, the CEO calls. Or the CFO. Sometimes both. Separately. Each with “just one follow-up”.

Those conversations reveal what actually matters. What worried them. What they chose not to ask in front of others. What they expect you to absorb so they do not have to.

This is not duplicity. It is hierarchy in action.

Fail to recognise this, and you will spend months responding to what was said in the room while decisions are shaped by what was said in the corridor.

Your old team will watch you carefully

Your former peers will congratulate you. In many cases, they will mean it.

At the same time, they will watch closely for signs that you have “gone native”. Every budget compromise, every ambiguous answer, and every defence of a decision they dislike will be noticed.

This observation is not malicious. It is professional.

You are no longer one of them. However, you are not fully one of them either. This liminal state is uncomfortable and unavoidable. Attempts to resolve it by over-identifying with either side usually end with a reorganisation and an awkward all-hands.

What actually changes, if you do it properly

A successful transition does not require becoming more visionary, more technical, or more executive.

Instead, it requires becoming more legible.

You learn to explain systems in terms of risk and choice rather than components. You stop describing what you are building and start describing what you are deliberately not building, and why.

Gradually, you develop tolerance for decisions that are imperfect but survivable. You lose patience with heroics. You become suspicious of anything described as “quick” and deeply interested in second-order effects.

None of this feels glamorous. It does not belong in a LinkedIn announcement.

The quiet conclusion nobody advertises

Moving from Head of Tech to CTO is not a promotion in the conventional sense. Rather, it is a shift from being judged on outcomes to being judged on coherence.

Do the stories line up? Does the spend make sense enough? Does the risk feel contained enough? Are there fewer surprises than last quarter?

If the answer is yes, nobody says much. If the answer is no, everything suddenly becomes very clear.

That is the job.

Not brilliance. Not popularity. Just making the organisation’s relationship with its technology stable enough that everyone else can argue about something else.