7 September 2026
Last time, this series looked at the rating moment — the small act of judgement that turns a vocabulary into data, and what it takes to make the resulting number honest enough to plan on. Suppose, for a moment, that the work has been done. The framework is current, the managers have compared notes, the ratings arrive with evidence attached and a distribution a statistician would not laugh at. The organisation now knows something true about its own capability. This post is about the week after that — the quiet, dangerous pause in which most skills programmes stall.
Because there is a version of success that looks exactly like failure with better graphics. The assessment closes, the dashboard fills, leadership nods appreciatively at the heat map — and nothing in anyone’s working week changes. Six months later the data has gone stale, the next cycle asks everyone to rate again, and people who watched nothing happen the last time answer accordingly. The distance between an honest number and a different Tuesday is where the whole endeavour is decided.
A Gap Is Not an Instruction
The first mistake is treating the gap analysis as a to-do list. It is not; it is a list of facts. An honest assessment of a workforce will surface far more gaps than any organisation can close, and the instinct to respond to every red cell with a development action produces four hundred initiatives, none of them resourced, most of them abandoned by March. A gap only becomes a priority in the light of what the business is actually trying to do next — which is why the most useful hour after an assessment is spent reading the skills analytics with the strategy document open beside it, not admiring the coverage.
Three questions do most of the sorting. Which gaps sit directly in the path of something the organisation has committed to — a new service line, a system migration, a succession risk with a date on it? Which are cheap to close because the appetite is already there and only the opportunity is missing? And which are simply tolerable — real, visible, and not worth anyone’s quarter? Deciding on purpose not to act on a gap is a perfectly respectable outcome. It is the undeclared version, where everything is nominally a priority, that quietly teaches the workforce the numbers lead nowhere.
From Gap to Goal, Named and Dated
Once the shortlist exists, each entry has to survive a conversion: from an observation about a person to a commitment with that person. This is the point where the data either becomes a training goal — specific, owned, dated — or evaporates into the general aspiration to ‘develop our people’. The difference is almost embarrassingly concrete. ‘Improve stakeholder management’ is a wish. ‘Run the next two client steering sessions, with a debrief afterwards, and reassess in November’ is a goal an employee can actually walk toward, and can tell whether they have reached.
The route matters as much as the destination, and the route depends on will as much as skill. A gap a person is eager to close calls for stretch and opportunity; the same gap in someone privately relieved to leave it alone calls for a different conversation entirely. This is what a skill-will conversation is for — the point where the organisation’s shortlist meets the employee’s own ambitions, and the goal gets chosen with the person rather than assigned to them. Goals arrived at that way have a habit of surviving contact with a busy quarter. Goals issued from a spreadsheet do not.
Development That Fits Inside a Working Week
Most development plans are written for an imaginary calendar — one with slack in it. The real one has delivery deadlines, a team member on leave, and a manager with forty minutes of discretionary attention. Development that actually happens is built for that calendar: small, adjacent to real work, and cheap to start. A stretch task inside an existing project. A fortnightly half-hour where the skill is used in front of someone who can comment. Structured feedback captured near the moment it happened, while the example is still warm, rather than reconstructed at review time from memory and generosity.
Courses still have their place — some capabilities genuinely begin in a classroom — but a course is an ingredient, not a plan. The pattern that works is unglamorous: a little formal input, followed quickly by a place to apply it, followed by someone noticing. An organisation that sequences those three things inside the working week will outrun one with a better content library every time, for the same reason this series gave when it looked at practice: capability is built between courses, in the work, or it is not built at all.
Close the Loop While It Still Means Something
The last step is the one most programmes skip: going back. A goal that was named and dated deserves a reassessment against the same skill, by the same standard, at the next development review — not as an audit, but as the moment the loop closes. Did the number move? If it did, the organisation has just produced its most persuasive artefact: a gap that was found, worked on, and visibly closed. If it did not, that is worth knowing too, while the plan is still warm enough to adjust.
The previous post in this series argued that ratings which go nowhere are never wrong, because nothing ever tests them. The loop is the test. And it pays for itself in an unexpected currency: honesty. When a two becomes a three because of something everyone can point to, the next assessment cycle changes character — people tell the truth about their gaps to a system they have watched do something useful with the truth. Candour, it turns out, is not a cultural trait. It is a learned response to being taken seriously.
The Dashboard Was Never the Point
The output of a skills programme is not a report. It is a workforce that can do more this quarter than it could last quarter, and knows it — and every layer this series has examined exists in service of that. The framework decides what can be seen. The rating decides whether what is seen is real. This is the layer where either of those comes to matter: the short, deliberate path from an honest number to a named goal, a changed week, and a closed loop.
The gap between knowing and doing has been this series’ quiet theme from the beginning, and it applies to organisations just as it applies to the people in them. A truthful dataset that changes nothing is knowledge without practice. The remedy is the same at every scale: pick something specific, start it soon, and go back to check.
