There's a particular kind of unease that's hard to name.

The team is shipping. The sprints are planned, the velocity is consistent, the deployment numbers look good. Nothing is on fire. By every measure that's supposed to matter, things are working. And yet there's an itch. Something that doesn't feel right, that no dashboard is capturing, that keeps surfacing in quiet moments and then disappearing before it can be examined properly.

I worked with a CTO who had been living with that feeling for weeks before he reached out. Finance company. Strong engineering operation. DORA metrics that most teams would be proud of. His CEO was satisfied. The board had no complaints. On paper, he was doing the job.

But he couldn't shake it.

When we started working together, he described his relationship to the leadership team in operational terms. He prepared updates. He attended meetings. He answered questions about the technical roadmap when they came up. He was, in his words, doing what had been asked of him.

What he hadn't noticed was the shape that had taken over time. He had become a supplier to the leadership team rather than a member of it. He arrived with answers. He left when the agenda moved on. The conversations between the other executives — about customers, about commercial positioning, about where the business was actually trying to go — happened in a space he wasn't really part of.

He was in the room, but he wasn't part of the room.

The metrics had given him a way to define the job that felt clean and defensible. Hit the numbers, keep the systems running, respond to what's asked. What they hadn't given him was a reason to go looking for the questions nobody had asked him yet.

There's a version of the CTO role that is essentially a very senior head of engineering. Technically excellent. Operationally reliable. Responsive to direction from the CEO and the wider business.

But it's a diminished version of the role, and the diminishment tends to happen gradually. The pattern is self-reinforcing. When a CTO positions themselves as someone who delivers what's asked, the business learns to ask. The CEO routes requests through them. Commercial conversations happen upstream, without a technical voice in the room. Over time, the CTO's influence narrows — not because anyone took it away, but because the operating pattern they established left no space for it.

Because everything still ran smoothly, there was no obvious signal that anything was wrong.

A few weeks into our work together — he was funding this himself, without organisational support — I suggested he ask the leadership team a question he had never thought to ask before. Something direct, about where the business was going and where he thought technology could be taking them — rather than waiting to be told.

He asked it. The room went quiet. His colleagues exchanged glances that he described as uncomfortable.

And then they told him that a search was already underway. They had been looking for a CTO who could operate as a genuine strategic partner. Someone who would bring a point of view to the commercial conversation, not just execute against it.

He found out a search was underway because he finally started asking questions instead of answering them. The timing was brutal.

He moved through what came next with more composure than most would. He understood quickly what had happened, put himself forward as a candidate for his own replacement, and made a serious case. It wasn't enough. The decision had already moved too far.

The CTOs I've worked with who turned this pattern around did so because they caught it earlier — before the business had already concluded something was missing.

What they changed wasn't dramatic. They started showing up to the leadership team with questions, not just status updates. They got curious about the commercial side — about what customers were actually experiencing, where the revenue pressure was coming from, what the sales team was running into. They started treating their peers in marketing, finance, and product as people who might have useful information, rather than stakeholders to be managed.

And over time, the nature of their contribution in those rooms changed. They went from being the person who explained what engineering was doing to being the person whose perspective the CEO actually wanted before a decision was made.

That's what it looks like to be part of the number one team, not just a function reporting into it.

The itch that CTO felt was accurate. He was reading something real. He just didn't have a frame for it yet.

The metrics were fine. They just weren't measuring the thing that was actually at risk.

In a leadership team, presence isn't established by attendance. It's established by contribution. By the questions you bring, not just the answers. By the degree to which your absence from a conversation would actually change its outcome.

That's the test worth running. Not the dashboard.

👉🏼 If you weren't in the room for your leadership team's last three significant decisions — not to present, but to actually shape them — what would have been different? Reply and let me know, I'm always happy to hear from you.

Talk soon,

Adam.

This week on The CTO Playbook, I’m joined by Nic Granger to explore how organisations turn data into meaningful outcomes. From siloed and inaccessible data to jumping too quickly to solutions, she shares a practical approach to creating value by focusing on people, workflows and real-world impact.

🎧 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 March cohort kicked off a couple of weeks ago. Join the waitlist to be the first to hear when the next cohort opens. Sign up for your waitlist-only discount.

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.