How far ahead should a roadmap actually plan?

Precisely for thirty days, loosely for a quarter, and as a hypothesis beyond that. Detail past a quarter is usually fiction — the market moves, the role changes, and what you want changes with it. The value of the year-two line is that it makes this quarter's choice legible, not that it will turn out to be right.

What makes a target role specific enough?

You should be able to find five current job adverts for it. If you cannot, the target is a category rather than a role, and every step you derive from it will be vague in the same way. Naming the level as well as the title is part of this — the gap to senior and the gap to staff are different gaps.

What do I do when the roadmap and the day job disagree?

Change one of them deliberately rather than letting the conflict run. Either the roadmap is aimed somewhere your current role cannot get you — in which case the move is the plan — or the day job could support it with a different project, which is a conversation with your manager. Quietly doing both is the option that reliably fails.

How do I know a checkpoint has been met?

By something outside your own judgement: a shipped thing, a review comment, a conversation where someone senior described you differently. Self-assessment drifts, usually downward when you are tired and upward when you are not, and a checkpoint that only you can evaluate stops being a checkpoint within a month.

My trajectory has stalled. Where do I start?

Find out whether it is a visibility problem or a scope problem, because the fixes are opposite. If people cannot see what you do, the answer is to report outcomes where decisions get made; if you genuinely are not doing work at the next level, no amount of reporting fixes it and you need different work. Asking someone senior which one it is usually gets a straight answer.

Should a career change roadmap look different?

Yes — it needs bridge work in the middle. Moving fields directly is hard because your evidence is in the old domain, so the useful roadmap names an intermediate role that uses what you have and touches what you want. The bridge is the part people leave out, and it is the part that makes the change happen in eighteen months rather than never.

content:contentPage.section.career

Career roadmap

How roles progress in practice — the steps between titles, and what usually has to be true before each one.

Last reviewed: 19 August 2026
Length: About 5 minutes
Scope: Maintained, not published. Corrections welcome.

A career roadmap is a 1–3 year written plan that names the role you are aiming for, the skills you need to get there, the projects that build evidence, and the checkpoints where you reassess. Roadmaps beat goals because they tell you what to do next week, not just where to end up. Most career stalls happen because people set vague goals ("get promoted", "switch fields") without a written plan to make the next 30 days unambiguous. The roadmap closes that gap. Keep the next month detailed; sketch the next quarter; treat year 2–3 as a hypothesis you will revise as you learn.

Who this is for

Where it applies.

Planning the path to a senior or staff promotion

List the gap between your current scope and the target level. Map projects that build evidence at each tier. Schedule monthly check-ins with your manager. Most engineering / PM / design promotions follow this pattern — explicit plans land them; implicit hopes do not.

Mapping a career change with bridge work

For larger transitions (engineering → PM, finance → data science), the roadmap covers 6–12 months of focused bridge work plus the actual job-search phase. Visible artifacts at each milestone make the change legible to recruiters when you start applying.

Recovering from a stalled career trajectory

When growth has stalled 12+ months, the roadmap forces a decision: stay and engineer the next move internally, or switch companies. Both can work. Drift — neither — is what loses years.

Writing the version you will actually re-read

A roadmap nobody opens again is a document, not a plan. Keep it to one page, put the next thirty days at the top where you will see them, and give it a standing date in the calendar. The format matters less than whether the next action is visible without scrolling.

In order

How it works.

Name the target role specifically
Title, level, industry, and 2–3 example companies. "Staff PM at a mid-stage SaaS company" is a target. "Something more strategic" is not.
List the gap honestly
What does the target role expect that you do not yet demonstrate? Skills, scope of ownership, mentorship range, public visibility. Be specific; vague gaps produce vague plans.
Schedule the next 30 days unambiguously
Pin three specific actions in the next month — a project to scope, a course to start, a person to ask for a 15-minute conversation. The 30-day plan is the part that has to be unambiguous.
Sketch the next quarter loosely
Outcomes you expect from the 30-day plan, what they unlock, the next set of actions. Sketch — do not over-engineer. Quarterly plans always need adjustment.
Treat year 2–3 as a hypothesis to revise
Long-horizon plans are useful as direction, not commitment. Review monthly; rewrite quarterly; full reassessment annually. Plans that survive contact with reality are the ones that get rewritten as reality changes.

Worked

Worked illustrations.

Constructed to show the shape of the decision, not reported cases. The figures are illustrative.

A senior engineer planning a path to staff

Identifies gap: cross-team scope, mentorship, public visibility. 6-month plan: own one cross-team initiative, mentor two juniors, write three internal blog posts. Promoted at month 9 with clear evidence at each gap area.

A teacher planning a career change to instructional design

12-month roadmap: 4 months bridge work (course, capstone curriculum, LMS certification), 4 months portfolio building, 4 months active search. Lands first instructional-design role at month 11; comp drops 10% but trajectory is steeper.

Asked often

Questions people bring here.

How far ahead should a roadmap actually plan?: Precisely for thirty days, loosely for a quarter, and as a hypothesis beyond that. Detail past a quarter is usually fiction — the market moves, the role changes, and what you want changes with it. The value of the year-two line is that it makes this quarter's choice legible, not that it will turn out to be right.
What makes a target role specific enough?: You should be able to find five current job adverts for it. If you cannot, the target is a category rather than a role, and every step you derive from it will be vague in the same way. Naming the level as well as the title is part of this — the gap to senior and the gap to staff are different gaps.
What do I do when the roadmap and the day job disagree?: Change one of them deliberately rather than letting the conflict run. Either the roadmap is aimed somewhere your current role cannot get you — in which case the move is the plan — or the day job could support it with a different project, which is a conversation with your manager. Quietly doing both is the option that reliably fails.
How do I know a checkpoint has been met?: By something outside your own judgement: a shipped thing, a review comment, a conversation where someone senior described you differently. Self-assessment drifts, usually downward when you are tired and upward when you are not, and a checkpoint that only you can evaluate stops being a checkpoint within a month.
My trajectory has stalled. Where do I start?: Find out whether it is a visibility problem or a scope problem, because the fixes are opposite. If people cannot see what you do, the answer is to report outcomes where decisions get made; if you genuinely are not doing work at the next level, no amount of reporting fixes it and you need different work. Asking someone senior which one it is usually gets a straight answer.
Should a career change roadmap look different?: Yes — it needs bridge work in the middle. Moving fields directly is hard because your evidence is in the old domain, so the useful roadmap names an intermediate role that uses what you have and touches what you want. The bridge is the part people leave out, and it is the part that makes the change happen in eighteen months rather than never.

Worth knowing

Small things that help.

Pin the target specifically — vague targets produce wandering plans.
The next 30 days must be unambiguous; everything beyond can be sketched.
Review monthly; rewrite quarterly; full reassessment annually.
A plan that never changes is a plan you stopped updating, not a perfect plan.
Drift is the enemy. A wrong plan you adjust beats no plan you stick with.
If you cannot find five current adverts for your target role, the target is a category and not yet a role.
Checkpoints need evidence somebody else can see — a shipped thing, a review comment, a changed description of you.

ClearHire Editorial

Written to be corrected. If something here is wrong, say so and it changes.