Last time, this series watched a second assessment cycle land beside the first and turn a static heat map into a trend — proof, skill by skill, of whether a development approach actually works. That was still a story about individuals: one person’s rating, compared with itself, six months apart. Almost every organisation stops there, because a single trajectory is a satisfying, legible thing. It answers one question well: is this person getting better at this skill? It was never built to answer the question sitting one level up.
That question belongs to the organisation, not the person: where does capability actually concentrate, where is it thinning without anyone deciding it should, and who is quietly carrying a critical skill that nobody has noticed depends on exactly one person? A single trajectory cannot see any of that. A hundred trajectories, read together rather than one at a time, can — and the view that appears looks less like a performance report and more like a talent map.
One Trajectory Is a Person. A Hundred Are a Map.
Line up every individual’s skill trend against the same axis and something appears that no single line can show: clustering. Three people rising together in the same critical skill is a pipeline. Three people flat in that same skill, all reporting to the same manager who retires next year, is a very different pattern — and it is invisible from inside any one of their individual reviews, because each manager only ever watches their own line move, or not, in isolation. Nobody in that chain of one-to-one conversations is lying or even withholding anything; the pattern simply does not exist at the scale any single conversation operates at.
This is the argument for building the skills analytics view at the level of the organisation rather than leaving it as a dozen separate spreadsheets belonging to a dozen separate managers. The aggregate is not simply a bigger report. It is a different instrument, built to answer a question the individual view was never asked — and, tellingly, it is usually the first time anyone has actually looked at the whole workforce’s trajectories side by side rather than one row at a time.
The Bench That Looks Fine Until You Look Twice
Succession planning has traditionally run on a name in a box: a critical role, and the two or three people theoretically ready to fill it. Two cycles of trend data quietly force that box open, because a name sitting inside it says nothing about whether the person’s relevant skills are rising, flat, or drifting the wrong way while everyone assumes the succession question is already handled. A bench that was true in March and never checked again is not a plan. It is a memory of one, and organisations tend to discover the difference at the worst possible moment — when the role suddenly needs filling and the assumed successor turns out to have been flat in the relevant skill for a year.
The uncomfortable finding, when organisations actually look, is usually concentration rather than absence: a critical capability sitting inside two or three trajectories instead of being distributed at all, each of those trajectories ordinary and unremarkable on its own, and none of them backed up by a fourth. Position asks whether the skill exists somewhere. Trend, read across the bench rather than down a single row, asks the harder question — whether it exists in more than one place, and whether that is getting better or worse.
Rising, Flat, and Falling: Three Different Conversations
Once trajectories are grouped rather than read one at a time, three shapes do almost all of the work. A rising line in someone who wants more of the skill is the easy case — succession and stretch, decided together in a genuine skill-will conversation rather than assumed from the chart. A flat line is not automatically a problem; flat in a skill the role no longer needs is simply accurate, and chasing it spends a quarter nobody had to spend. The mistake is treating all three shapes the same way, which is what happens by default when nobody has separated them out first.
The line that deserves the room’s full attention is the falling one in a skill the organisation still depends on, because it rarely announces itself as urgent. Nobody schedules a crisis meeting over a two that used to be a three; the number simply drifts while the work that once exercised it moves to someone else. Turning that finding into a dated training goal is exactly the mechanism this series described two posts ago — it only helps if something is still watching for the drift in the first place.
What the Aggregate View Changes Upstairs
A succession conversation built on individual memory tends to produce the same three or four names every year, because those are the people leadership happens to remember clearly. A succession conversation built on aggregated trend data produces a different, occasionally uncomfortable list — the quietly rising person two levels down whom nobody has mentioned in a planning meeting, and the well-regarded name whose relevant trajectory has actually been flat for two cycles running. Neither of those findings is visible from memory alone, however good that memory is; both are sitting in data the organisation already collected and simply never grouped.
It also changes what shows up in the development review itself, because a manager holding that conversation with an aggregate view in hand is negotiating from evidence rather than impression. “I think they’re ready” becomes “these three skills have risen two cycles running, against evidence, and this one hasn’t moved” — a sentence a succession committee can actually act on, rather than one it has to take on faith.
The Org Chart Was Never the Real Map
The org chart shows who reports to whom. It has never shown where capability actually concentrates, or where it is thinning without anyone deciding that it should. Two cycles of honest, evidenced skills data, read across people rather than down them one at a time, comes closer — not a replacement for judgement about succession, but the layer of evidence that judgement has usually had to do without. It will not draw the org chart’s replacement on its own, but it will tell the room, in its own numbers, exactly where that chart is quietly lying.
The practical instruction is short, and it is the same one this series keeps arriving at from a different direction. Do not stop at the individual trajectory. Group it, look for concentration and thinness rather than just movement, and let the bench be redrawn by what the data actually shows — including the name nobody would have thought to put there first.
