Career Pathing

What is a career path, and what is it not?

A career path is a described route: a starting role, the roles it can lead to, and the criteria somebody would be expected to meet along the way. It is a statement about the organization, not about a person. The failure mode is that it gets read the other way. An employee shown a path reasonably infers that they are on it, that meeting the criteria produces the move, and that somebody has agreed to this. Nobody has. The damage lands on a manager who made no promise and now has to explain a decision they were never party to, usually at the point the employee is most invested in the outcome. That is why the framing belongs inside the document, stated where the path is read, rather than left to a conversation that may never happen.

Why does a dual ladder collapse into a single one?

A dual ladder offers an individual contributor route advancing in parallel with a management route, so somebody with depth is not obliged to acquire reports in order to progress. On paper both exist. In practice the ladder collapses whenever the senior individual-contributor rungs carry no real scope, no authority over anything that matters, and no pay matching the management rung beside them. People read the organization rather than the diagram. If nobody at the senior technical level is in the rooms where decisions get made, the message is unmistakable whatever the map says, and the second ladder becomes decoration that costs credibility instead of adding a route. The useful test is not whether the rung exists, but whether anyone has taken it and been treated as senior afterwards.

What does a lattice show that a ladder cannot?

Drawn as a ladder, a career map shows upward steps inside one function, which is the smaller part of what actually happens. The moves that widen somebody's range most are frequently sideways, into an adjacent function where existing knowledge transfers and the work is unfamiliar. A map rendering progress as height makes those look like a detour at best and a step down at worst, so people do not ask for them, and the employer loses the transfers that would have been cheapest to make. Drawing the map as a lattice, with routes running across as well as up, is partly a diagramming decision and mostly an honest one, because it stops the document implying that only one direction counts. Sideways routes need criteria too, or they read as available to whoever is already known.

What makes a path credible rather than aspirational?

Two properties carry most of the weight, and the first is that somebody can assess themselves against the criteria without asking anyone. Criteria needing a conversation to interpret hand the decision back to whoever holds the conversation, which is the situation the map existed to improve: people comfortable asking get an answer, people who are not assume the route is closed to them. The second is that the route has been travelled. A path with named people who have actually made that move, and who can be approached, is a different document from one drawn on a whiteboard, because the reader can verify it. Where nobody has made a move, saying so plainly beats listing it as though it were routine. One hypothetical route discovered to be hypothetical damages every other route on the page.

The third property quietly decides whether any of this works, and it is not written on the map at all. A manager who loses a strong performer to another team absorbs the gap, runs the replacement search and carries the delivery risk. If nothing in how their own performance is judged recognizes that, the rational response is to discourage the move without ever refusing it. Routes then exist and go unused, and the reason is invisible in every report the employer runs. Crediting a manager for a released move, and recording it where their own contribution is assessed, is the change that turns a published map into a used one. Employers watching internal movement in their [HR analytics software](/hr-analytics-software) without ever looking at which managers release people are measuring the outcome and ignoring the mechanism.

Why does a career map go out of date faster than the roles it describes?

Because it depends on structure, and structure changes for reasons that have nothing to do with careers. A reorganization merges two functions, and a route drawn between them now leads to a team that no longer exists. A role is retired, and every path terminating in it terminates nowhere. A remit moves between groups, and a lateral route that used to broaden somebody now leads to work they already do. None of these are errors when they happen; they become errors the following month, when the map still shows them and nobody has told the reader. The document does not announce that it is stale, which is what makes this failure different from most: it keeps presenting itself with the authority it had when it was accurate.

The cost is not the wrong route, it is what the wrong route teaches. An employee who follows a path to a team that was dissolved concludes the whole document is decorative, and applies that conclusion to the routes still correct. Credibility is lost across the map rather than locally, which is why a small amount of stale content does disproportionate damage. The cheap discipline is to attach the map to something that already changes when the organization does, so a structural change surfaces as a list of routes to check rather than as nothing at all. Where reporting lines are maintained in [org chart software](/org-chart-software), a change there is the natural trigger. Naming an owner who hears about reorganizations before they are announced is the other half.

How do you say a path is not a promise without making the document useless?

Two ways of handling it both fail. Saying nothing lets every reader supply their own assumption, and the assumption people supply is the favorable one, so the employer ends up having made a commitment it never wrote down. Saying it defensively, in the register of a disclaimer, tells the reader the document was drafted to protect the employer, and a map opening with what it does not mean will be read as an admission that it means very little. The useful version is neither. It states what the document supplies, which is the routes and the criteria, and what it does not, which is a decision about any individual, and then says where that decision does get made and by whom. That reads as information rather than as protection.

Placement matters as much as wording. A qualification sitting in an introduction nobody reads does not survive contact with the page somebody was actually sent, since readers arrive at a specific route from a search or a link rather than at the front of the document. The framing therefore belongs on the route itself, next to the criteria, where the expectation is being formed. It also has to match what managers say out loud, because a careful document and an enthusiastic conversation net out as a promise. Agreeing the language before publication, so the person holding a career conversation and the page they refer somebody to describe the same thing, prevents most of the disputes that otherwise arrive later, once the criteria are met and no role has opened.

What does a published map change about the conversation an employee actually has?

Its main effect is to change who has to start the conversation and what it is about. Without a map, an employee raising the subject is asking their manager for an opinion about their prospects, which is an uncomfortable request many people never make, and which produces an answer shaped by the relationship rather than by anything checkable. With one, the employee arrives having read the criteria for a route they are interested in, and the discussion is about evidence and gaps rather than about whether they are the sort of person who gets promoted. That is a smaller and more repeatable conversation, and one a manager who is not naturally good at career discussions can still hold competently, because the structure is supplied rather than improvised.

What the map cannot supply is a manager's willingness to be honest about the gap, and clear criteria make an evasive answer more conspicuous rather than less. An employee told twice that they are close, who then sees the criteria unchanged, learns something the document never intended to teach. The counterpart discipline is recording what was discussed and what was agreed somewhere the next conversation starts from, usually alongside the rest of the assessment record in [performance management software](/performance-management-software), so the second conversation is not a fresh negotiation of the first. Employers that publish routes and leave the conversations entirely unstructured tend to find the map is used most by the people who needed it least.