There's a director I worked alongside years ago who I'll call Thomas. Same organization, same level, similar technical background. We started in comparable roles around the same time.

Within four years, Thomas was a VP. I was still a director. And I spent a significant stretch of that time genuinely confused about what was happening.

The easy explanation was relationships. Thomas knew people. He was more naturally social, more at ease in executive conversations. I was more introverted.  I told myself that was the difference. It let me off the hook. It was an excuse not to take responsibility for my situation.

The real explanation was harder to see and harder to admit. Thomas was running a loop I wasn't. And I didn't understand the loop until I could look back at it clearly.

Here's what the loop looks like from the outside.

A leader shows up with presence in an executive conversation. Not dominance. Not performance. Presence. They communicate clarity. They speak to what matters. They signal, without announcing it, that they belong in this conversation.

That signal does something. The people in the room notice. They start including this leader in the next conversation. And the next one after that. Each conversation brings more context. More visibility. More access to the people who make decisions about advancement.

Over time, the leader running this loop is operating at a level of organizational access that almost guarantees opportunity. Not because they schemed their way there. Because presence created a compounding advantage that most people around them never noticed building.

The person outside the loop has a completely different experience. They're delivering. Often delivering well. Getting positive feedback. Waiting for that feedback to translate into advancement. Watching peers move while they stay still.

I was in that second group. For longer than I want to admit.

What I didn't understand then is that work and presence are different mechanisms. Work creates reputation. Presence creates opportunity. Those are not the same thing, and optimizing for one does not produce the other.

Technology leaders are almost universally trained for the work side of this equation. When I was coming up, technical depth was the primary currency of advancement. You moved up by being the person who understood the systems better than anyone else. That worked, to a point.

The ceiling became visible to me in my late 30s. The work was excellent. The recognition was real but constrained. The advancement had slowed in a way I couldn't explain through performance data.

What I hadn't built was the loop. And by the time I understood what the loop was, I'd already spent three years outside of it.

The entry point into the loop is not a single moment or decision. It's a shift in what you're paying attention to. Instead of asking "how do I deliver this well," the question becomes "what am I communicating in the rooms I'm already in."

Most technology leaders never ask that second question. They're optimizing for delivery, expecting it to eventually generate strategic visibility. It rarely does.

Here's what the loop actually requires at its entry point: showing up in non-technical conversations with something to contribute. Not a technical opinion. A perspective that connects to what the people in the room care about. Business outcomes. Strategic direction. Organizational dynamics. The questions that matter above the technical layer.

That shift is harder than it sounds. Technology leaders spend years building expertise in one domain. That expertise generates real confidence. Walking into a strategy conversation and contributing without that same expertise requires a different kind of confidence. Most leaders don't have it yet because they haven't built it.

And that's the beginning of what the newsletter tomorrow will focus on: why the loop is harder to enter than it looks, and what specifically tends to keep capable leaders stuck outside of it.

But before that: take a moment with this question. In the last six months, what rooms have you been in where you had a perspective and stayed quiet? What kept you from speaking?

That answer tells you where your loop is stuck.

The credibility loop sounds simple once you can see it. Presence creates opportunity. Opportunity creates visibility. Visibility creates advancement.

Simple to name. Genuinely difficult to perfect.

Here's what I've observed about why capable technology leaders stay outside the loop even after they understand it.

The first friction point is identity. Most technical leaders have built their confidence through expertise. They know how to walk into a room where they're the authority on the subject. They know how to answer questions, defend decisions, explain complexity. That expertise-based confidence is real and earned.

For leaders who've spent 20 years building confidence through depth, that pivot feels exposed. Like operating without the armor that made them credible. Your nervous system has been trained to associate credibility with expertise. Showing up without expertise feels like showing up without credibility.

That's the friction. And it's why leaders who intellectually understand the loop still hesitate at the entry point.

The second friction point is feedback delay. When you deliver a project well, the feedback is relatively fast. You know quickly whether it worked. That feedback loop trains leaders to stay in execution, because execution produces clear signals.

The loop requires staying in it long enough for the compounding to become visible. That usually takes six to twelve months of consistent presence. Most leaders give up in three.

The third friction point is the perception that presence requires a personality you don't have. That it's about being the loudest voice, the most charismatic, the most naturally commanding. I've watched some of the most impactful leaders I know operate very quietly. Calm. Measured. They don't dominate rooms. They anchor them.

What they do consistently is speak with clarity when they speak. They don't hedge. They don't bury their point in caveats. They say what they think, connect it to what matters, and stop. That's it. That's the behavior. It's not personality. It's practice.

So what does entering the loop actually look like in practical terms?

It starts with identifying the conversations that matter and being present in them. Not every meeting. The ones where strategy is being shaped, where decisions are being made, where your perspective on the intersection of technology and business has relevance.

Then it requires contributing. Not waiting until you have a fully formed technical argument. Offering a perspective. A question that reframes the room's thinking. An observation that connects what you know to what they're solving. Imperfect is fine. Absent is not.

Over time, if you're consistent, the invitations start coming. Not announced. Just present. You're included in a conversation you weren't before. Someone asks your perspective when they weren't required to. A decision gets made in a room you were in, rather than a room you heard about later.

That's when you know the loop has started.

This is the work I do with technology leaders who are in the gap between strong execution reputation and genuine executive presence. It's not about transforming personality. It's about understanding specifically what presence communicates and developing the behaviors that produce it, consistently, over time.

The leaders who make this shift don't all look the same on the other side. But they share one thing: they stopped waiting for the loop to find them and started building it deliberately.

If you're recognizing yourself in any of this, the next step isn't a big move. It's a small one. Identify one conversation this week where you have a perspective and have been staying quiet. Say the thing.

The loop starts there.

Robert

Follow me on LinkedIn

Join the IT Leadership Excellence Network on LinkedIn