You already know why your peer is ahead of you.

You've known for a while. The story you've been telling yourself… their sponsor, their timing, the project that landed with unusual visibility. That story has a problem. You've been telling it for two years and it hasn't made the gap smaller.

The part you haven't said out loud is the part that's actually true. Three years ago, there was a move available to both of you. They made it. You didn't. That's the whole story. Everything else is texture around a decision.

This isn't a piece about what your peer did right. You already know what they did right. This is a piece about what you're going to do with the next twelve months, now that you've run out of ways to make the gap feel like something that happened to you.

I have watched many technology leaders carry the peer comparison story for years. The version where circumstances explain the gap is always more comfortable than the version where choices do. But the comfortable version has a cost: it removes the only variable you actually control. Circumstances are not yours to change. Choices are.

I have watched many technology leaders carry the peer comparison story for years. The version where circumstances explain the gap is always more comfortable than the version where choices do. But the comfortable version has a cost: it removes the only variable you actually control. Circumstances are not yours to change. Choices are.

What I've watched happen, consistently, is that the leaders who finally close the gap do it the same way. Not by getting lucky. Not by finding the right sponsor (although that can help). By going back to the moment the gap started and doing the thing they didn't do then. The move that felt premature. The room that felt presumptuous. The ask that felt like overreach. They make that move now, with three years of evidence about what waiting costs, and they don't stop making versions of it until the pattern is visible enough for the organization to read.

That's not a complicated strategy. It's an uncomfortable one. Which is why most leaders who know it don't execute it.

The longer this runs, the smaller you start playing. Not dramatically. Incrementally. You stop raising the strategic question because you're not sure it's your place. You pass on the project because your plate is full and you're not certain it would land well anyway. You wait. And every time you wait, the organization updates its picture of you with the data you just gave them. 

The decisions your peer made that you didn't are not mysterious. They are specific and repeatable and available to you now.

They put themselves in rooms before they felt ready to be in them. Not recklessly. Deliberately. They found a legitimate reason to contribute to a conversation one level above their scope, and they showed up to that conversation before anyone invited them.

They applied increasing demand to themselves before the organization required it. The leader who waits for the promotion to take on VP-level work never builds the evidence that justifies the promotion. The leader who takes on VP-level work first, visibly, gives the organization something to point to when the decision arrives.

They made a readable pattern out of their decisions. One stretch assignment is noise. Three in eighteen months is a narrative. The narrative is what gets said in the room when the promotion decision is made and you're not there to make your own case.

The reason the comfortable story is so durable is that it's partially true. Timing does matter. Sponsors do help. Some projects create visibility that others don't. Your peer probably did catch some breaks that you didn't.

But here's what you know and haven't fully let yourself sit with: the breaks your peer caught were downstream of moves they made. The sponsor relationship existed because they put themselves in proximity to that leader before they needed them. The high-visibility project landed in their lap because they had already established themselves as someone who raised their hand for things like that. The timing worked because they had been creating conditions for timing to work.

You've been waiting for conditions to create themselves.

That's the distinction that matters. Not luck versus unluck. Not sponsored versus unsponsored. Proactive positioning versus waiting. And the waiting feels like patience, which is why it's so persistent. Patience is a virtue in most domains of life. In compensation and advancement, it's a cost that compounds quarterly.

The specific thing you've been avoiding is also specific to you. Only you know what it is. But the shape of it is consistent across the leaders I've watched carry this gap.

It's the senior leader you haven't introduced yourself to because you're waiting until you have something more impressive to say. It's the cross-functional project you passed on because you were too busy with current deliverables. It's the moment in the meeting three months ago when you had a perspective on a strategic question and stayed quiet because it wasn't strictly your domain.

Each of those felt like a reasonable call at the time. Collectively, they are a portrait. The organization has been looking at that portrait for years. They know exactly where your ceiling is. You showed them, one careful decision at a time.

The twelve months in front of you can produce a different portrait. But only if you're willing to name what the current one actually shows.

Three things. One senior leader you have not yet had a real conversation with…find the reason to have it in the next 30 days. One project above your current scope…find the contribution you can make to it this quarter, visibly. One room you've been waiting to be ready for…decide you're ready enough and get in it.

None of those moves guarantee the promotion. All of them start building the pattern the promotion decision runs on.

You know what twelve months of the current approach produces. You've been watching it.

What would twelve months of the other approach produce?

If you want to map out specifically what those moves look like in your organization and your role, this is where we start: https://meeting.techleadership.net/

Your peer didn't get lucky. You didn't move. Those are different problems. One of them is yours to solve.

Robert