Why You're Not Getting Promoted: The Three Months Before the Packet
90% of "I can't get promoted" is not a capability problem. It's a narrative problem.
A year of your work turns into five bullet points on a slide. The committee is not evaluating your actual year — it's evaluating whether those five lines make them remember you. "What I did" and "how it gets told" are two separate jobs. You've already finished the first one. Most people start the second one the week before the deadline, which is far too late.
What's Actually Happening in That Room
The people on the promo committee don't know you. They may never have heard your name or read a doc you wrote. They have thirty candidate packets to get through, about fifteen minutes each.
In those fifteen minutes they're answering two questions:
- Is this work at the next level? (business impact / complexity / who was actually driving)
- Is this someone the org can't afford to lose? (irreplaceability, worth continued investment)
Question one is already settled — that's the last twelve months, and it's in the past. Question two is narrative, and you can still move it.
Four Things to Do in the Three Months Before
1. Find One Thing That Isn't Arguable
The strongest possible case for a level bump: there is one thing you did this year that only someone at the next level could have done.
If you're a senior going for staff, "I shipped five senior-scoped projects" is a much weaker argument than "I owned something that should have been a staff-level charter."
It doesn't have to be big. It has to match the next level in complexity. Here's a test: find someone already at that level, describe the problem, and ask how they'd staff it, break it down, and pull the resources. If their answer lands in the same order of magnitude as what you actually did, you're there. If it's obviously more sophisticated than yours, you're not.
2. Say It Out Loud, Outside Your Team
Even to three people on another team. A department brown-bag, a 1-on-1, a doc you broadcast. The goal is not to teach anyone anything. The goal is that someone outside your reporting chain has heard of the thing you did.
During calibration, someone will ask people off your chain: "Have you heard about the Y thing that X did?" If the answer is "yeah, I have," you now have evidence of org-level impact. If it's blank stares, all you have is a claim.
3. Get Your Manager to Tag You Early
Don't bring up "I want to go for the next level" a week before packets are due. Start three months out:
- In 1-on-1s, proactively report progress on the next-level-scoped work — not just status on your assigned tasks
- Ask flat out: "What's still missing between me and staff?"
- Take the answer, write it into a doc, and send it back: "Last time you said X — here's how I'm planning to close it."
By promo season your manager has already filed you as "a senior doing staff work." That's what they're standing on when they argue for you in the calibration room, and it's the difference between advocacy and a shrug.
4. Write the Packet Two Weeks Early, Get Three Readers
Not your manager — they're too invested to be honest. Get:
- A peer on a different team: can they state your core contribution back to you in 30 seconds?
- Someone one level above you: does the work read as next-level to them?
- A peer from another org: as a total outsider, where do they poke holes?
Revise after each one. Draft four is an order of magnitude better than draft one.
The Three Ways the Story Fails
Failure 1: a list of N projects with no through-line The committee reads that as "produced a lot, all over the place." Thread the projects into one theme: "this year I've been working the Y problem." Retrofitting the thread afterward is fine — that's not dishonest, it's how humans store information about other humans.
Failure 2: process instead of impact "I designed a new architecture." "I drove a cross-team collaboration." So what? Spell out what would have happened without you, and what actually happened because of you.
Failure 3: claiming your team's or your manager's work Someone in that room knows your manager. The moment they smell credit-grabbing, the whole packet is dead. You drove it; the team delivered it. Drawing that line explicitly makes you look more senior, not less.
Closing
The worst part of not getting promoted isn't the not getting promoted. It's not knowing why. In most cases the answer is boring: the work was enough, the org just never saw it. Three months of narrative engineering beats a week of polishing slides by a factor of a hundred.