Digital Leadership Excellence
Robert Castle
Robert Castle
Former Accenture Partner, CIO, two $50M+ exits. Now helping senior tech leaders break the invisible ceiling, usually in 3 to 6 months.

Greetings, and welcome to Digital Leadership Excellence, your trusted weekly guide to excelling in tech leadership, delivering results, and thriving with clarity and purpose. In every issue, we provide insights into winning strategies, growth tactics, and practical solutions, designed to support both current and aspiring technology leaders navigating the ever-evolving digital world.

ISSUE #112

Stop Proving You Can Execute

Why great execution keeps you filed as an operator.

The Myth of "Great Work"

Great work gets noticed. Most technology leaders grew up on that advice, and it's only half right. Great work gets noticed at the level you're already at.

Early in your career, you get promoted for execution. You solve the hard problems. You hit the dates. You're the one they call at two in the morning when something breaks, and you get rewarded for it over and over again. So you keep doing it.

Then, at some point, it stops working. Nobody tells you why. You deliver every time, and you still watch other people get the promotion.

The reason is simpler than most people expect. When the promotion decision gets made, nobody doubts you can do the job. They just can't point to a time you've actually done it.

“Great work gets noticed at the level you're already at.”

The hidden trap of out-executing everyone else.

Escaping the Operator Label

I think about how leadership sees people in three levels. These are my terms, and they aren't titles. The operator is the person who gets things done. The manager coordinates people and timelines so things get done. The executive shapes where the business is going.

Most technology leaders get stuck at operator or manager. Rarely because they can't think strategically. Usually because nobody above them has ever seen them do it.

A leader I'll call Victor heard this directly from an HR leader after he'd been passed over: "We really know you, but we kind of don't know you. You're too buried in the operation." Victor was a strong leader with real ideas about the business. Everything leadership had actually seen of him said operator.

Another client heard a different version early in his career: "You're too valuable here to promote. We need you doing what you're doing." He took it as a compliment. It was a warning.

There's a reason the label is so hard to shift. People change how they think through repeated action, and so do organizations. One strategic idea mentioned in passing doesn't move anything. A run of visible strategic moves does, both in how leadership sees you and in how naturally that kind of thinking comes to you.

Here's what makes waiting so costly. Every strong quarter of execution adds more proof to the file that says operator. The file gets thicker, and the label gets more accurate, because you keep confirming it.

By the time the role you want opens up, the decision is mostly made already. It gets made on the evidence people have about you, and that evidence has been piling up for years. A great interview can't outweigh it.

Working harder makes this worse. More effort at the operator level produces more operator evidence. You can tell people you're strategic until you're blue in the face. Until they see you doing strategic work, they won't believe it.

So here's the one thing. Stop proving you can execute, and start creating evidence that you can think strategically, in front of the people who decide. Execution still matters. Your team has to do it. Your job is to think about where it's all going.

There are three steps to that.

1. Buy back your think time. You can't show strategic thinking if you never have time to do any. Block half an hour a day like a meeting with your CEO, and use it to think about where your part of the business needs to be in a year.

2. Lead one strategic thing visibly. Lead it. Don't participate, and don't just attend the meeting. A business case, a roadmap, a cross-functional project. Anything where the question is "where should we go," not "how do we fix this."

3. Put the evidence in front of the people who decide. This is the step most people skip, and it's the one that matters most.

Three questions to sit with before you start:

1. When did you last spend thirty minutes thinking about next year with nothing on fire?

2. What's the last thing you led where the question was direction, not repair?

3. Who above your boss has seen you do it?

The Tech Leader's Brief
The Tech Leader's Brief
Get your Saturday back.
The whole week in tech, filtered to what matters.
See what's inside

Why Capable Leaders Stall (and How to Break Through)

Capable leaders stall on these steps for a handful of predictable reasons.

The first is trying to eat the elephant. A leader finally decides to show strategic thinking, so they pitch a huge transformation. It gets turned down. They conclude that leadership just doesn't get it, and they go back to execution, where at least the results are clear.

I've been there. After an acquisition, I kept pitching strategic ideas to my new leadership. They kept saying, "These are great ideas, keep them coming." Nobody wanted to fund any of them. It was really frustrating. What I learned is that more ideas weren't the answer. Buy-in was.

So if you keep hearing no, change the size of the ask. Propose a smaller piece of work. Better still, offer to support one initiative a senior leader already cares about, and add real value to it. A small strategic win that people actually see beats a big strategic deck that never gets approved.

Say your instinct is to pitch a full platform overhaul. Instead, find the initiative your COO keeps bringing up, maybe a customer-onboarding problem that's quietly costing renewals, and offer to map what technology could take off its critical path in the next ninety days. It's smaller. It already has a sponsor. And it puts your thinking in front of someone senior who wants it to succeed.

The second reason is that only your boss sees the work. You do strong strategic work, and the only person who knows about it is the person you report to. Your boss probably thinks highly of you. But your boss doesn't have much time to think about your career, because you take care of everything and you make them look good.

Promotion decisions are rarely made by your boss alone. Your boss's boss is part of that conversation, and so are their peers. If they don't know you, they can't support you. That means managing up and across as well as down. For most technology leaders that's a real shift, because we spent most of our careers with our own teams.

One of the easiest ways in is asking for feedback. One of my clients was doing a 360 assessment and asked his CEO to take part. The CEO said yes, and then said, "Why don't we meet for lunch?" That lunch turned into an ongoing conversation about what it would take for him to become a VP. It started with a simple request for feedback.

While you build those relationships, ask yourself who can champion you. A champion is someone senior who speaks up for you when your name comes up and you aren't there to speak for yourself. You want someone in that meeting who has seen your strategic work firsthand and can say, "I've watched them do it."

The third reason is quieter. The think time disappears first. You block the half hour, and on Tuesday an outage eats it. On Wednesday a meeting runs long. By Friday the block is back to being a gap in your calendar that anyone can book. The pull toward the urgent never lets up, and it makes you forget what matters most. Protect the block the way you'd protect a meeting with your CEO. You'd never cancel on the CEO for a status update. Don't cancel on your own thinking for one either.

The fourth reason is the one people don't like to say out loud. It feels like self-promotion. Nobody wants to be the person who talks himself up all the time. I get it, and I struggled with this too. There's a difference, though, between being arrogant and giving yourself credit where it's due. If leadership never sees your best thinking, your team loses an advocate and the business loses your ideas. If you aren't going to toot your own horn, who will?

Here's what the shift tends to look like in practice. In the first month, the half hour feels awkward, and most of what you write down is half-formed. By the second month, you notice you're asking different questions in meetings: where this is heading, what it costs, who else it touches. Somewhere in the third month, you pick one initiative a senior leader cares about and offer to help shape it. One move doesn't change the label. Three or four visible ones over six months to a year usually do, because by then the people deciding have their own examples of your thinking instead of your word for it.

If you keep delivering and keep watching the promotion go to someone else, this is the work I do with technology leaders. In a short conversation we'll look at the evidence the people deciding your next role actually have about you, and the one move that would change it fastest.

Leadership promotes people it has already seen operating at the next level. Hard work got you here. Evidence of your judgment is what gets you to the next one.

Robert

What did you think of today’s Newsletter?

select below

Login or Subscribe to participate

Robert Castle
Former Accenture Partner & CIO · Executive coach
Tech Leadership Solutions

This is my free Friday newsletter. I also write a paid one for Saturdays. The Tech Leader's Brief: 18 items, about seven minutes, $49.97 a year. See what's in it

Reply

Avatar

or to participate