A career roadmap that exists only as a memory from one good conversation evaporates by the time the next review cycle comes around. It needs to be specific enough to act on between now and then, and durable enough that both people can open it in three months and immediately remember where things stood. That takes more structure than a vague promise to talk about growth and less rigidity than a fixed promotion date neither side can actually guarantee.
What changed in 2026
- Published career ladders became more common. More companies now document explicit leveling criteria internally, giving roadmap conversations a shared reference instead of each manager improvising the bar from scratch.
- AI-assisted gap analysis tools appeared. Some tools now suggest learning resources mapped to a named skill gap, though judging which gaps actually matter for a given person still needs a manager who knows the work.
- Roadmap check-ins moved to a quarterly cadence at more companies. Following the broader shift toward continuous feedback, fewer teams treat the annual review as the only moment a roadmap gets discussed.
- More roadmaps explicitly name an individual-contributor track and a management track as separate, equally valid paths. Assuming everyone wants the same climb is a fading default.
The three inputs a roadmap needs
A useful roadmap is built from three things: where the person stands today, where they want to go, and what specifically separates the two. The first input often comes from something like a skills matrix, which turns "pretty strong on backend" into a specific, checkable list. The second comes directly from the person, not assumed by the manager. The third is the actual plan.
What belongs in the roadmap
| Component |
Question it answers |
| Destination |
What is the next level or lateral goal, in concrete terms |
| Gap analysis |
What specific skills or scope separate today from that destination |
| Milestones |
What observable progress looks like along the way |
| Support and resources |
What the manager and company will actually provide to help close the gap |
| Review cadence |
When this gets revisited, and by whom |
Running the planning conversation
Ask what the person actually wants before proposing a path for them. A roadmap handed down as a fait accompli, however well-intentioned, tends to reflect what the manager thinks the person should want more than what they do. Be honest about constraints too — headcount, level caps, and timing factors nobody in the room controls — rather than implying a guarantee that cannot be kept. A vague promise a manager cannot deliver damages trust more than an honest constraint stated plainly.
Individual contributor track versus management track
The fork is real and both paths are legitimate destinations, not a consolation prize for the one that did not lead to management. The most common early mistake is a roadmap that defaults to a management track without ever asking, simply because that used to be the only visible ladder. Name both explicitly and let the actual answer come from the person, not from habit.
Keeping the roadmap alive
A roadmap that only gets reopened at the annual review is a document, not a plan. Tie it into regular 1:1s, revisit it on an explicit cadence, and treat it as something to adjust as priorities shift rather than something to discard the moment reality does not match the original draft.
Common mistakes
- A vague destination. "Grow into a stronger engineer" cannot be checked against later. Name the level, scope, or role explicitly.
- A plan with a date but no gap analysis. A promotion timeline with nothing concrete backing it sets up disappointment on schedule.
- A roadmap owned entirely by the manager. Without real input from the person on direction, it rarely survives the first time priorities shift.
- Treating the individual contributor path as the fallback. Framing it that way discourages a path that, for many people, is the right one.
FAQ
How often should a career roadmap be updated?
Quarterly is a common cadence, tied to regular 1:1s rather than saved only for the annual review. Priorities and interests shift faster than an annual document can track.
Should a roadmap include a specific promotion date?
Be cautious with firm dates unless the organization can actually back them. A roadmap tied to closing specific gaps, with milestones, holds up better than one built around a date that depends on factors outside the plan.
What if the person and manager disagree about the destination?
Surface it directly rather than defaulting to what the manager assumed. A roadmap built around a destination the person did not choose rarely sustains real effort.
Does every team member need a formal roadmap?
Not with equal formality. Someone actively working toward a level change benefits from real structure; someone content at their current level still deserves a lighter version so growth options stay visible.
Where to go next