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.
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.
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.
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.
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 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.
26 August 2026
Last time, this series looked at the framework underneath — the taxonomy that quietly decides what an organisation is able to see about its own capability. But a vocabulary only becomes data when somebody applies it to a person. Someone sits down, reads a skill description, thinks about a colleague or about themselves, and picks a number. That moment — small, routine, repeated thousands of times a year — is where every dashboard, every gap analysis and every workforce plan ultimately comes from.
It is also the least examined part of the whole apparatus. Organisations will spend a quarter designing a framework and an afternoon deciding how it gets rated, then treat what comes out as measurement rather than judgement. This post is about that moment: what a skills rating actually is, the two directions it reliably drifts in, and what makes one honest enough to plan on.
A skills rating looks like a measurement. It arrives as a number on a five-point scale, it averages neatly, and it renders beautifully in a bar chart. But it is not a measurement in any sense a scientist would recognise. It is a claim — one person’s judgement about capability, made at a particular moment, on whatever evidence happened to be within reach that week. The number is a compression of that judgement, and like every compression it discards the part that mattered most: the reason.
This is not an argument against rating people. Judgement is unavoidable and often rather good, and organisations have run on it for a century. It is an argument against forgetting what the number is made of. The moment a rating is treated as a fact, it stops being questioned — and an unquestioned claim will sit happily in a skills analytics view for two years, shaping succession shortlists and hiring briefs, long after the person it described has moved on. Everything downstream depends on remembering that each cell in the grid was once a sentence somebody said out loud.
Ratings drift in two directions, and most organisations manage both at once. The first is generosity. Marking a colleague down is unpleasant, the conversation is awkward, and a three feels like a criticism where a four feels like encouragement. Nobody sets out to inflate anything; each individual four is defensible and kindly meant. Two cycles later, ninety per cent of the workforce is proficient or better in almost everything, the gaps have vanished from the report, and the only honest conclusion available from the data is that no development is required anywhere.
The second direction is fear, and it usually shows up in self-assessment. If people suspect a rating will be read as a verdict — that admitting to a two will cost them a project, a promotion or a place on the list — they will rate themselves defensively, and the safest answer is always the middle. What makes a skill-will conversation work is precisely the opposite reflex: the willingness to say plainly that you are not there yet and would like to be. That candour is a function of consequence, not of scale design. Nobody tells the truth about a gap to an audience they expect to be judged by.
The most reliable cure for drift is not a better scale. Five points, four points, behavioural anchors, elaborate rubrics — organisations rework these endlessly and the ratings move very little, because the problem was never the granularity. The problem is that a number arrived without anything attached to it. Ask for one piece of evidence alongside every rating, a specific thing the person did and roughly when, and the whole exercise changes character. It becomes much harder to award a casual four when a sentence has to follow it.
This is also the argument for keeping assessment close to work rather than to the calendar. Structured evaluations and feedback gathered near the moment something happened are worth more than a retrospective sweep in November, when the only evidence anyone can recall is whatever occurred in October. The same applies at the other end: a rating that produces a specific training goal is being used, and things that get used get corrected. Ratings that go nowhere are never wrong, because nothing ever tests them.
Different managers mean different things by the same number, and no amount of guidance in a handbook fixes that. What does fix it, slowly, is managers comparing notes out loud. Half an hour with three or four peers, each explaining what a four in one specific skill looks like in their team, does more for consistency than a page of definitions — mostly because it surfaces the disagreement rather than averaging it away. The point of the session is not to force agreement on every rating. It is to ensure that when two people say four, they are describing roughly the same thing.
It is worth being clear about what this is not. Calibration in the skills sense is a shared-language exercise, not a forced distribution and not a ranking; the moment it starts allocating a fixed quota of fives it has become a performance mechanism and the honesty drains out of it within one cycle. Done well, it is a quiet, recurring habit attached to the development review cycle, and its main output is not a corrected spreadsheet but a group of managers who now describe capability in compatible terms.
There is a useful diagnostic available to anyone with access to the reporting. Look at the distribution rather than the average. A healthy skills dataset has spread — ones and twos in places, genuine variation between teams, some skills where the organisation is visibly weak. A dataset where almost everything clusters at three-and-a-half is not describing a uniformly competent workforce; it is describing a population of people who have worked out what the safe answer is. The shape of the data is usually more informative than anything in it.
Which leads somewhere slightly uncomfortable. A partial dataset that people believe is worth considerably more than a complete one they quietly discount, and coverage is the wrong first target. Better to have forty skills rated candidly, with evidence, by managers who have compared notes, than four hundred rated to fill in a form. The framework tells you what can be seen. The rating tells you whether what you are seeing is real — and no amount of downstream sophistication will rescue a number that nobody meant.
17 August 2026
Last time, this series looked at the line manager — the person in the middle who decides, week by week, whether a skills-based approach becomes a habit or an announcement. Every post before it has leaned on the same unexamined noun. The taxonomy. The framework. The skills list. It has been named in passing in almost every piece and never given a post of its own, which is odd, because it is the thing all the rest of it sits on.
A skills framework is the vocabulary an organisation uses to talk about capability. Get it right and everything downstream — the reviews, the analytics, the development plans — has something solid to point at. Get it wrong and you have built a very expensive machine for producing confident numbers about nothing in particular. This post is about the framework underneath: why it decays, what makes it decay faster, and what it takes to keep one honest.
Nobody gets excited about a skills taxonomy. It is a list. It has no launch event, no dashboard and no obvious owner, and in most organisations it is written once, early, by whoever had capacity that quarter and needed something in place before the platform went live. Then it disappears into the background — and quietly becomes the dependency for everything else the programme does.
This matters because the framework determines what can be seen. A skill that isn’t named cannot be assessed, developed, reported on, or hired for — it simply falls outside the field of view. When leaders complain that the skills analytics don’t reflect what the business actually needs, the problem is rarely the reporting layer. It is that the vocabulary underneath was written to describe an organisation that has since moved on, and the numbers are faithfully measuring the wrong things.
The most common failure is not a framework that is wrong. It is a framework that is enormous. The instinct when building one is completeness: consult every function, capture every specialism, make sure nobody’s work is missing from the list. It feels like rigour, and every individual addition is easy to justify. The result is eight hundred skills, each defensible on its own, and collectively unusable by a manager with forty minutes and a team of nine.
Size compounds in a way that is easy to miss at the design stage. A large framework takes longer to assess against, so assessments get rushed. Rushed assessments produce noisy data, and noisy data erodes the trust that makes anyone bother assessing carefully in the first place. Within two cycles you have a comprehensive taxonomy that nobody believes. A smaller framework — the fifty or so capabilities that genuinely differentiate performance in this business — will be assessed properly, which makes it more accurate than the exhaustive version it replaced. Completeness and usefulness pull in opposite directions here, and usefulness should win.
There is no prize for writing a skills framework from a blank page. Industry libraries, role standards and off-the-shelf taxonomies are a reasonable starting structure, and in 2026 an AI-assisted first draft will get you a workable skeleton in an afternoon rather than a quarter. Borrowing the scaffolding is sensible, and the organisations that insist on originality here mostly spend six months arriving at something close to the library they could have started from. The mistake is a different one: believing the borrowed version is finished.
Generic frameworks describe a generic organisation. They cannot know that ‘stakeholder management’ in your business mostly means holding a difficult conversation with a client’s finance team, or that ‘data literacy’ has a specific and demanding meaning in one division and a much lighter one in another. The work that cannot be outsourced is the local translation: writing the descriptions in the language people at your organisation actually use, with examples they recognise. That is also what makes a skill-will conversation land — an employee can only place themselves honestly against a description they can picture themselves doing.
Most taxonomies rot for an unglamorous reason: after launch, no one owns them. Roles change, tools change, a new service line appears, and the framework stays exactly as it was written eighteen months ago. It doesn’t break loudly, which is precisely the problem — there is no moment where the framework announces that it has fallen behind. It just drifts, a role at a time, until the gap between the words on the page and the work happening in the building is wide enough that people quietly stop taking it seriously.
The fix is boring and effective. Name an owner — a person, not a committee, with the authority to change the thing. Set a review cycle, twice a year is usually enough, where the framework is checked against what the business now actually does, with additions and, more importantly, retirements. The best signal for that review is friction reported from the front line: skills managers keep having to explain, ratings that cluster suspiciously at one level, capabilities that never once appear in a training goal. Those are the entries doing no work, and a framework improves as much by deleting as by adding.
A skills framework is not a reference document, and it is not an asset to be admired for its coverage. It is a working vocabulary, and the only real test of a working vocabulary is whether people reach for it when nobody is making them. If a manager opens it during a development review because it helps them say something true and specific, and the employee across the table recognises themselves in the description, it is doing its job — regardless of how many capabilities it leaves out.
Which suggests the right ambition is smaller than it first appears. Not a complete map of everything the organisation can do, but a short, current, locally-worded list of the things that matter, maintained by someone whose job it is to keep it true. Every layer this series has covered — the practice, the feedback, the analytics, the manager conversations — inherits its credibility from that list. It is worth the unglamorous effort of keeping it honest.
11 August 2026
Last time, this series looked at the first twelve months — the sequencing that keeps a skills-based L&D programme from quietly dying in the year it is stood up. That piece, like the ones before it, kept its eye on the design: the taxonomy, the evidence, the order of operations. But designs don’t run themselves. Somewhere between the strategy deck and the employee’s desk sits a person the series has mentioned in passing and never given its own post — the line manager. And that is an oversight worth correcting, because the manager is the point at which almost every good intention either becomes a habit or evaporates.
It is tempting to treat the manager as a channel — someone you brief once, hand a dashboard, and expect to relay the programme downward. But a skills-based approach asks the manager to do something far harder than relay: to change how they read their own team, week after week, in the ordinary run of work. This post is about that person in the middle — what the model actually demands of them, why their resistance is usually a signal rather than an obstacle, and what it takes to make the role survivable.
Every skills-based L&D programme has an org chart, and on that chart the line manager sits at the one node no strategy can route around. The platform can be excellent, the taxonomy sound, the executive sponsorship real — and none of it reaches an employee except through the person they report to. When a manager treats a skills conversation as a box to tick, the employee learns, correctly, that it doesn’t matter. When a manager takes it seriously, the same conversation becomes the most useful half-hour of the month.
This is why programmes that look identical on paper produce such different results in practice. The difference is rarely the tooling; it is whether the managers running the day-to-day chose to carry it. A skills model is not a system employees interact with directly so much as a set of expectations their manager either upholds or lets slide. Which means the manager is not one stakeholder among many — they are the single point of failure, and the single point of leverage.
It helps to be honest about the size of the ask. A manager already carries delivery targets, hiring, the endless triage of a real team. A skills-based approach now adds a second lens: alongside ‘did the work get done,’ they are asked to watch ‘what did this person get better at, and what should they build next.’ That is not a lighter version of the old job — it is a genuinely different discipline, closer to coaching than to supervision, and most managers were promoted for the supervision.
Concretely, it means holding a regular conversation about capability rather than only output; setting clear training goals an employee can actually walk toward; and giving honest, specific feedback about where someone stands against a skill instead of a vague reassurance at review time. Tools like a skill-will matrix make the thinking easier, but they don’t do the noticing. That still falls to a human who has to pay a kind of attention the previous version of the job never required.
When managers push back on a skills programme — ‘I don’t have time,’ ‘the ratings feel made up,’ ‘this is HR’s project, not mine’ — the reflex is to treat the resistance as a change-management problem to be overcome with communication. It is usually more accurate to treat it as feedback about the design. A manager who says they have no time is often telling you the programme has asked for the ceremony without removing anything to make room for it.
The manager who distrusts the ratings is frequently the most valuable person in the room, because they are the one who will actually be held to the numbers when a staffing decision goes sideways. Their scepticism is a demand for the evidence to be real before it is acted on — the same discipline that keeps skills analytics honest at the organisational level. Listening to the objection, rather than steamrolling it, is how a programme finds the places it was going to break anyway.
The fastest way to lose managers is to hand them a new obligation with no visible payoff to the team they are trying to run. If the skills work shows up as extra admin in service of a central dashboard, it will be done grudgingly and badly, and the data underneath it will be worth exactly what was put into it. The managers who lean in are the ones who can see the programme making their own week easier — a clearer read on who is ready for what, fewer surprises at review time, a defensible basis for the promotion they wanted to make anyway.
So the sequencing that matters most in year one is not technical, it is motivational: give the manager an early, concrete win before you give them the full apparatus. A development review that finally has real substance behind it, a case where the skills view caught a gap before it became a problem — these are what convert a compliant manager into a committed one. Reason first, task second. Do it the other way round and you get the task without the reason, which is another name for a programme nobody trusts.
There is a comforting myth that some managers are simply ‘people developers’ by nature and the rest are not, and that the programme’s job is to find the naturals. It is a myth worth dropping. The managers who run skills conversations well are, overwhelmingly, the ones who were shown how — given a simple rhythm to follow, a little language for talking about capability, and the cover to spend time on it without feeling they were stealing it from ‘real’ work.
That is the quiet implication of everything above: if the manager in the middle decides the programme’s fate, then equipping that manager is not a side-project of the rollout — it is the rollout. The taxonomy and the analytics and the platform all matter, but they are scaffolding around a single human act repeated across a workforce: a manager paying attention to how their people are growing, and doing something about it. Get that person right and the rest compounds. Get everything else right and neglect them, and you have built a very sophisticated machine with no one to turn it on.
03 August 2026
Last time, this series took on the machinery — what artificial intelligence genuinely does for skills-based L&D, and which decisions have to stay human. That post, and the ten before it, shared a quiet assumption: that the programme already exists. The series has spent four months explaining why skills-based L&D matters and what it looks like when it works. It has said almost nothing about the part that keeps people up at night — how you actually stand the thing up from a standing start.
That silence is telling, because the first year is where most of these programmes quietly die. Not from a lack of conviction — the business case usually clears — but from a handful of avoidable mistakes made in the opening months, when the temptation is to do everything at once and the reality is that almost nothing is ready. This week, the series changes register: from why and what to how, and specifically to what the first twelve months actually demand of the team standing at the starting line.
The instinct, once the business case lands, is to treat the first year as a build: choose a platform, define the skills, roll it out, and start reporting. Framed that way, the work looks like a checklist, and checklists get done in parallel. But skills-based L&D is not a system you install; it is a set of habits a workforce has to adopt, and habits cannot be installed in parallel. They have to be sequenced, because each one depends on the trust built by the last.
That reframing is the whole game. The organisations that stall in year one are almost never the ones that lacked resources or executive air cover. They are the ones that tried to do everything the model eventually requires — the full taxonomy, the analytics, the performance linkage — before anyone had a reason to believe the first small piece. Sequencing is not a project-management nicety here. It is the difference between a programme that compounds and one that is quietly shelved by March.
The first and most common way the year goes wrong is the taxonomy. It is intellectually satisfying to map every skill in the organisation before doing anything with it, and it is a trap. A comprehensive framework built in a vacuum takes months, ages before it ships, and lands as a monument nobody asked for — thousands of skills, no evidence behind any of them, and a workforce that experiences the whole thing as a survey.
The teams that get through the first year start narrow and deliberately incomplete. One function, one set of roles, the fifteen or twenty skills that actually decide whether someone is good at the job. A smaller map that is used beats a complete one that is admired, because the point of the taxonomy was never accuracy for its own sake — it was to give people clear training goals they can actually walk toward. A framework earns the right to grow by being useful first.
The second failure mode is the mirror image of the first: rushing to measurement before there is anything trustworthy to measure. A skills dashboard stood up in month two, populated by self-assessments nobody has any incentive to make honest, produces a confident-looking picture that is quietly wrong. Worse, it teaches leaders to make decisions on it — and the first time a staffing call goes visibly sideways because the data was fiction, the whole programme loses the room.
The discipline here is to let analytics follow evidence rather than lead it. Numbers earn authority slowly, by being grounded in something real — a completed assessment, an observed piece of work, a manager and employee who looked at the same picture and agreed it was true. Reporting that arrives before that groundwork is not insight; it is decoration that will eventually be believed, which is more dangerous than being ignored.
If the first year is a sequencing problem, the first move is not a platform decision or a taxonomy workshop. It is a question, asked of the people whose skills are about to be measured: where do you actually want to go? Capturing career aspirations alongside skill and will before deciding what anyone should learn does something no framework can — it makes the whole exercise feel done with people rather than to them, which is the difference between honest data and polished data.
Starting with the person also quietly solves the adoption problem the rest of the year will otherwise fight. When the first thing someone experiences is a conversation about their own direction, the profile that follows reads as a tool for getting there, not a file being kept on them. Get that opening beat right and the later steps — assessment, feedback, measurement — inherit a reservoir of goodwill. Get it wrong, and every one of them is uphill.
The single most useful thing a team can do in the first year is to close one complete loop, small, before scaling anything. Pick a handful of roles. Capture aspirations, agree a couple of priority skills, run one round of real practice, and let evaluations and feedback put honest signal back in front of the person — all the way through to a development review that both sides can actually have because they are looking at the same evidence. One loop that people believe is worth more than a full rollout they merely tolerate.
A closed loop is proof, and proof is what buys the second year. It gives you a real story to tell the next function, a handful of people who will vouch for the thing because it demonstrably worked for them, and — crucially — a set of assumptions tested against reality before they were baked into a platform-wide rollout. Scale the loop, not the ambition. The ambition was never in doubt; the loop is what makes it survivable.
There is a simple test for whether a first year has gone well, and it has nothing to do with how many skills were mapped or how polished the dashboard looks. It is this: at the twelve-month mark, do the people who went through it want more of it? If a manager is asking to bring the next team in, if an employee is keeping their profile current without being chased, the sequence worked — trust was built in the right order, and the model has somewhere to grow.
If instead the honest answer is that profiles were filled in once and abandoned, that the dashboard is impressive and unbelieved, that the taxonomy is complete and unused — the failure was almost never ambition. It was sequence: too much attempted, too fast, before anyone had a reason to trust the first small piece. Skills-based L&D is not won in the boardroom that approves it or the platform that hosts it. It is won, or lost, in the patience of the first year. Start small enough to be believed, and let being believed earn you the rest.
16 July 2026
Last time, this series changed seats and looked at skills-based L&D from the employee’s side of the profile. Sitting there, something became hard to ignore: almost everything the series has promised — profiles that stay current, feedback that compounds, career paths that assemble themselves from skills data — quietly assumes a layer of machinery doing work no L&D team could do by hand. That machinery has a name everyone is either overusing or avoiding: AI.
So this week the series asks the question directly. Not “is AI coming for L&D” — that debate has been stale for two years — but something more useful: in a skills-based operating model, what is AI actually good for, what can it not carry, and how should a sensible L&D team divide the labour in 2026?
Go back through this series and count the moving parts a skills-based organisation depends on: a taxonomy kept current as roles evolve, thousands of profiles refreshed as people learn, gaps mapped against strategy, content matched to gaps, practice generated at the right difficulty, feedback captured in the flow of work. Now imagine maintaining all of that manually. The honest answer is that nobody does — and nobody ever intended to.
This is the assumption hiding inside every skills-based pitch deck: the model only scales because inference, matching, and generation are automated. That is not a criticism. But it does mean the AI question is not an optional add-on to a skills strategy. It is the load-bearing wall, and it deserves the same scrutiny the series has given taxonomies, measurement, and the business case.
Three jobs stand out, and they happen to be the three that were breaking L&D teams before automation arrived. The first is inference — reading the exhaust of everyday work and learning activity and suggesting what it says about capability, so profiles drift towards accuracy instead of towards fiction. Paired with analytics that surface the patterns, this is what turns a skills database from a survey snapshot into something closer to a living picture.
The second is matching: person to gap, gap to content, content to moment. This is pure pattern-work across more variables than any human curator can hold, and it is where the “course catalogue” posts of this series quietly get their answer. The third is generation. AI-assisted course creation has collapsed the cost of producing a first draft of learning content from weeks to hours — which is precisely what makes the skills-first content library, built against the taxonomy rather than the calendar, economically possible for teams that are not enterprise-sized.
Now the other column of the ledger. AI cannot decide what capability the business actually needs next year — that is strategy, and outsourcing it to a model means optimising towards last year’s patterns. It cannot supply the trust this series wrote about from the employee’s seat; an inference engine that quietly rescores people’s profiles without explanation is the fastest way to lose the honesty that makes the data worth having.
And it cannot replace judgement at the moments that matter. A model can flag that someone’s evidence looks thin; only a human conversation — the kind that structured evaluations and feedback exist to hold — can establish what is actually true and what should happen next. The pattern across every failure story of the past two years is the same: the organisation automated the judgement and kept the admin, when it should have done the opposite.
Put the two columns together and a clean rule emerges: let AI propose, let people decide. AI drafts the profile update; the person confirms it. AI suggests the learning path against a training goal; the employee and manager commit to it. AI surfaces who is ready for a stretch move; the career conversation decides whether the person wants it. Every “propose” saves hours; every “decide” protects trust.
The teams getting this right in 2026 are noticeably unglamorous about it. They talk less about AI strategy and more about which specific decisions stay human. That list — written down, shared with employees, honoured in practice — is doing more for adoption than any capability the technology itself has shipped this year.
So when the next AI-for-skills demo lands in your inbox, skip the feature tour and ask one question: for each thing this automates, who was doing it before, and who checks it now? If the answer to the first half is “nobody — it simply wasn’t being done,” that is genuine capacity you are buying. If the answer to the second half is “nobody,” walk away.
Everything this series has argued — the taxonomy, the measurement, the practice loops, the feedback rhythm, the employee’s ownership of their own picture — depends on machinery that works and people who trust it. In 2026 you can, at last, have both. But only in that order.
06 July 2026
Last time, this series watched L&D reinvent itself as the steward of the capability picture the whole business now runs on. That closed a loop this series has been drawing since April — managers, taxonomies, measurement, content, practice, feedback, the business case, the organisation, the function itself. Read the list back and something stands out: every one of those posts looked at skills-based L&D from above. The one perspective the series has never taken is the one belonging to the person whose skills are actually in the data.
That gap matters more than it looks, because in 2026 the success of a skills-based organisation is not decided in the boardroom that approved it. It is decided at thousands of individual desks, where people quietly choose whether to keep their profile honest, whether to engage with the feedback, and whether to believe that any of this is being done for them rather than to them. This week, the series changes seats.
To the organisation, a skills profile is infrastructure — a row in the dataset that feeds planning, staffing, and development decisions. To the employee, it is something far more personal: a standing claim about who they are and what they are worth, held and read by their employer. Whether that claim feels like an asset or an exposure is not a soft question about sentiment. It is the single biggest determinant of whether the data underneath the whole strategy can be trusted.
The mechanism is simple. Skills data is only as good as people’s willingness to be honest in it, and honesty follows consequences. In an organisation where admitting a gap reliably produces support — a course, a stretch assignment, a coaching conversation — people tell the truth. In one where a visible gap quietly costs you the interesting project or the promotion shortlist, people polish. No taxonomy, platform, or dashboard survives a workforce that has learned to polish.
The old deal was passive: learning was something the organisation did to you. You were enrolled, you completed, you were certified, and the record of it belonged to a system you never looked at. The skills-based deal is different in kind, not just degree. A living profile shows you where you stand; visible gaps show you what is between you and the role you want; and clear training goals turn that distance into something you can actually walk.
The best implementations go a step further and ask the person where they want to go before deciding what they should learn, capturing career aspirations alongside skill and will so that development is negotiated rather than assigned. That single change — from consumer of a curriculum to owner of a direction — is what employees mean when they say skills-based working finally feels different from the annual training calendar it replaced.
There is a harder edge to all this, and pretending otherwise is how programmes lose the room. The same data that powers development can, from the employee’s seat, look like surveillance. Who sees my gaps? Does this number follow me into pay conversations? Was I passed over because of something in a system I have never been shown? These questions rarely appear on an implementation roadmap, and they are the ones the workforce is actually asking.
The organisations that answer them well do it with transparency rather than reassurance. They put plain rules around who sees what and what it is used for, and — crucially — they make the data flow back to the person, not just upward. When evaluations and feedback reach the employee as insight they can act on, and the analytics visibly serve their development rather than only management reporting, measurement starts to read as investment. Opacity, not measurement, is what people distrust.
Get the trust question right and the payoff lands squarely on the employee’s side of the table. Career conversations stop being exercises in advocacy — who noticed you, who will vouch for you — and start being grounded in shared evidence. A development review built on a skills profile is a conversation two people can actually have, because both are looking at the same picture rather than trading impressions.
There is a fairness dividend here that deserves more airtime than it gets. When capability is the currency, the quiet performer in the regional office competes on the same terms as the confident voice in head office. Internal moves stop depending on being in the right meeting. That is not a soft benefit; it is the employee-side answer to why any of this is worth the discomfort of being measured at all.
The honest catch is that handing employees ownership means asking them to do something with it. A profile only stays true if the person keeps it true; feedback only compounds if it is engaged with; a visible gap only closes if somebody chooses to close it. Organisations that frame skills-based working as pure empowerment set themselves up for the quiet disappointment of profiles that were filled in once, enthusiastically, and never touched again.
Nor can the organisation use ownership as an exit. “It’s your career” is a partnership when it comes with time, support, and honest data — and an abdication when it does not. The test worth applying in 2026 is disarmingly simple: would the person being measured choose this system for themselves if it were optional? Everything this series has covered — the taxonomy, the measurement, the manager conversations, the business case — ultimately exists to make the answer yes. Build it so that it is.
01 July 2026
Last time, this series followed the skills data L&D builds as it quietly outgrew the function and became something the whole business runs on — feeding hiring, workforce planning, and the decisions about who moves where. That shift is easy to celebrate and easy to stop thinking about too soon. Because if the data has left home, there is an obvious question sitting right behind it that almost nobody asks out loud: what happens to L&D itself?
For most of its history, L&D has known exactly what it was — the function that makes and runs learning. In 2026 that definition is quietly coming apart. When the point of the work is no longer the courses but the capability picture underneath them, the team that built that picture can’t keep describing its job the way it did in 2018. The interesting story this year isn’t only that skills data changed the business; it’s that it’s changing the function that made it.
Ask most L&D teams what they do and the answer is still framed around output: courses designed, programmes launched, completions logged, satisfaction scored. It’s a job description built for a world where the deliverable was content and success meant people consumed it. That world hasn’t vanished, but it has been demoted. When the organisation starts asking whether capability actually moved — and using the answer to hire, staff, and promote — a tally of courses shipped stops being a measure of anything that matters.
This is uncomfortable precisely because the old metrics were so easy to report. A completion rate is clean; a claim that the workforce is measurably more capable is not. But the moment skills data becomes the thing the business relies on, L&D’s worth is judged by the quality of that data and the capability behind it, not by the volume of learning it pushed out. The job description didn’t get updated so much as it quietly ran out of road.
The clearest change is where the team’s centre of gravity sits. Producing content used to be the core craft — storyboarding, authoring, building the catalogue. That work doesn’t disappear, but it’s no longer the point, especially as faster ways to produce and assemble content make the raw making of courses less of a bottleneck. What becomes central instead is stewardship: keeping the skills taxonomy honest, making sure profiles reflect reality, and connecting learning to the capability it’s supposed to build.
In practice that reframes almost every existing activity. Managing the catalogue becomes less about how much sits in it and more about whether each piece maps to a capability the business actually needs. Setting learning goals stops being an annual formality and becomes the way individual development ties back to the skills picture leaders are now reading. The team’s product isn’t a library any more; it’s a trustworthy, current view of what people can do.
Once skills data feeds hiring, mobility, and planning, L&D can’t operate as a self-contained factory that takes requests in and ships courses out. It sits in the middle of a conversation that now includes recruiters, workforce planners, HR, and the line managers who own the day-to-day of capability. Its most valuable move is often not to build something but to broker — to translate a business problem into a capability question, and a capability question into the right mix of development, hiring, or redeployment.
That’s a consulting posture more than a production one. It leans on the same signals the rest of the business is starting to trust: what development conversations reveal, where aspiration and readiness line up, and what the capability data says is genuinely missing. The team that used to be measured by throughput becomes valuable for judgement — for knowing which lever to pull, and when building a course is the wrong answer.
A function that stewards capability and brokers decisions needs a different toolkit from one that produces courses. Data literacy stops being a nice-to-have and becomes core: if the team owns the skills picture, it has to be fluent in reading, questioning, and governing it. The same analytics that once tracked learning now have to be interpreted for an audience making real workforce decisions, which is a genuinely different skill from reporting completions.
Alongside that sits a more consultative craft — business partnering, facilitation, the ability to sit with a leader and shape the problem rather than take an order. It’s worth naming that this can be a stretch for teams hired for instructional design and content production. The skills function needs its own skills, and building them is part of the transition, not an afterthought to it. There’s a neat symmetry in it: the function that tells the business to take capability seriously has to do exactly that with itself.
None of this is free, and the honest catch is about identity as much as capability. A team that has always known its worth through course counts and completion rates is being asked to give up a scoreboard that was reassuringly concrete for one that’s harder to point at. Measured by the old numbers, the new L&D can look like it’s doing less; measured by the new ones, it may be doing the most important work it ever has — but only if the organisation agrees to change what it counts.
That’s the real risk in 2026: not that L&D fails to evolve, but that it evolves while everyone around it still grades it on the old metrics. The functions that navigate this well tend to renegotiate their own scoreboard early — agreeing with the business that success now means trustworthy capability data and better workforce decisions, not a busier learning calendar. The skills data may have outgrown L&D, but the function that stewards it hasn’t shrunk. It’s being asked to grow into something considerably more valuable — and to stop measuring itself by the thing it used to be.
22 June 2026
Over the past few months this series has walked through the whole machinery of skills-based L&D — the taxonomy underneath it, the managers who drive it, the practice that turns knowing into doing, the measurement that proves capability moved, and finally the business case that earns it a budget line. Build all of that well and you end up with something most organisations have never actually had: a live, trustworthy picture of what their people can do.
Here is the part nobody quite plans for. Once that picture exists and is good enough to rely on, it stops being an L&D asset. Other functions start reaching for it — recruiters, workforce planners, the leaders deciding who gets the stretch project. In 2026 the most interesting shift isn’t happening inside L&D at all; it’s what happens when the skills data L&D built quietly becomes the operating data for the rest of the business.
A skills taxonomy and a current capability profile were originally meant to answer an L&D question: who needs to learn what. But a good skills graph answers a far wider set of questions, and people notice. A leader staffing a project no longer has to guess who might be ready; a recruiter no longer has to start every search assuming the answer is external; a planner can finally see capability as a quantity that can be measured, not a vague worry. The data was built for development, but it reads as infrastructure.
This is the point at which skills-based L&D stops being a programme and starts being a system the organisation runs on. It’s also the moment the stakes change. When skills data only informed a learning plan, an error was a slightly wrong recommendation. When the same data starts shaping who gets hired, promoted, or moved, the cost of a sloppy taxonomy or a stale profile is no longer academic. The opportunity and the risk arrive together, which is exactly why this transition deserves more thought than it usually gets.
The clearest place skills data spills out of L&D is recruitment. For years, hiring has leaned on proxies — a degree, a number of years, a previous job title — because the real thing, capability, was too hard to see. A mature skills picture removes the excuse. Roles can be defined by the capabilities they actually require, candidates assessed against those capabilities directly, and — crucially — the internal market checked before the external one. The question shifts from “who can we find” to “who do we already have, and what’s the real gap.”
That last move is where skills-based hiring and internal mobility finally meet. When the same skills profiles that power development also feed a view of aspiration and readiness, an open role becomes a prompt to look inward first. The result isn’t just cheaper hiring; it’s a workforce that watches capability rather than CVs, and a quieter signal to good people that the path forward runs through the organisation they’re already in.
Strategic workforce planning has always been long on ambition and short on data. The strategy names the capabilities the business will need in two years; the planning then proceeds on instinct, because nobody can say with confidence what the organisation can do today. Skills data closes that gap. With a real baseline of current capability and a clear view of where demand is heading, the build-buy-borrow decision stops being a guess and becomes a comparison between numbers — the cost of developing a capability internally against the cost and time of acquiring it.
This is where the analytics that L&D built to track learning earn a second life. The same view that shows which skills are accelerating and which are stuck is, from a planner’s seat, an early-warning system for capability risk: the critical skill concentrated in two people, the capability the strategy depends on that nobody is actually building. Planning that used to run a year behind reality can start running slightly ahead of it.
None of this is free of risk, and it’s worth being honest about the catch. The moment skills data influences hiring, pay, and promotion, it becomes something people have a reason to game — and something that can quietly encode bias at scale. A taxonomy that’s subtly wrong is no longer just an L&D inconvenience; it’s wrong everywhere the data is now used. Self-assessed levels that were fine for nudging a learning plan are dangerous as a basis for who gets the promotion. Extending skills data across the business raises the bar on keeping it honest.
Which means governance isn’t bureaucratic overhead here — it’s the thing that makes the whole move safe. Capability claims need evidence, not just confidence; profiles need to stay current; and the same skills picture should be fed by real signals from work and development conversations rather than a one-off survey. The organisations that get this right treat their skills data the way finance treats its numbers: shared widely, but governed carefully. That, in the end, is the real maturity marker for 2026 — not that skills data finally escaped L&D, but that it could be trusted once it did.
08 June 2026
Every L&D leader has had a version of the same meeting. The strategy is sound, the platform is in, the skills work is genuinely moving — and then someone in finance asks the only question that decides whether any of it survives the next budget cycle: what are we getting back for this? It’s a fair question, and for years L&D answered it badly, with completion rates and satisfaction scores that prove activity happened but say nothing about whether the business is any better off.
In 2026, that answer no longer holds. Skills-based L&D has spent three years earning the right to be taken seriously as a capability strategy; now it has to earn its place in the budget by speaking the language of return. The good news is that the same skills data that powers the development loop is also the raw material for a credible business case. The shift is learning to frame it not as a defence of training spend, but as evidence of capability built — and tied to outcomes leadership already cares about.
The traditional L&D scorecard measures effort, not effect. Hours delivered, courses completed, seats filled, a satisfaction average north of four out of five. None of it is wrong, exactly — it’s just answering a question nobody in the boardroom is asking. A CFO doesn’t want to know that 8,000 courses were completed; they want to know whether the organisation can now do something it couldn’t do before, and whether that closed a gap that was costing money.
The deeper problem is that activity metrics are unfalsifiable as a value claim. A high completion rate is equally consistent with a transformed workforce and with eight thousand people clicking through slides they’ve already forgotten. Until L&D can show movement in capability — and connect that movement to a business outcome — it remains, in the language of the budget meeting, a cost centre. The job of the business case is to move the conversation from what was delivered to what changed.
The strongest business cases don’t begin with what training costs — they begin with what the skills gap is already costing. Roles that sit open because no internal candidate is ready. Projects that stall waiting on a capability the team doesn’t yet have. Work outsourced or contracted at a premium because it can’t be done in-house. Each of these is a number, and each is a number leadership already feels. Anchored against specific skills goals, the development spend stops looking like an expense and starts looking like the cheaper side of a trade-off.
This reframing matters because it changes who owns the case. When L&D argues for a bigger learning budget, it’s asking for money. When it shows that a defined capability gap is costing the business a quantifiable amount each quarter, and that closing it is materially cheaper than continuing to absorb the cost, it’s making a financial argument on finance’s own terms. The taxonomy and skills profile are what make this possible — they turn a vague worry about ‘skills shortages’ into a specific, sized, addressable gap.
A credible return story needs two halves: evidence that capability actually moved, and a plausible link to an outcome the business already measures. The first half is now within reach — skills analytics and reporting can show which capabilities are accelerating, which are stuck, and how the organisation’s skills position has shifted over a quarter, against a real baseline rather than a feeling.
The second half is the discipline most L&D functions skip: deciding, in advance, which business metric a given skills investment is meant to move, and watching them together. Time-to-fill on critical roles as internal mobility improves. Quality or error rates as a core competency deepens. Customer outcomes as a service skill matures. The point isn’t to claim L&D single-handedly caused the result — leadership is too sophisticated for that. It’s to show capability and outcome moving in step, consistently enough that the relationship is hard to dismiss.
The mistake is treating the business case as something you assemble in a panic the week before the budget review. By then the data is whatever happened to be collected, and the story is reverse-engineered. The functions that win the funding argument build the case continuously — choosing the outcomes that matter up front, instrumenting for them, and reviewing capability-against-outcome on the same cadence as any other part of the business. When development reviews feed the same skills picture the analytics report from, the evidence accumulates on its own.
Done this way, the budget conversation stops being a defence and becomes a briefing. L&D walks in with a sized gap, a record of capability moving against it, and an outcome trending in the right direction — the same shape of case any other function brings when it asks for investment. That’s the real maturity marker for skills-based L&D in 2026: not a better platform or a richer content library, but the ability to stand in front of the people holding the budget and answer the only question that ever mattered — what are we getting back? — with a number, and a straight face.