Last time, this series followed an honest skills rating into the working week — how a gap becomes a named goal, how a goal is built to fit a real calendar, and why the loop only counts once someone goes back to check whether the number moved. A closed loop is a satisfying thing: a gap found, worked on, and visibly narrowed. It is also, statistically speaking, an anecdote. This post is about what appears when the cycle runs again across a whole organisation — a second snapshot, and with it the first honest answer to the question leadership has been asking since the programme began: are we actually getting better?

Most organisations still read skills data the way they read a photograph. Where do we stand? What is covered? How much of the map is red? Those are position questions, and the first assessment answers them well enough. But a heat map is a photograph of a moving object. Two organisations can produce identical heat maps while travelling in opposite directions — one improving steadily into its gaps, the other quietly decaying out of its strengths. The snapshot cannot tell them apart. The second snapshot can, and nearly everything interesting about a skills programme lives in the difference between the two.

One Number Is a Position. Two Are a Direction.

The first cycle tells an organisation where it stands, and that knowledge is genuinely valuable — expensive, hard-won, and ageing from the moment it arrives. The second cycle answers a different kind of question: what moved. The moment a second honest rating lands beside the first, the data acquires a shape rather than just a state. Gaps that were worked on and closed. Strengths that faded because nobody exercised them — capability decays where it is not used, a fact every snapshot politely conceals. Teams that convert development goals into movement, and teams that accumulate development plans the way a drawer accumulates cables.

This is also the moment the previous post’s discipline pays out. The training goals that were named and dated last quarter stop being commitments and become hypotheses — each one a small, testable claim that a particular action would move a particular number. The reassessment is the result coming back from the lab. An organisation that ran the loop properly does not need to wonder whether its development approach works; it can read the answer, skill by skill, in its own data.

Comparing Like With Like

A delta, however, is only as honest as the two ratings it stretches between — and there are several well-intentioned ways to break one. The comparison holds only if the second rating is made against the same skill, by the same standard, with the same kind of evidence as the first, ideally in the ordinary rhythm of a development review rather than as a special occasion. Rate a skill one way in March and another way in September and the resulting movement is fiction, whichever direction it points.

The most common breakage is the tidy-up. Between cycles, someone improves the framework — renames a skill, splits it in two, sharpens a level description — and in doing so quietly cuts the thread that made comparison possible. The framework post in this series argued for taxonomies that stay small and current, and that still holds; the refinement simply belongs at the cycle boundary, declared, so everyone knows where the line breaks. The other quiet threat is rater turnover: a new manager reads the scale differently, and a team appears to improve or collapse on the strength of a personnel change. The anchor for both is evidence — structured feedback captured close to the work gives the second rating the same footing as the first, whoever happens to be holding the pen.

What Direction Does to Decisions

Once trend is visible, the skills analytics stop being a league table and start being a time series, and decisions change accordingly. Development budget can be aimed where it demonstrably works: at the gaps that move when pushed. A gap that has absorbed two cycles of effort without moving is not proof that the people are hopeless — it is usually proof that the method is wrong, most often a course where practice was needed. The trend does not just show progress; it audits the development approach itself.

Direction also reads differently against ambition. A skill rising in a person who wants more of it is a succession plan writing itself; the same skill flat in someone whose energy points elsewhere is a signal to stop pushing and have the more honest conversation a skill-will view exists for. And the trend surfaces the one risk no snapshot can: the critical capability that is quietly sliding because the work that once exercised it has moved elsewhere. Position flags the gap you have. Direction flags the gap you are about to have — while there is still time to do something cheaper than a crisis.

The Report That Changes Upstairs

The second snapshot also changes what L&D sends up the stairs. The traditional report is a record of activity — enrolments, completions, hours of learning consumed — numbers about effort, silent on results. A trend report reads differently: these gaps were found, these were prioritised, this is what moved, and here is the capability the organisation has this quarter that it did not have last quarter. In June this blog made the business case for skills-based L&D in prospective terms — investment and expected return. The trend line is the retrospective version: the case proving itself, quarter by quarter, in the organisation’s own numbers.

And it compounds the honesty dividend this series keeps encountering. People are candid with a system they have watched do something useful with the truth; executives are no different. A leadership team that has seen capability visibly move stops treating the skills conversation as an L&D enthusiasm and starts treating it as operating data — which is, in the end, what all the careful work on frameworks and ratings was for.

Position Is a Fact. Direction Is a Verdict.

Each layer this series has examined hands its result to the next. The framework decides what can be seen. The rating decides whether what is seen is real. The loop decides whether any of it changes a working week. The trajectory is where all three face judgement — the layer at which the programme itself is rated, by its own data, with no room for appeal. A snapshot can flatter or alarm, depending on the lighting. Only the trend can say whether the machinery underneath is actually working.

The practical instruction is short. Run the cycle again. Compare like with like, and be honest about where the line breaks. Read direction, not just position — and report movement, not activity. The still photograph was never the point. The film is.