Executive technical advisory

What this role actually is

Executive technical advisory is not consulting in the traditional sense. It’s not a deck, a recommendation, and an invoice. It’s a sustained relationship with the CEO, CTO, CIO, CISO, and board — translating between strategy and engineering, holding both sides honest, and shaping the technical decisions that determine whether a transformation succeeds or quietly stalls.

I spend my time in three rooms:

• The boardroom, helping non-technical directors understand AI, cloud, and platform risk in language they can act on — without dumbing it down to the point of being misleading.
• The executive table, helping the CXO team make the few decisions that actually matter: build vs buy, the platform bet, the security stance, the talent model, the regulatory posture.
• The engineering floor, with the architects and staff engineers who will live with the consequences — making sure their reality reaches the executive table intact.

The conversations that matter

A typical advisory engagement turns on a handful of decisions, each of which compounds for years:

• The AI bet. Where on the spectrum from “buy SaaS” to “build foundation-model-adjacent capability” should the organisation sit? What does it cost to be wrong in either direction?
• The platform strategy. One platform or many? Centralised or federated? Who owns it, who funds it, and how do product teams consume it without being slowed down?
• The security and governance stance. Conservative enough to satisfy regulators, permissive enough to ship. The exact line is different for every organisation and every quarter.
• The talent model. Which capabilities must be in-house forever, which can be partnered, which can be augmented by AI? What does the engineering org look like in three years?
• The portfolio. Which initiatives are real, which are theatre, which should be killed today to fund what matters? Executives rarely have the technical context to answer this on their own.

How I work

A few principles, refined across more transformations than I’d care to count:

• Independent, but inside. Close enough to know what’s actually happening, far enough to say things that internal leaders can’t.
• No surprises. The job is to surface risks early, in plain language, with options — not to be proven right in the post-mortem.
• Decisions, not opinions. Every meeting ends with a decision taken, deferred deliberately, or escalated cleanly. Advisory that doesn’t move decisions is noise.
• Quiet credit. The wins belong to the team. My job is to make sure there are wins to claim.

Why it matters

The cost of a wrong technical decision at the executive level — a misjudged platform bet, a flawed AI strategy, a security posture that breaks under regulation — is measured in years and hundreds of millions. The cost of getting it right is a calmer organisation that ships ambitious things on a predictable cadence.

That’s the work. Get the few decisions that matter right. Make sure the people doing the work are heard. Hold the bar.