ISSUE #107

The window closes quietly, and your reviews stay excellent the whole time.

Most technology leaders treat advancement as a capability question.

Build the skills, deliver the results, and the next level follows. It's a reasonable belief. It's also why a lot of very capable people arrive at 52 wondering what happened.

Capability is necessary. It has never been sufficient. The variable almost nobody plans around is timing, and timing is the one with a deadline attached.

Across thirty years I've watched a specific version of this play out. The leader is strong, the reviews are strong, and the scope keeps growing. The advancement conversation keeps getting postponed for reasons that are individually sensible and collectively fatal.

What makes it hard to see from the inside is that nothing is going wrong. There's no bad quarter to point at, no conflict with a boss, no missed number. The career doesn't stall in any way that shows up on a dashboard. It just stops converting effort into altitude, and the conversion rate changes so gradually that the first real signal is usually somebody else's announcement.

Malcolm came to me after he'd been passed over for a CIO role. He'd been a senior technology director for years and he'd delivered everything asked of him. The role went to an external candidate. By the time we talked he was reacting to everything and initiating nothing, and his confidence was gone. He told me he'd assumed his track record would speak for him.

What we changed wasn't his capability. He already had that. We changed where his attention went: strategic thinking instead of firefighting, delegation instead of control, presence instead of panic. Three months later he landed a CIO role at a much larger company, at a significant step up.

The capability had been there the whole time. What had been missing was anyone senior seeing it in the shape of the job he wanted.

The postponements are the expensive part, and each one is defensible on its own.

Finish the migration first. Get through the reorg. Wait until the new CTO has settled in. Let the reorganized team stabilize. Every one of those is a real reason, and every one of them costs twelve to eighteen months.

Run three of them back to back and you've spent four years. By the time you turn your attention to positioning, you're doing it from the narrow end of the window instead of the wide end. The organization has spent those same four years forming a view of you, that view is now well established, and it's the view of someone who runs the current thing well.

Quietly, that becomes your ceiling. Not because anyone decided it. Because nobody had a reason to decide otherwise.

Some things genuinely do improve with time, and it's worth being precise about which ones don't. Your technical judgment improves. Your instinct for your organization improves. Your reputation for reliability improves, which is the one that quietly hurts you. What doesn't improve on its own is the number of senior people who can describe your value in business terms without your help. That number stays flat for years unless you do something specific about it, and it's the number the decision actually turns on.

When a leader tells me they're not sure whether they're inside the window or past it, I ask three questions.

Where does the evidence live? If everything that proves you're ready sits inside your own function, you have evidence that convinces the people who already know. The decision gets made by people who don't.

What's the last thing you did that had nothing to do with delivery? Not a project. A conversation about pricing. A customer escalation you inserted yourself into. A board deck you helped shape. Positioning is built out of these and almost nothing else.

If a role opened next quarter, who inside your company would advocate for you without being asked? Name them. If the name takes more than a few seconds to surface, that's the gap, and it closes more slowly than most people expect.

None of those three questions are about capability. That's deliberate. Capability is almost never the thing that's missing by the time someone starts asking me about the window.

Clarity doesn't produce movement here, which surprises people.

A leader can see the whole picture, agree with every word of it, and still do nothing different for another eighteen months. The reason has nothing to do with discipline. The work of positioning carries no deadline, and everything else on the calendar does. Delivery has dates. Escalations have dates. A window doesn't page you at 2 AM.

There's something less comfortable underneath it too. Positioning means being visible before you feel ready, in rooms where you're not the expert, on subjects where somebody else knows more. For people whose entire professional identity is built on being the one who knows, that's genuinely unpleasant. Avoiding it doesn't feel like avoidance. It feels like being appropriately humble, or waiting for the right moment, or focusing on the work.

In practice it shows up as three specific stalls, and I've watched all three enough times to see them coming.

The first is the proof-point loop. One more successful launch, one more clean audit, one more year of numbers, and then the case will be undeniable. The case is already as strong as delivery can make it. Additional delivery adds almost nothing to it, because the people deciding stopped evaluating your delivery a long time ago and started evaluating your range. More proof of the thing they already believe doesn't move anyone.

The second is the sponsor gap. Almost nobody advances on the strength of their own advocacy. Somebody senior has to be willing to spend a little of their own standing on your behalf, in a room you're not in. That relationship takes eighteen months to build and about four weeks to need. Leaders discover the gap at the exact moment the gap can't be closed, and then they spend the following year building the relationship they should have had, for the role that already went to somebody else.

The third is the permission problem, and it's the quietest of the three. A lot of very capable people are waiting to be told it's their turn. Not consciously, and they'd deny it if you asked. But they're organizing their behaviour around being selected rather than being considered, and those produce completely different calendars. One of them is full of excellent work. The other has recurring time in it for conversations that have no deliverable attached and no obvious reason to exist yet. Nobody is coming to tap you.

Nobody stalls here because they're lazy. They stall because the thing that made them excellent is now telling them to wait.

There's one more thing worth saying, because it's the part leaders find hardest to accept. The window closing doesn't mean your career is over. It means the ceiling relocates. You keep advancing in scope, in compensation, in respect, and you do it inside a band that got decided while you were being reasonable. Plenty of people build genuinely good careers there. The ones who struggle are the ones who intended something else and never made a decision against it.

If you're inside the window and you're not sure how much of it is left, that's worth an hour of real conversation rather than another quarter of estimating.

Book a time and we'll map where you actually stand: how the decision-makers describe you today, what would have to change for them to describe you differently, and what's realistic in the runway you have. You'll leave with a read on your own position, whether or not we ever work together.

https://meeting.techleadership.net/

The window doesn't close with an announcement. It closes with a year where nothing unusual happens, and then another one just like it, and by the time the pattern is obvious you're reading it backwards.

You're inside it right now. That's the good news and the pressure in the same sentence.