There is a version of this story that gets told often. Someone was stuck for years, then they did the work, and four months later they got promoted.
The version is true. The version is also useless.
It skips the part that matters: what specifically happened in those four months, in what order, that produced the result. This is the part most senior professionals never get to see. The clients who break through tell their version of the story in shorthand. The clients still waiting do not have anyone to watch closely.
So I want to walk through one in detail. A senior IC at a tech company who had been on the promotion path for over two years without movement, and closed the gap in four months of deliberate work. Not what he did. When he did it. What changed in his read at each stage, and why the sequence mattered.
The shorthand version is that he did “positioning work.” That is technically accurate and practically meaningless. Positioning is not a thing you do. It is a sequence of specific moves, and the order of the moves is most of what determines whether the work compounds or just fragments.
Here is how the four months actually unfolded.
Month one: the audit
The first month was not about doing anything externally. It was about getting an honest read on what the current state actually was.
Most senior professionals skip this and go straight to “what should I do differently.” They cannot answer that question yet, because they do not have an accurate picture of what is currently being read about them. They have their own internal narrative, which is usually generous. They have whatever fragments of feedback they have received in reviews, which is usually polite.
Neither is the actual read.
The audit was three pieces. First, a careful look at his work over the previous six months, not what he had done, but at what altitude he had been operating. Most of his work, even the work he was proud of, was at his current level. Some of it, three projects specifically, had operated at the next level. He had not labeled the difference because he had been evaluating his work on effort and outcome, not on altitude.
Second, an honest read on what his manager, skip-level, and the cross-functional peers with influence currently believed about him. Not what he hoped they believed. What they actually said when his name came up. We could not get inside the calibration meetings, but we could read the proxies: the kinds of projects he was getting pulled into, the cross-functional escalations that did or did not route through him, the conversations he was or was not being included in.
The proxies told a consistent story. He was being read as a strong current-level contributor whose next-level readiness was an open question.
Third, an honest assessment of the gap between (a) the work he had actually been doing at the next altitude and (b) the read decision-makers had on whether he was ready for it. The gap was significant. The three next-level projects existed. They had not been visible at the decision-making layer because he had not made them visible.
They had landed as “good work” alongside all his other good work. No signal that they represented something different.
Month one produced no external action. It produced an accurate map of where he actually stood.
Without that map, every subsequent move would have been a guess.
Month two: the language
The second month was about building the case.
Not the case for promotion in the abstract. The specific case for him, at the next level, in three sentences he could use in every conversation that touched the question. Not pitched. Used. As the natural way of framing what he did.
The three sentences were not slogans. They were the answer to a specific question: what does he, specifically, bring at the next level that nobody else in his cohort brings? Most senior professionals cannot answer this question. They reach for descriptions of their role, their responsibilities, the kinds of work they do.
None of that is an answer.
The answer has to name a specific thing about how he operates that produces a specific kind of value at the altitude above his current one. For him, it was a particular combination of technical depth and judgment about which problems were worth solving, not just executing well, but consistently identifying the leverage points in a system before anyone else had named them.
The three sentences captured this without overstating it. They named the capability, gave an example of where it had shown up in his recent work, and described what it produced at the next altitude.
He spent month two getting comfortable using this language. In 1:1s with his manager. In conversations with his skip-level. In how he described his own work when someone asked.
By the end of the month, the language had become natural. Not rehearsed. Available.
And he had started noticing something. His manager was beginning to use some of the same framing.
That was the first real signal that the work was landing. The language was now in his manager’s vocabulary, which meant it was now in the calibration conversation by proxy.
The first two months were diagnosis and language. The second two months were where the actual external signal got built, and the order matters more than people realize.
Below the paywall: months three and four. What specifically happened in the rooms that mattered. The two cross-functional moves that produced the inflection point. Why the promotion conversation itself was almost anticlimactic by the time it happened. And the four most common ways senior professionals try to compress this four-month sequence into one month and fail.
