Getting Promoted Roadmap
A getting-promoted roadmap is a sequence, not a waiting game: build the case before you ask, gather the proof, and time the conversation. Here is the five-step path from invisible to obvious.
Promotion is not a reward for time served. It is a risk decision someone else makes about you, and the question in their head is not "has this person earned it" but "can I picture this person doing the job, and will it be awkward if I am wrong." That is a much more answerable question than it sounds, and it is answerable in advance.
This roadmap is the order that works: decide what you are actually asking for, get known for one thing, do work that leaves a mark, build the case with evidence, make the ask, and handle both the setback and the step up. Work through it in sequence, or jump straight to the stage you are stuck on right now.
1. Decide what you are actually asking for
Most stalled promotion attempts are two different asks wearing one coat: more money, or a different job. They are negotiated differently and they need different evidence, so name which one you want before you build anything. Making a career plan when you feel stuck is the place to start if the answer is not obvious yet, because it forces the goal into a sentence a stranger could check.
2. Get known for one thing before you get loud
Visibility is not volume. The people who get promoted are usually known for one specific thing - the person who fixes the messy handoffs, the person who can be trusted with the difficult client - and that reputation travels into rooms you are not in. Building a personal brand without feeling like a salesperson and building executive presence without faking it are the two guides for this stage; pick one thing and let the rest of your work support it.
3. Do work that leaves a mark
Effort is invisible; outcomes are not. The move is to take on work that has a visible before and after, and to write the before down while it is still true. Writing a 30-60-90 day plan gives you a structure for turning a new responsibility into a documented result, and delegating without micromanaging is what buys you the hours to do it - the work you hand off is the work that stops being your ceiling.
4. Build the case with evidence
A promotion case is a document, not a feeling. Collect the outcomes with dates attached, then write them the way a decision-maker reads: what changed, what it was worth, and what you did that someone else would not have. Writing a self-evaluation that reads like evidence is the worked example, and naming the strengths you can defend plus the Interview Story Bank keep the same evidence ready for the interview that follows the decision.
5. Make the ask
The ask is the last step, not the first, and it is a conversation rather than a request. Building the case before you ask walks the sequence - the timing, the framing, and the question to ask when the answer is not yet yes. If the promotion comes with a number, the raise scripts and timing guide covers the money half of the same conversation.
6. Handle the setback, then step into the role
Being passed over is information about timing and evidence, not a verdict on your worth, and it has a recovery plan: the five-step recovery plan for being passed over. If the feedback arrives as a formal plan instead, handling a performance improvement plan without panicking is the same skill pointed at a harder deadline. And once the title lands, becoming a manager without waiting to be noticed and giving feedback without sounding like a critic are the first two things the new role actually asks of you.
How to run this roadmap
Give the sequence one quarter, one stage a fortnight, and write down the signal you expect to see by the end of each stage. If the signal does not show up, change that stage's variable rather than the whole plan.
| Stage | What you actually do | The signal to look for |
|---|---|---|
| Decide the ask | Write down whether you want more money or a different job, and put the answer in one sentence a stranger could check. | You can say which of the two you are asking for without hedging. |
| Get known for one thing | Pick the single thing you want to be the person for and do it visibly for a month. | Someone outside your team describes you using that thing. |
| Leave a mark | Take on work with a visible before and after, and write the before down while it is still true. | You have one completed outcome with a date attached. |
| Build the case | Turn the outcomes into a one-page document: what changed, what it was worth, what you did that others would not have. | A decision-maker can read the case in two minutes and repeat it back. |
| Make the ask | Ask the question about the role, not about yourself, and write down the answer verbatim. | You leave the conversation with a yes, a date, or a specific gap. |
What good looks like
You are running the roadmap correctly when these are true. If two or more are false, you are waiting to be noticed rather than building a case.
- You can name the one thing you want to be known for.
- You have at least one completed outcome with a date attached.
- The case fits on one page and a stranger could repeat it back.
- You know whether you are asking for money or for a different job.
- The ask is scheduled, not hoped for.
- If you were passed over, you left with the specific gap written down.
Where people get stuck
Stuck because the work speaks for itself. It does not. Work is evidence, not an argument - someone still has to make the case, and if you will not, the decision defaults to whoever is most visible. Writing down what changed is not bragging; it is the raw material the decision gets made on.
Stuck because the ask feels like a confrontation. That is usually a framing problem. Ask about the role rather than about yourself: what would have to be true for this to be a yes, and by when. A question about the job is a planning conversation; a demand about you is a confrontation.
Stuck because the last no is still open. A no with no follow-up date is a closed door you keep knocking on. Go back once, ask what would have to be true, write it down, and put the review date on the calendar. The second conversation is a different conversation.
Common mistakes this roadmap is designed to prevent
- Waiting to be noticed. Promotion is not a reward for tenure; it is a risk decision someone makes about you. If the decision-maker cannot picture you in the role, the work you did is invisible no matter how good it was.
- Building the case in your head. A promotion case is a document, not a feeling. If you cannot point to the outcome and the date, you are asking for a favour rather than making an argument.
- Asking before the evidence exists. The ask is the last step, not the first. Ask too early and you spend your one conversation on a no, and the next ask is harder because the answer is already on record.
- Treating the setback as a verdict. Being passed over is information about timing and evidence, not about your worth. Ask what would have to be true, then go build that thing.
- Confusing visibility with noise. Being loud is not the same as being known for something. Pick the one thing you want to be the person for, and let the rest of your work support it.
Promotion is a sequence, not a moment: decide what you want, get known for one thing, do work that leaves a mark, build the case, then ask. Most people skip straight to the ask and then wonder why the answer was no.
If you want the whole set of guides in one place, start from the Start Here guide and pick the stage you are in.
Continue with another roadmap: Interview Prep Roadmap or Career Pivot Roadmap or Job Search Roadmap or Labor Market Roadmap or Resume & Applications Roadmap or Networking & LinkedIn Roadmap or AI & Job Search Roadmap or Salary Negotiation Roadmap or Career Planning Roadmap or Strengths & Self-Assessment Roadmap - or start from the Start Here guide for the full index.
Quick answers
Short answers to the questions this piece gets asked most.
How do I get promoted without being seen as pushy?
Separate the work from the ask. Spend the months before the conversation making one thing visibly better and writing down what changed, then make the ask a question about the role rather than a demand about you. Pushy is asking with no evidence; direct is asking with it.
How long should I wait before asking for a promotion?
Long enough that you can point to a completed outcome the decision-maker already knows about, and not so long that the next review cycle passes you by. If you cannot name the outcome and the date, you are early. If you can name three, you are late.
What do I do if I am passed over?
Ask what would have to be true for the answer to be yes, write it down in the room, and set a date to check it. Being passed over is information about timing and evidence, not a verdict on your worth - but it only becomes useful if you leave the conversation with the specific gap.
Should I take a counteroffer instead?
A counteroffer fixes the number and leaves the reason you looked untouched. If the reason was money alone, it can work. If the reason was scope, growth or a manager, the counteroffer buys you time rather than solving anything, and the same conversation returns in a year.
Read next:
LaunchPath Careers by UFO Chaser® helps job seekers build a strategy-first job search. Learn more at LaunchPathCareers.com.
Comments
Post a Comment