There's a version of a CEO check-in that goes like this.

You walk in prepared. Delivery on track. The metrics you were asked for, green. The sprint closed cleanly. You've covered everything on the agenda, answered every question, and left nothing unresolved.

The CEO nods. Says good. And moves on.

You leave the room not knowing what just didn't happen.

Early in the CTO role, the instinct is to measure what you can control.

Tickets closed. Features shipped. Uptime maintained. Sprint velocity trending in the right direction. These are real numbers. They represent real work. And for a while, they feel like the right answer to the question: how are we doing?

The problem isn't that these metrics are wrong.

It's that they point inward.

They describe the health of the engineering function. They tell you how the team is performing against its own targets. What they don't tell you, and what they were never designed to tell you, is how the business is moving, where it needs to go, and whether the CTO in the room is helping steer it there.

When I was running a small team early in my career, I was delivering. Cranking through tickets. Hitting short-term goals. Every number I was tracking was within my control, trending positively, exactly where it should be.

I had no idea what the CEO was actually watching for.

It isn't the metrics.

What a CEO needs from a CTO isn't a status update on engineering health. They can get that from a dashboard. What they're watching for is something harder to measure and easier to feel. Often they can't articulate it clearly themselves.

Can this person see around corners? Do they understand where the business needs to go, not just where engineering is heading? When a decision needs to be made about direction, will they bring a point of view or a progress report?

The numbers were right. The narrative was missing.

That gap between accurate reporting and genuine business thinking is what creates the quiet room. The CEO nods because the answer is technically correct. The conversation ends because there's nothing to push back on, nothing to build from, no indication that the CTO has been thinking about the company rather than the team.

Over time, that pattern compounds. The CTO becomes reliable but not indispensable. Present but not shaping anything.

The metrics feel like evidence.

When everything you're tracking is green, it's genuinely difficult to see the problem. There's no failure signal. The work is getting done. Nobody is complaining. The engineering team is performing well.

What's missing is invisible precisely because you're not measuring it.

CTOs in this position are often focused on delivering for their boss rather than delivering on the company's goals. They're producing what was asked for. They're reporting against targets that were set for them. The whole system is working. Just at the wrong level.

The technical goals and the business goals can look identical from inside engineering. They rarely are.

The CTOs I've worked with who make this transition describe a specific shift.

They stop presenting answers and start asking questions. In a CEO check-in, instead of walking through what engineering delivered, they open with something that requires the CEO to think. A question about direction. A challenge about where the company is heading and what that means for the technical roadmap. A perspective on what's coming that nobody else in the room has articulated yet.

At first, that can feel uncomfortable for both sides. A CEO who has been receiving reports isn't always prepared for a CTO who wants to interrogate the strategy.

But as that dynamic matures, something changes.

The CTO is no longer the person who accounts for engineering. They become the person whose thinking the CEO actually wants in the room. The relationship moves from reporting line to strategic partnership. And it's usually the CEO who notices the difference first.

What most CTOs don't realise is that this transition isn't about doing more.

It's about measuring differently. Thinking at a different level. Asking the questions that only someone who understands both the technology and the business can ask.

The metrics will always be part of the conversation.

They just can't be the whole of it.

👉🏼 In your last CEO check-in — were you reporting on engineering, or were you shaping the direction of the business?

If that quiet room feels familiar, I've been working on something for exactly this moment. A free five-day map for early-stage CTOs, built from everything I learned the hard way and everything I've seen work in coaching. Reply "YES" and I'll make sure you get it first.

Talk soon,
Adam.

This week on The CTO Playbook, I'm joined by Michael Di Prisco to explore how engineers navigate the tension between technical identity and leadership responsibility. From documenting technical debt as a cultural shift rather than an avoidance strategy to separating authority from responsibility, he shares a pragmatic, experience-first approach to growing without losing the craft.

🎧 Tune in on your favourite podcast platform or listen on the podcast page.

Build the habits, systems and focus to step beyond execution, and grow with influence, alignment and real strategic impact.

The next CTO Playbook cohort starts on 14 May. Enrolment is now open, and places are limited to maintain depth, trust, and support.

If you’re ready to scale your leadership, influence, and impact, let’s talk about my premium 1:1 coaching for strategic, high-impact leadership. CTO Ascent works as a standalone engagement or alongside CTO Basecamp or CTO Elevate. Book your call with me here.