ISSUE #105

Advancement asks you to release the identity that made you successful.

You were told you needed executive presence, so you worked on executive presence. You were told you needed business acumen, so you sat in on the sales calls and read the annual report. You were told to think more strategically, and you built the three-year plan nobody asked you for.

You did the work.

Your last review said you had grown noticeably. Your peers said it too, unprompted, which is the version that actually counts.

The role still went to someone else.

Every conversation about executive advancement covers the same territory. Skills. Visibility. Sponsorship. Timing. All of it is real, and all of it is discussable, which is exactly why it gets discussed.

The part that decides the outcome almost never comes up, because it sounds abstract until the moment it costs you something concrete.

Advancing to the executive level asks you to release the identity that made you successful for twenty years. Not your standards. Not your judgment. The self-concept underneath them, the one that says I am the person who knows.

Raymond (not his real name) came to me not long after his company was acquired into a 70,000 person organization. He had been leading technology teams for years. He had delivered serious results in analytics and data science, the kind of work that gets referenced in other people's business cases.

Every time I described him as a technology leader, he corrected me. Not aggressively. A small adjustment, over and over, until I stopped and asked him directly.

"You have been leading tech teams for years. You have delivered major results in analytics and data science. Why don't you consider yourself a tech leader?"

His answer came without hesitation, which told me he had been carrying it for a while.

"Well. I don't have a tech degree. And some folks on my team are more technical than me."

Sit with that. A leader running significant technology work inside a 70,000 person company, measuring his right to the title against a credential he did not have and a comparison nobody had asked him to make.

Nothing in his skill set was missing. He had the results. He had the scope. What he did not have was a version of himself that matched what he was already doing.

Identity misalignment does not announce itself. There is no review that says you have developed the capabilities and your self-concept has not caught up. Nobody has that language, including the people deciding.

What happens instead is quieter and slower. You keep developing skills you already have, because the visible feedback named the visible thing. You get another year of strong reviews and no movement. You watch a peer with less depth move into the seat and you assemble an explanation about politics or timing, and some of it is even true, which makes it harder to see past.

Quietly, this becomes the shape of a decade. Not a failure. A long, well-reviewed plateau, with a development plan refreshed every year that never touches the thing holding the ceiling in place.

By the time most leaders can name it, they have usually been carrying it through two or three advancement cycles. The capabilities were ready years before the identity was.

You cannot fix what you cannot locate. Three questions will tell you where yours sits. Answer them fast, before you construct the better answer.

1. When you introduce yourself, what comes first? Not your title. The sentence after it, the one where you explain what you actually do. Does it describe what you know, or what you move?

2. What do you reach for when the pressure lands? In the meeting where something has gone wrong and a decision has to happen now, does your attention go to the technical problem or the business consequence? Everyone watches this and nobody mentions it.

3. Ask someone who knows your work well: do they see you primarily as a technical expert or as a business leader? Ask it plainly. Then listen without defending, which is the hard half.

None of these have comfortable answers on the first pass. The discomfort is the useful part.

Why Capable Leaders Stall Right Here

The leaders who carry this longest are usually the strongest ones, and the reason is almost mechanical.

Twenty years of leading from technical identity built something physical. The route from problem to technical answer is worn smooth. It is fast, it is efficient, and it fires before you have finished hearing the question. The executive route has not been built yet. There is nothing there to fire.

That is why reading about the shift produces so little. Insight does not build the second route. Only repetition does, in rooms where your best instinct is the wrong tool, which feels like incompetence long before it feels like growth.

Most capable leaders will not sit in that feeling voluntarily. They have spent two decades being the person who knows. Being visibly not-the-expert, on purpose, in front of people whose opinion matters, runs against everything that has worked.

So they retreat to skill development, which is comfortable and legible and produces a certificate. The identity stays exactly where it was.

The organization helps them stay there. Every time you solve the hard technical problem in front of the room, somebody thanks you for it that afternoon. Nobody thanks you for the meeting where you stayed quiet on the architecture and asked about the customer instead. One of those behaviors gets immediate, warm, specific feedback. The other gets silence for a few months and then, maybe, a different kind of consideration when a seat finally opens. You are being trained continuously, by people who mean you well, to keep being exactly who you already are.

I know the pull of that retreat, because I ran the same play in a different direction.

When I left Accenture after seventeen years, I lay awake wondering whether I was making the biggest mistake of my career. I had the money, the title, the prestige. People told me I was on the fast track. Seventeen years in. I walked anyway, and I was not confident about it. I second-guessed every step. Was I throwing away years of hard work? Was I being reckless?

Years later, one of my favorite leaders told the story to his team. He said he had watched me walk away from the comfort of a big company to join a startup, and that it took courage.

It stopped me. I had not seen it that way at the time. From the inside it had not felt like courage at all. It felt like fear and doubt and no map.

That gap between how it feels and what it is turns out to be the whole thing. The identity shift feels like loss while you are inside it. From outside, it looks like the moment someone became who they were going to be.

If this describes where you are, the useful next step is not another capability to develop. You have enough of those. What is worth doing is looking honestly at where your identity is anchored, what it is costing you in advancement terms, and what the next ninety days would need to contain for the second route to start getting built.

That is difficult to see from inside your own career, because the anchor is not visible to the person standing on it. Everyone around you has adapted to the version of you that already exists, and none of them has reason to question it.

I work with technology leaders on exactly this. The first conversation is thirty minutes. We name where you are actually anchored and what would have to change, specifically, in your organization and your role.

Book time here: https://meeting.techleadership.net/

The identity that got you here was never a mistake. It served you. It earned every title you hold. That is what makes releasing it feel like a betrayal of the person who did all that work.

It is also the only thing standing between you and the seat you have been developing toward for three years.

You will not think your way across. Nobody has. You build the second route by walking it before it exists, badly at first, in rooms where you would rather be the expert.