Three years in. Reviews that use words like “reliable” and “exceeds expectations.” Nothing has ever gone badly. And last month someone who joined eighteen months ago moved up a level, and you found out in the same all-hands announcement everyone else did.
The natural explanation is that something unfair happened. Sometimes it is. More often something duller is true: that decision had been forming for most of a year, in conversations you were not in, on evidence you were not producing. You were producing a different kind — that you are very good at the job you already have.
Why does being excellent at your current job keep you in it?
A promotion is not a reward for past performance. It reads like one and is often described like one, but it is a prediction. Someone is deciding whether you can do a job you have not done, and betting a team, a budget or a client relationship on being right.
So the evidence they need is about the next job. Three years of flawless delivery answers a different question extremely well: can this person do this level? Obviously, look at the record. That record is not neutral — it quietly builds a case that this is where you fit.
The shift you want is from being the best at your level to being visibly unremarkable at the next one. Not brilliant at it — unremarkable. The promotion becomes easy when it looks like paperwork catching up with reality.
How do you do the next job before you have it?
This sounds like advice to work unpaid, and done badly that is what it becomes. Done well it is narrower: you take on a small amount of scope that resembles the shape of the level above, visibly and at low risk, and let go of some current-level work to make room. Shape matters more than volume. Levels usually differ along a few axes:
- Scope — one task, versus one project, versus one area that keeps existing after the project ends.
- Ambiguity — being told what to do, versus deciding what should be done.
- Blast radius — if you are wrong, who notices, and how expensive is it.
- Dependence on others — doing it yourself, versus getting it done through people who do not report to you.
Doing more of your current work faster moves you along none of these. Owning the messy cross-team thing nobody wants moves you along all of them at once, which is why that thing is usually the opportunity even though it looks like a chore. Pick work that is:
- Genuinely needed. Invented scope reads as empire-building. Real gaps read as initiative.
- Bounded. “I’ll own the vendor migration through Q2” is a promise you can keep. “I’ll own quality” is not.
- Recoverable if they fail. You want a track record of taking on hard things, not a spectacular first attempt.
- Legible outside your team. If describing it takes ten minutes of context, it will not travel to the room where levels are discussed.
And drop something. Add the next job to all of the current one and you will do both at eighty percent, and the story becomes “stretched thin” rather than “ready.” Hand off the thing you are best at. That is uncomfortable and it is the point.
What does the next level actually require here?
Almost nowhere writes this down usefully. Where a ladder document exists it says things like “demonstrates strategic thinking” and “influences beyond their immediate team” — not criteria, but the vocabulary people use to justify a decision after making it. The real bar lives in examples:
- Who has been promoted into that level here in the last two years? Not what their title is — what were they actually doing in the six months before it happened?
- What do the people currently at that level spend their days on, as opposed to what their job description says?
- What kinds of decisions do they make without asking? That boundary is usually the clearest definition of a level anyone will ever give you.
This differs sharply between organisations. Somewhere small, the next level might mean breadth — covering three functions competently. Somewhere large, it might mean depth, being the final word on something narrow. Advice written for one shape is actively wrong in another, which is why generic promotion advice cannot help you: it does not know which building you are in.
How do you become visible without becoming insufferable?
Here is the honest version, because most advice on this is either “let your work speak for itself” or “build your personal brand,” and both are bad.
Work does not speak for itself. It cannot. The people deciding your level are not watching you work; they are working. What reaches them is a compressed, second-hand summary assembled from whatever happened to be salient. Contribute nothing to it and it gets assembled without you, from fragments.
But the fix is not self-promotion, and the instinct that recoils from bragging is sound — it recoils because bragging genuinely does not work. It makes people discount everything you say, including the true parts.
The middle ground is reporting. Not selling. The distinction is whether someone could disagree with you.
“I’m crushing it on the migration” is a claim about yourself. “Migration is through phase two, we’re two weeks ahead, the risk is the vendor’s API deadline in March” is a claim about the world. The second is more useful, more credible, and — this is the part people miss — it carries the same information about you.
Practically:
- Send a short regular update to your manager and whoever else has a stake. Weekly or fortnightly, five lines: what moved, what is stuck, what you need. Highest-return habit available, and boring enough that nobody reads it as showing off. It gives your manager ready-made language for the rooms you are not in.
- Give credit precisely. “Priya found the root cause, I rewrote the handler” is generous, specific, and establishes that your accounts are accurate. People who are accurate about others’ work get believed about their own. Vague generosity — “great team effort” — helps nobody.
- Be present where decisions happen. Ask to attend the planning meeting, the client call, the postmortem. Offer to take notes if you need a reason. Most rooms are less guarded than they look.
- Say what you think in those rooms. Once, briefly, on something you know about. Silent attendance builds no case.
- Write things that outlive the moment — a proposal, a decision record, a short analysis. Documents circulate. Meetings evaporate.
Here is the uncomfortable part. Waiting to be noticed is a strategy that works fine for people who are already visible for other reasons — because they sit near the decision-makers, share a background with them, present at the thing everyone attends, or joined at a moment when the team was small. If that is not you, waiting is not modesty. It is opting out of a process that continues without you.
Who actually decides, and is your manager enough?
Your manager is necessary and almost never sufficient. In most places levels get set in a room with several managers, an HR partner, and a fixed number of slots, where each manager advocates for their people against people they have never met. Two consequences follow.
First, your manager needs ammunition, not enthusiasm. They have to describe your case in ninety seconds to peers with no context, against someone else’s ninety seconds. “She’s great, everyone loves working with her” loses to “he took the platform migration when it was failing, landed it a month early, and now three teams depend on what he built.” Give them the second kind of sentence — literally, in an update or a summary before review season, in words they can borrow.
Second, one or two people in that room should recognise your name for a reason — not because you networked at them, but because you did work that touched their world. This is the real argument for cross-team scope: it converts you from an abstraction into a person.
How do you have the conversation with your manager?
Directly, early, and about criteria rather than about wanting it. “I want to be promoted” puts your manager in the position of managing your feelings. “I want to understand what the next level requires here, and where I sit against it” puts them in the position of assessing evidence, which is a job they know how to do.
What you are trying to leave the room with:
- The specific gaps. Not areas for growth — gaps. What, concretely, would someone need to see?
- What closing them looks like. Which project, which scope, which behaviour, observable by whom.
- A timeline. When would this be assessed, and against which cycle.
- Who else is involved in saying yes.
And here is the thing to watch for. “Keep doing what you’re doing” is not an answer. It sounds supportive and it contains no information. If what you are doing were sufficient, the promotion would have happened. Treat it as a prompt to ask again, more specifically:
- “If the decision were made today, what would the argument against be?”
- “What is someone at that level doing here that I’m not?”
- “What would you need to be able to say about me in that room?”
That last one is unusually effective, because it moves your manager from evaluating you to solving a problem with you.
Ask when nothing is at stake — a quiet Tuesday one-to-one gets a more honest answer than a review, where everyone is performing a process.
One boundary worth naming: a promotion and a pay rise are separate conversations, and they do not reliably arrive together. Titles move without money; money sometimes moves without titles. Keep them separate in your own head and in the room — mixing them lets each one become the excuse for not doing the other. If pay is the actual thing you want, that is asking for a raise, and it runs on different mechanics.
Why does everything need to be written down?
Because an agreement you cannot point to tends to dissolve, and usually not through anyone’s bad faith. Managers leave. Reorgs happen. Priorities urgent in March are forgotten by September. A verbal “yes, if you land this, we’ll put you forward next cycle” is real in the moment and gone within two quarters, and the new manager inherits none of it.
The remedy is unglamorous. After the conversation, send an email:
“Thanks for this morning — capturing what we agreed so I’m working to the right thing. The gap is owning delivery end-to-end on something cross-team. I’ll take the vendor migration through Q2. We’ll review in the September cycle. Shout if I’ve got any of that wrong.”
Non-confrontational, easy to correct, and now it exists. It also converts vague encouragement into a specific commitment. If your manager softens it in reply — “well, review is a strong word” — you have learned something important very cheaply.
When should the conversation start?
Months before the decision, because the decision is made months before the announcement.
Most organisations run on cycles you can find out about: a review calendar, a budget year, a planning period when headcount and levels get allocated. Promotions get decided inside those windows, using evidence gathered before them.
So work backwards. If levels are set in November, the argument needs to be visible by September, which means the scope that proves it has to have started delivering by summer, which means you should be having the criteria conversation now. Raising it in October is not early enough to change the outcome — it is early enough only to be told “next year.”
Moments also open unexpectedly: someone leaves and their scope needs an owner, a new team forms. These go to whoever is already visibly adjacent to the work. That is what the preparation is for.
What if the answer is structurally no?
Sometimes no amount of good work changes anything, and it is worth recognising that rather than trying harder for another two years. The structural blocks:
- No headcount at the next level. The level exists, the budget for another one does not. This is not about you and no performance will conjure a slot.
- A manager who will not advocate. Either they cannot — no standing in the room — or they will not, sometimes because you are too useful where you are. Watch what happens rather than what is said. Two cycles of warm encouragement and no movement is data.
- The company is too small or too flat. In a fifteen-person company there may be one job above yours and someone is doing it. No process fixes arithmetic.
Where any of these hold, the fastest route to the next level is usually a different employer. External hiring assesses you against a job description rather than against three years of institutional memory of you as a junior person, which is why moving often produces a jump internal progression would take years to deliver.
That is a normal outcome, not a failure, and not a verdict on the place. Good companies run out of room. Treat it as a planned move rather than a reaction — line up the next thing properly, and handle leaving well, because the people you are leaving are the people who will be asked about you for the next decade. Then give yourself a real run at the first ninety days in a new job, because arriving at a higher level with a clean slate is exactly the advantage you were being denied.
What do you do when you’re told “not yet”?
“Not yet” is genuinely ambiguous. It can mean the timing is wrong and the case is good. It can also mean no, delivered kindly. The way to find out which is to try to make it concrete. A real development plan has:
- Named gaps, not qualities. “You haven’t led anything cross-functional” rather than “more executive presence.”
- A defined proof point. A specific piece of work that, if it goes well, settles the question.
- A date. A cycle, a quarter, a review.
- Reciprocal commitment. Your manager has something to do too — get you into a room, hand you a piece of scope, sponsor the case.
A soft no has none of these and resists acquiring them. You ask what specifically would need to change and get themes. You propose a proof point and it is deferred. You ask for a timeline and get “let’s see how the year goes.” The tell is not disagreement, it is fog — every attempt to make it specific slides off. Do not force a confrontation. Just recalibrate: one vague answer is a busy manager, three across six months is your answer.
If it is real, do the work and then close the loop explicitly: “We agreed this was the gap, here’s what happened, I think it’s closed — do you?” Plans left uncollected expire quietly.
What if you’re too valuable where you are?
This gets discussed less than it should, and it catches conscientious people almost exclusively. You have become the only person who can do something the business needs weekly. Nobody is being cynical — your manager is solving for the next six months, and moving you creates a hole with your name on it. So the promotion becomes expensive to grant, and quietly keeps not happening.
The trap is built out of virtues — being reliable, saying yes, absorbing the messy things nobody else will. The way out is to make yourself replaceable on purpose, before you need to be:
- Write down what only you know. The runbook, the gotchas, the reasons behind decisions that look arbitrary. This is also the most level-appropriate thing you can do — senior people leave systems behind, not just outputs.
- Train a specific person. Not “share knowledge with the team.” One named person who takes it over.
- Hand off your best work first. The instinct is to give away the boring parts and keep what you are known for. That is backwards — what you are known for is exactly the anchor.
- Say the constraint out loud. “I want to make sure reconciliation isn’t a reason I can’t take on more — can we get Dan trained on it this quarter?” Framed that way it is a business problem you are helping solve, not a demand.
Being irreplaceable feels like security. It is the opposite: it is a ceiling made of your own competence.
Is management the promotion you want?
In a lot of places the visible next level involves managing people, treated as the reward for being good at the individual work. That framing has made a great many people miserable.
Management is a different job. The craft you built is no longer what you are paid for. You are paid for hiring, one-to-ones, deciding with less information than you would like, delivering bad news, the slow work of building people who are not you. The feedback loop stretches from days to quarters. Many people exceptional at the work find they do not enjoy any of it, and — the harder part — people who do not enjoy it are rarely good at it, which affects everyone reporting to them.
Before pursuing it, ask yourself honestly: do you enjoy unblocking other people, or tolerate it? Would a good quarter you did not personally produce satisfy you? If yes, go for it properly — and note the evidence needed is different: mentoring, running things through others, handling a conflict well.
If they are not, the next level is not automatically management. Senior individual paths exist in many organisations and are worth asking about explicitly. Where they do not exist, that is a real limitation of the place and it is worth knowing before you take a job that will make you unhappy in order to move up. Wanting the level and wanting the job are different desires, and the gap between them is where a lot of career regret lives.
The TUC publishes material on pay and progression written from the employee side rather than the employer side.
Acas covers pay and wages, which is the conversation that usually follows the one about title.
Frequently asked questions
How long is too long to wait before raising this?
If you have been at your level longer than the people around you were, and nobody has raised progression with you, waiting is no longer adding anything. If you have never had an explicit conversation about what the next level requires, that conversation is overdue regardless of tenure. It is not an aggressive thing to ask.
Doesn’t asking make me look impatient or entitled?
Asking for a promotion can. Asking what the next level requires does not — it reads as someone taking their development seriously, a trait managers actively look for. The difference is whether you are asking for a decision or for information. Ask for information, act on it, and the decision tends to follow.
What if my manager is the obstacle?
First work out whether they lack the power or the will, because the responses differ. If they lack standing, help them by building visibility with the people who have it — through cross-team work, not by going around them. If they will not advocate, going over their head rarely works and reliably costs you the relationship. The realistic options are an internal move to a different manager, or an external one.
Should I say I’m considering leaving to force the issue?
Only if it is true and you are prepared for it to be taken at face value. It changes how you are seen — from someone being invested in to someone being retained — and that outlasts the conversation. It also tends to produce a fast counter-offer rather than structural change, which fixes nothing about why you were stuck.
Does any of this apply if I work remotely?
All of it, more so. Visibility, written updates, being present where decisions happen, leaving a durable record — all matter more when nobody bumps into you. The compensating advantage is that written communication is your native medium: a good update or a clear proposal travels further than corridor presence ever did. Lean into that rather than trying to simulate office visibility.