How to Get Promoted

Every piece of advice in this guide follows from this one structural fact.

In most organisations above about fifty people, promotions run through a calibration process. Managers put forward candidates. Peer managers, a skip-level, and often HR review them together. The purpose of the meeting is to ensure that a Senior on one team means roughly the same thing as a Senior on another.

Three things follow, and they are uncomfortable.

1. Your manager is your advocate, not your decider. Their skill at arguing for you matters roughly as much as your performance does.
2. Most people in the room have never seen you work. They are evaluating a description of you, not you.
3. You are being compared, not assessed. The question is not "is this person good" but "is this person more clearly ready than the other names on the table."

Diagnose before you act. Working on the wrong blocker is the most common way people lose a year.

Note the pattern in the right-hand column. Only the skill blocker produces specific, repeated feedback. If the feedback you get is vague, warm, or absent, you almost certainly do not have a skill problem — and grinding harder at the work will not move you.

The work is real. The record of it is not.

This is the most common blocker and the fastest to fix, because nothing about your actual performance has to change. What has to change is whether it exists anywhere outside your own memory.

Keep a running record

One document. Every two weeks, three lines: what you did, what changed as a result, who else saw it. This takes about four minutes and it is the single highest-return habit in this guide. When your manager sits down to write your case, you hand them the raw material instead of hoping they remember March.

Make the work legible to outsiders

• Write short summaries of finished work and post them where people beyond your team read them.
• Present at whatever cross-team forum exists. Once a quarter is enough.
• When you help another team, make sure their manager knows it happened. A one-line note to them is not self-promotion, it is closing the loop.
• Name the result, not the activity. "Cut onboarding from six weeks to three" travels. "Worked on onboarding improvements" does not.

A mentor gives you advice. A sponsor spends their own credibility on you when you are not in the room.

This is the blocker people are least willing to name, because it feels political. It is not political. It is structural: someone senior has to be willing to say "I will put my name on this person" in a room full of peers who will remember if they were wrong.

How sponsorship is actually earned

Not by asking. Sponsors back people who have made them look good. The mechanism is simple and it is slow: do work that matters to a senior person, do it visibly and reliably, and let them experience you solving something they care about.

1. Find out what the senior people are worried about. Listen in reviews and all-hands for the problem that keeps recurring.
2. Take a piece of it. Not the whole thing — a piece you can finish.
3. Deliver it and close the loop directly with them. Short, factual, no padding.
4. Repeat. Two or three cycles of this builds something that asking never will.

Making your intent known

Sponsors cannot advocate for something they do not know you want. This conversation is worth having explicitly, once, with anyone senior who has seen your work.

I'm working toward [level] over the next year or so.

You've seen a fair bit of my work on [project]. I'd
value your read — where do you think I'm genuinely
ready, and where would someone push back?

And if there's work coming up where I'd be useful to
you, I'd like to be in the room for it.

You cannot be promoted for work you have never been given the chance to do.

Promotion committees look for evidence that you are already operating at the next level. That creates a chicken-and-egg problem: you need next-level work to get promoted, and you need the promotion to be assigned next-level work. Everyone who gets promoted breaks that loop before the title arrives.

What "next level" usually means

How to get the scope before the title

• Ask for the ambiguous problem, not the bigger version of your current task. Scope is about ambiguity, not volume. Doing twice as much of your current job reads as capacity, not readiness.
• Volunteer for the thing that crosses team boundaries. Cross-team work is how people outside your team form an opinion of you, which is also the evidence fix.
• Take the unowned problem. Every organisation has a known issue nobody owns. Owning one is the cleanest way to demonstrate the next level.
• Hand your current work away deliberately. If you are still doing all of your old job, you have no room for the new one, and you look like someone who cannot delegate.

I want to be a credible candidate for [level] in the
next couple of cycles.

Reading the level definition, the gap I see is that I
haven't owned something with [the ambiguity /
cross-team surface / people component] yet.

Is there something coming up like that I could take?
I'd rather be tested on it now than talk about it in
the abstract.

The least common blocker — and the only one where the feedback is specific.

You have a genuine skill blocker when the same specific criticism has come from more than one person, more than once. Not "be more strategic." Something like "your written updates leave people unclear what decision you want," or "you escalate too late."

The good news is that a named skill gap is the most tractable of the four blockers, because you know exactly what to work on. The bad news is that most people never get told plainly enough to act on it, which is why the diagnosis matters so much.

Get the feedback sharp enough to use

I want to close the gap rather than guess at it.

If you were arguing against my promotion in a
calibration meeting, what's the sentence you'd use?

I'd rather hear the blunt version now.

That question works because it gives the other person permission and a frame. Most managers soften feedback out of kindness; asking them to voice the objection removes the need to soften it.

Promotions are decided months before they are announced. Work backwards from that.

If promotions are decided in, say, October, then October is not when you start. It is when the argument is made using evidence that had to exist by August, from work that had to be assigned in April.

The document you hand your manager

One page. Not a plea — a briefing. Written so your manager can paste sections of it into whatever form the company uses. Make it easier for them to advocate for you than not to.

[Your name] — case for [level]

Scope owned this cycle:
• [the ambiguous or cross-team thing, and the outcome]
• [second piece, with the measured result]

Evidence against the level definition:
• [criterion] — [what you did that demonstrates it]
• [criterion] — [what you did that demonstrates it]

Who has seen this work:
• [name, team, what they saw]

Known gap and what I've done about it:
• [the honest one, and the fix]