01 June 2026
There’s a familiar reflex in most organisations the week before performance reviews open. Calendars fill with one-on-ones. Managers dig through six months of half-remembered work. Employees rewrite their own narratives. A neat document gets filed, ratings get calibrated, and then the system goes quiet for another half-year. In 2026, that rhythm finally looks like what it is: a beautifully formatted summary of feedback that never actually arrived in time to change anything.
The skills-based shift has made this gap impossible to ignore. If capability is supposed to be moving every week — through practice, application, and small course corrections — then the once-a-year review is an X-ray of a body that’s already healed or already broken. The teams making real progress on skills aren’t replacing the review with a better template. They’re replacing it with a continuous feedback rhythm that runs alongside the work, and treating the formal review as a periodic stocktake of a system that’s already doing its job.
The annual review wasn’t designed to develop capability — it was designed to rationalise pay, manage risk, and document performance for the record. It does those things reasonably well. What it has never done well is help someone get better at the work in front of them. By the time the feedback lands, the project is closed, the team has moved on, and the moment when the lesson could have changed behaviour has long passed.
In a skills-based model that gap compounds. The taxonomy is moving in week-long increments. Practice cycles are running across days, not quarters. The library is being refreshed against real capability signals. Bolting a six-monthly conversation onto a weekly system was always going to feel slow, and in 2026 it finally feels obsolete. The question isn’t whether to keep the review — most organisations still need a formal cadence for compensation and progression. The question is what runs in the long stretches between them.
Continuous feedback is one of those phrases that has been used to mean almost anything — from a Slack thumbs-up to a quarterly check-in re-labelled as “always-on”. The version that actually moves capability is narrower and more disciplined than that. It’s a short, specific signal — tied to a named skill, attached to a piece of real work, and delivered close enough to the moment for the person to act on it. It doesn’t need to be long, and it doesn’t need to be formal. It needs to be timely, concrete, and traceable.
The teams getting this right have stopped trying to invent a separate feedback ritual and started threading it into the work itself. A reviewer marks up a draft against the same rubric the course used. A manager spends three minutes after a client call naming what was strong and what to tighten next time. A peer leaves a structured comment on a deliverable using a shared framework. None of those moments looks like a “feedback meeting”, and that’s precisely why they work.
One of the quieter changes in 2026 is that feedback has stopped being framed primarily as a judgement and started being framed as a signal. The shift sounds semantic; it isn’t. A judgement is a closed loop — the person was good or wasn’t, the rating goes into the record, the conversation ends. A signal is an input — it tells the skills profile something specific, it nudges the next development action, and it accumulates into a much more honest picture of capability than any single review could produce.
That reframing changes what gets captured and how. Instead of one composite rating per person per cycle, the system captures many small signals against named skills: a manager’s rubric score on a deliverable, a peer’s qualitative note on a collaboration moment, the outcome of a deliberate practice cycle, an evaluator’s structured response inside evaluations and feedback. Each signal on its own is small. In aggregate they’re the most reliable read of capability the organisation has ever had.
The instinct, when feedback frequency goes up, is to assume managers need to do more. The honest answer is that they need to do less of one thing and more of another. Fewer end-of-cycle essays. More short-form, in-the-moment notes attached to real work. The managers who land this well aren’t suddenly trained coaches — they’re operating a much smaller loop, repeatedly: name what good looks like before the task, name what was strong and what to tighten after it, and let the system carry the rest.
Where the formal cadence still matters — in performance and development reviews and progression decisions — the manager’s job is no longer to manufacture feedback in the room. It’s to read the signals that have already accumulated, surface the patterns the day-to-day notes can’t, and decide what changes in the next development cycle. The review stops being where feedback happens and starts being where feedback is interpreted.
The reason continuous feedback finally pays back in a skills-based world is that the loop actually closes. A signal lands against a named skill. The skills profile shifts. The next piece of content, the next practice opportunity, the next stretch assignment is chosen against that updated picture rather than the stale one. Analytics and reporting stop telling leaders what was delivered and start telling them what’s moving — which skills are accelerating, which are stuck, which managers are running the loop and which are not.
There’s nothing flashy about any of this. No new platform category. No keynote-friendly rebrand of the performance review. It’s a quieter discipline: shorter feedback, more often, attached to specific skills, captured in a way the system can read. Done consistently, it does what every previous attempt to fix the annual review never quite managed — it turns feedback from a once-a-year ritual into the operating rhythm of how capability gets built. In 2026, that’s the half of the conversation worth investing in.
25 May 2026
There’s a moment in almost every skills-based L&D conversation when the room goes quiet. The taxonomy is in. The library has been re-tagged. The managers are having better development conversations than they were a year ago. The dashboards are starting to tell a real story. And then someone leans forward and asks the harder question: so when is any of this actually going to change what people can do? That’s the question 2026 is finally forcing L&D teams to answer head-on.
The honest answer is that most of the work we’ve done so far — the strategy, the platforms, the content rebuild — has been about getting the inputs right. But capability doesn’t come from inputs. It comes from what people actually do between courses, in real work, with feedback loops short enough to matter. The missing half of skills-based L&D isn’t another piece of the architecture. It’s the practice and application layer that turns exposure into ability. And almost everyone is still under-investing in it.
The instinct, for a long time, was to assume that good content plus a willing learner equals capability. Sit through a module on giving feedback, watch the scenarios, take the quiz, and the skill is yours. We now know that’s mostly not how skill formation works. Exposure to an idea is the first step in a longer process — not the process itself. Without retrieval, application, and correction, the content fades within days, and almost nothing about what the person can do at work actually changes.
In a skills-based model, that gap becomes uncomfortably visible. The taxonomy says we want someone at “intermediate” on a specific skill. The library says they’ve completed the intermediate content. The dashboard says “complete”. But the work they produce hasn’t moved. The honest reading is that we measured the wrong thing: we measured exposure when we needed to measure practice. The skills profile is only as real as the work behind it.
Practice, in an organisational sense, isn’t a separate event — it’s a structured use of the skill on real work, with someone close enough to the outcome to give honest feedback. That can be a scenario-based exercise inside the platform, but more often it’s smaller and messier than that: a junior writes a first-draft brief with the framework, a senior marks it up against the same criteria the course used, and the conversation that follows is where the skill actually starts to land.
The teams getting this right share a pattern. They name the practice opportunity at the same time they assign the content — “between now and our next one-on-one, you’re going to lead the first ten minutes of the team meeting using this technique” — rather than leaving it to chance. They tie it back to an explicit development goal, captured somewhere both the employee and the manager can see, so it doesn’t fall through the cracks. Tools like training goals and evaluations and feedback stop being admin features and start being the structure that holds practice in place.
One of the quieter shifts in 2026 is that L&D teams have stopped trying to build a parallel practice environment alongside the real one. The simulations and sandboxes still have a place — especially for high-stakes skills where mistakes are expensive — but for most capabilities, the best practice surface is the work itself. The next real customer email. The next forecasting cycle. The next difficult conversation. The job of L&D is to make that practice deliberate rather than accidental.
That “deliberate” piece is what changes the outcome. Random repetition reinforces whatever the person was already doing. Deliberate practice is narrower, harder, and structured around a specific gap. It targets the part of the skill the person is currently weakest at, runs through it under realistic conditions, and ends with feedback specific enough to act on. Done five times across two weeks, that loop moves capability further than a full day of content ever will.
The honest answer about managers and practice is that we keep asking them to do the wrong thing. We don’t need managers to become coaches in the formal, certified sense; most don’t have the time, and quite a lot don’t have the inclination. What we do need is something much smaller and much more consistent: a manager who is willing to spend five minutes at the start of a task naming what good looks like, and five minutes at the end of it pointing at what was strong and what to tighten next time. That’s the practice loop, and it doesn’t require a coaching qualification.
Where this gets formalised — in performance and development reviews and ongoing capability conversations — the manager’s job is to surface the patterns the day-to-day feedback doesn’t. Which skills are moving? Which ones aren’t? Where is the person ready to be stretched into the next level, and where do they still need protected practice time? Done well, the review stops being an annual artefact and starts being the place where the practice loop gets recalibrated.
The last piece, and the one that makes the whole thing pay back, is feeding practice signals back into the skills profile. Right now, most skills profiles are populated by content completions and self-assessments — both of which are weak proxies for real capability. The teams furthest ahead are starting to add signals from actual work: peer feedback on a deliverable, a manager’s rating against a known rubric, evidence of a skill applied to a stretch project, completion of a deliberate practice cycle. None of those signals is perfect on its own; together, they paint a much more honest picture than “course complete” ever did.
When those signals start to flow, the rest of the architecture finally clicks into place. The library knows which content actually moved capability and which only got watched. Internal mobility decisions are based on demonstrated practice, not on who happens to be visible. Analytics and reporting stop telling leaders how busy L&D has been and start telling them where the workforce is genuinely getting better. The skills-based programme stops being something the L&D team owns alone and starts behaving like a shared system of record for capability.
There’s nothing glamorous about the practice layer. It doesn’t come with a vendor demo or a category-defining keynote. It’s a quieter discipline — naming the practice opportunity, running the loop, capturing the signal, recalibrating — week after week. But it’s the half of skills-based L&D where the strategy stops being a slide and starts being something you can see in the work. In 2026, that’s the half worth investing in.
18 May 2026
Every skills-based L&D conversation eventually arrives at the same uncomfortable moment. The taxonomy is in. The managers are on board. The dashboards are saying something useful. And then someone in the room asks the simplest question of all: OK — so when an employee needs to actually learn one of these skills, what do we point them at? Nine times out of ten, the answer is a course catalogue built three to five years ago, organised by topic rather than skill, and last reviewed when half the current workforce wasn’t even hired.
That mismatch is the quiet bottleneck behind a lot of skills strategies right now. The strategy layer has moved on; the content layer is still 2018. Until that gap closes, every other investment — taxonomy, analytics, manager enablement, internal mobility — runs into the same wall: the learning the data points to isn’t actually there in a usable form. The next move in skills-based L&D, for most organisations, isn’t another platform decision. It’s a content decision.
Most L&D libraries were built around a clean assumption: people need to learn topics. “Time management.” “Effective communication.” “Excel for beginners.” Each course was a self-contained module, between thirty minutes and two hours, dropped onto a tile-based homepage and recommended by job role. It made sense when L&D was measured by completion rates and people genuinely did sit down once a quarter to take a course end-to-end.
A skills-based world breaks that model in three places at once. First, the unit of value is no longer the course — it’s the skill, at a specific level, in a specific context. Second, learners don’t arrive with two free hours; they arrive with seven minutes between meetings and a problem they need to solve. Third, the data that should be flowing back into the skills profile — what the person actually engaged with, what they tried in their work, where they got stuck — is invisible to a system that only knows whether someone clicked “mark as complete”. The catalogue isn’t wrong; it’s just answering an older question.
The first shift is conceptual, and it’s the one most catalogues quietly fail. In a skills-based library, the unit of organisation isn’t a course — it’s a skill, tagged at a level. A single ninety-minute course on “Effective Feedback” becomes, in the new model, a small constellation: a five-minute explainer on the foundational skill, a scenario-based practice at the intermediate level, a manager-only debrief at the advanced level, plus the short reference content people actually open before a difficult conversation. Same content, fundamentally re-shaped.
That re-shaping is what unlocks everything downstream. When content is tagged to a skill and a level, the system can finally answer the question learners are actually asking — “I need to get from intermediate to advanced on this specific skill, in the next six weeks; what should I be doing?” The course catalogue couldn’t answer that. A skills library can. And the same tagging is what lets analytics start showing capability movement instead of completion volume.
The second shift is structural. Content for a skills-based world isn’t just re-labelled — it’s re-formed. The long, linear course is being unbundled into shorter, modular pieces designed to drop into the flow of work, alongside richer formats like scenario practice, peer-shared playbooks, short videos from internal experts, and step-by-step references that live next to the task they support. The point isn’t that long-form learning is dead; it’s that it can no longer carry the whole load on its own.
For L&D teams, this is where the work changes character. Rather than commissioning one new course a quarter and watching its completion rate drift downward over twelve months, the team is curating a much wider mix — some authored in-house, some pulled from an existing library, some captured live from how the best people in the business already work. KnowHow’s AI-powered course creation tools and course management capabilities sit naturally here — they make it realistic to author, tag, and maintain that kind of granular content without a content team five times the size.
The third shift is the least glamorous and probably the most important. Every piece of content has to be tagged to the skills taxonomy — the same taxonomy the rest of the skills programme is built on. If a video, a course, a job aid, or a scenario practice can’t be traced back to specific skills at specific levels, it can’t be recommended intelligently, can’t be measured against capability movement, and can’t be connected to the development goals managers and employees are agreeing on.
This is the moment a lot of L&D teams hit a wall — not because the work is intellectually hard, but because retro-fitting tags onto a legacy library is a slog. The way through is to stop treating it as a one-off cleanup project and start treating it as the standard way new content gets in. From now on, nothing enters the library without a skill, a level, a context, and an owner. Over a few quarters, the catalogue turns into a library — and the library starts to behave like an asset rather than an archive. Linking those development goals back to the work is exactly where features like training goals and insightful analytics & reporting become useful, because the tags finally have somewhere to land.
It’s tempting to assume that AI quietly solves the content problem — that a clever model will generate whatever a learner needs in the moment and the library question goes away. Generative tooling really has changed what’s possible. It can draft outlines, summarise long content into short reference cards, translate, role-play, and personalise tone. What it can’t do is invent the organisation’s point of view on how work actually gets done here. That has to come from inside the business, captured deliberately, and curated as content.
In practice, AI raises the bar on the library rather than removing the need for one. The better the source material — well-tagged, current, written in the organisation’s own voice — the better the AI’s recommendations, summaries, and adaptive paths get. The L&D teams getting genuine value from AI aren’t the ones with the flashiest model; they’re the ones whose underlying content is in good enough shape for a model to work with.
Most of the leaders we speak to don’t describe the content shift as a project — they describe it as a slow, deliberate rebuild that runs underneath the bigger strategy. New content is born skill-tagged. Legacy content gets re-tagged when it’s touched, and quietly retired when it isn’t. Formats diversify; the catalogue stops being a wall of tiles and starts being a layered library that recommends differently depending on the skill, the level, and the person.
When that rebuild lands, the rest of the skills programme stops dragging. Managers can recommend specific things, not generic courses. Career and mobility conversations point at content that exists and fits. Analytics finally measures capability movement and not just clicks. The content layer becomes what it was always meant to be — not the archive at the end of L&D, but the working surface where strategy and people actually meet.
11 May 2026
After all the conversations about skills frameworks, manager engagement and capability analytics, every L&D leader I speak to eventually arrives at the same place: OK — we have the data. Now what do people actually do with it? In 2026, the answer that’s starting to separate strategic L&D from operational L&D is internal mobility. Once skills data is alive and trustworthy, it stops being a reporting layer and starts being the engine that helps people move — into projects, into new roles, into careers that don’t require leaving the company.
That shift is bigger than it looks. For two decades, learning and career conversations sat in different parts of the building. L&D ran courses. HR managed succession spreadsheets. Managers held annual career chats that mostly produced polite vagueness. In 2026, the organisations getting skills-based L&D right are the ones using their skills data to make those conversations sharper, faster, and finally, useful — both to the employee and to the business.
The career conversation has always been awkward. Employees often arrive without language for what they want; managers often arrive without information about what’s possible; HR closes the meeting with “let’s revisit this in six months.” That dynamic survives because both sides are missing the same thing — a shared, current view of what the person can actually do today and where those capabilities point next.
When skills are a living object inside the organisation, that whole conversation changes shape. Employees see their own skills profile and the level they sit at. Managers see how those skills map to other roles, projects, and stretch assignments. The conversation moves from “where do you see yourself in three years?” to something concrete — “these four skills are 70% of the way to this role; here are the two we’d close together this quarter.” That clarity is most of the magic.
In a traditional organisation, the org chart is the model of who can do what. It works at one level — reporting lines, headcount, layers — but it tells you almost nothing about capability. Two people in the same job title routinely have very different skill profiles, and the people best suited to a new opportunity are often nowhere near it on the chart.
Skills data flips that picture. Instead of “this is the role you sit in,” the system answers a more useful question: across the whole workforce, who has the skills (and the level of skills) this opportunity needs? That single shift unlocks a different operating model. Project leads can find internal talent without going through three layers of HR. People with non-obvious skill combinations get visible. Roles that would have defaulted to external hires get an honest internal-versus-external comparison for the first time. The org chart still exists, but it stops being the only map of the workforce.
Most internal mobility programmes don’t fail for lack of ambition. They fail because the underlying skills picture isn’t there. HR launches a talent marketplace, an internal opportunity portal, or a career-pathing tool — and within twelve months it’s a thin layer of role descriptions that don’t connect to anyone’s actual capabilities. Employees can’t see why they’d be a fit for the open project; managers can’t see who across the business might be. The marketplace becomes a job board with a friendlier brand.
The pattern is the same one we covered with capability measurement: without a stable, shared definition of skills, every downstream system is doing its own private translation work, and the answers don’t line up. With a taxonomy in place and skills signals flowing in from learning, performance conversations, and applied work, an internal mobility programme finally has something to stand on. The fit calculation gets honest. People start moving. The business retains capability it would otherwise have hired in or lost out the door.
“Career path” used to imply a ladder — junior, mid, senior, lead, manager, director. Some industries still need that scaffolding, but it isn’t where most careers actually move in 2026. Lateral moves, project work, stretch roles, hybrid roles that combine two adjacent disciplines — these are how capability compounds inside an organisation, and a rigid ladder can’t represent any of them.
In a skills-based system, a career path is something more useful: a shape in the skills graph. It’s the set of capabilities that distinguish where someone is from where they want to go, and the learning, projects, and feedback that will move them between the two. Some paths run up a familiar ladder; others move sideways into a new function; others fan out into a more senior, more cross-functional shape that doesn’t have a clean title. The skills data lets the organisation honour all of those, without forcing every conversation into a template that doesn’t fit. This is also where tools like KnowHow’s Career Aspirations and Skill-Will Matrix and Performance & Development Reviews earn their keep — they make the path visible, agreed, and trackable across both sides of the conversation.
The strategic reason CEOs and CHROs are spending real attention on this in 2026 is that the workforce numbers won’t bend on their own. Roles change faster than hiring pipelines can keep up. Skills shortages in critical areas don’t get solved by a single recruiter. The only sustainable answer is to grow people from the inside — and that requires knowing, with precision, what the inside actually has.
That’s the quiet promise of skills-based L&D when it crosses over into internal mobility. The same data that shows whether capability is moving across the business also shows which careers are available, which growth bets are realistic, and which gaps the organisation should be growing into rather than buying in. The L&D function that owns that data isn’t a training department anymore. It’s a critical layer of how the business builds itself for the next three years.
06 May 2026
After the strategy slides, the taxonomy work, the manager training, and the learning-in-the-flow-of-work pilots, every L&D leader eventually runs into the same uncomfortable question — and it almost always comes from a CFO or a CEO. OK. Is any of this actually working? In 2026, the organisations getting skills-based L&D right are the ones that have stopped trying to answer that question with the old metrics and have rebuilt the way they measure capability from the ground up.
Because here’s the catch: skills-based L&D and traditional L&D measurement aren’t just misaligned — they’re built on completely different assumptions about what success looks like. You can’t run a skills-based strategy and report on it with course-completion dashboards, any more than you can run a modern engineering team using lines-of-code as a productivity metric. The numbers will look fine. The story they tell will be wrong.
Traditional L&D reporting was designed for a world where the deliverable was the course. Completion rates, hours of training delivered, post-course NPS, mandatory compliance percentages — these are operational metrics. They tell you whether the L&D function is functioning. They don’t tell you whether anyone in the business is more capable than they were six months ago.
That gap stayed invisible for a long time because nobody was asking. As long as the dashboards turned green and the audits passed, the question of “are people actually getting better at their jobs?” sat in the too-hard pile. In 2026, with skills-based strategies in active rollout and finance teams asking pointed questions about return on capability investment, the gap is no longer ignorable. The metrics that made L&D defensible in the past are now actively misleading the people trying to steer it.
Measuring capability instead of activity means tracking three different kinds of signal, all anchored to the same skills taxonomy:
No single one of these tells you the whole story on its own. A passed assessment isn’t capability. A manager’s view that someone is “doing better” isn’t capability either. What matters is whether the three signals start to line up over time. When proficiency rises, the right behaviours show up in the work, and the related business outcomes improve for the same cohort, you have something close to genuine evidence that capability is moving.
Most organisations discover the limits of their reporting stack about three months into a serious skills-based effort. The LMS knows about courses and completions. The performance system knows about ratings and goals. The HRIS knows about roles and titles. None of them know about skills as a shared object — which means none of them can answer “how is capability X moving across the organisation?” without a quarterly heroic effort by someone in HR analytics with a spreadsheet and a long evening.
This is exactly why the taxonomy work matters as a foundation. Without a single, agreed list of skills with stable IDs, the analytics layer has nothing to attach to. With it, every learning event, every manager check-in, every assessment result, and every internal move can be tagged to the same underlying capabilities — and a real picture starts to emerge. The analytics question and the taxonomy question are, in practice, the same question approached from opposite directions.
The systems carrying skills-based L&D in 2026 don’t treat analytics as a reporting afterthought. They treat it as part of the operating model. Every time a learner finishes a piece of content, completes a goal, demonstrates a skill in a project, or receives feedback from a manager, the system writes a signal back against a specific skill at a specific level. Over weeks and months, those signals form a living picture of capability — at the individual, team, and organisation level — that doesn’t need a quarterly stitch-together to make sense.
This is where KnowHow’s Training Goals and skills analytics earn their keep. Because every goal is tied to a defined skill at a defined level, and every learning interaction feeds the same model, the data is consistent by design rather than reconciled after the fact. Managers see exactly which skills their team is building, where gaps are widening, and which interventions are actually shifting the dial. L&D leaders see capability movement across the business, not just course traffic. And executives finally get a view of the workforce’s skills that means the same thing in May as it did in March.
There’s an old line that you become what you measure. For two decades, L&D has been measuring courses delivered and tickets closed — and it has, broadly, become a function that delivers courses and closes tickets. The shift to skills-based L&D is, at its core, a decision to start measuring capability instead. That choice quietly forces every other part of the system — content, manager conversations, learning experiences, taxonomy, technology — to reorganise around the thing that actually matters. In 2026, the L&D functions winning the budget conversation are the ones that have stopped reporting on activity and started reporting on capability.
28 April 2026
Most skills-based L&D strategies stall in the same place. Not at the platform. Not at the content. Not even at manager engagement. They stall the moment a leader asks a deceptively simple question: which skills, exactly, are we developing? And the answer comes back from three different parts of the business in three different vocabularies. In 2026, the organisations making real progress on capability are the ones quietly fixing this first — by investing in a clear, shared skills taxonomy before they invest in anything else.
A skills taxonomy isn’t glamorous. It doesn’t show up in keynote slides or vendor demos. But every meaningful capability decision an organisation makes — what to develop, who to promote, where to hire, which roles to redesign — depends on a shared language for what “skill” actually means. When that language is missing, even the best learning content lands inconsistently, manager conversations fragment, and analytics produce numbers that nobody quite trusts.
Walk into most mid-sized organisations and you’ll find half a dozen lists of skills, all real, all in active use, and almost none of them in agreement. Recruitment uses one taxonomy in job ads. The performance review system uses another in its rating scales. L&D has its own list inside the LMS. A succession-planning spreadsheet somewhere uses a fourth. Each list was built for a sensible reason; none of them speak to each other.
The cost of this fragmentation only becomes visible when an organisation tries to do anything strategic with skills. Workforce planning becomes guesswork. Internal mobility stalls because no one can match a person’s capabilities to a different role with confidence. Reskilling investments are made without a baseline to measure them against. And every dashboard that claims to show “skill levels” is quietly stitching together data that was never designed to be compared.
The skills taxonomies that work in 2026 don’t look like the bloated competency frameworks of a decade ago. Those tended to be exhaustive, theoretical, and impossible to maintain. Modern taxonomies are smaller, more pragmatic, and built to be lived in:
Done well, this kind of taxonomy quietly becomes the operating layer underneath everything else: career pathways, learning recommendations, skills gap analysis, manager development conversations. It’s the piece that lets a “skills-based” strategy actually behave like a system rather than a slogan.
Historically, building a skills taxonomy was a heavyweight project. A consultancy would interview stakeholders for months, produce a 400-page framework, and hand it over to an HR team that had neither the bandwidth nor the tooling to keep it current. Within eighteen months it was out of date; within three years it was quietly abandoned.
What’s changing in 2026 is the toolset. AI-assisted skills extraction can read job descriptions, learning content, and performance data and propose a coherent skills model in days, not months. That doesn’t remove the need for human judgement — taxonomies still need to be validated by the people who actually do the work — but it dramatically lowers the cost of getting started, and even more importantly, the cost of keeping the taxonomy alive as roles evolve. The result is that organisations no longer have to choose between an unmaintainable monster of a framework and having no shared skills language at all.
A skills taxonomy that lives in a document is a research project. A taxonomy that lives inside the platforms people actually use every day is infrastructure. This is where the choice of LMS matters more than it used to. The systems carrying skills-based L&D in 2026 aren’t course-delivery engines with a skills bolt-on; they’re built around skills as a first-class concept — connecting content, training goals, manager conversations, and analytics to the same underlying skills model.
KnowHow’s Training Goals and skills analytics are designed exactly around this principle. When every learning goal, every development conversation, and every progress signal is anchored in the same shared skills definitions, the picture finally lines up. Managers see what their team is actually growing into. L&D sees where capability is moving across the business. And leaders get a view of organisational skills that means the same thing on Tuesday as it did on Monday.
It’s tempting to treat a skills taxonomy as a back-office detail — something to clean up after the strategy is set. The organisations getting skills-based L&D right are doing the opposite. They’re investing in the shared language first, because they’ve recognised that without it, every downstream initiative — from learning in the flow of work to manager-led development to performance-linked outcomes — is built on sand. In 2026, the unglamorous work of agreeing what a skill is, and naming it the same way everywhere, is quietly becoming the most strategic thing an L&D function can do. Explore how KnowHow helps organisations build a skills taxonomy that actually lives inside their learning ecosystem.
21 April 2026
There’s a quiet truth that most L&D teams know but rarely say out loud: the single biggest factor in whether a skills-based learning programme succeeds isn’t the content, the platform, or even the analytics. It’s whether the employee’s line manager is genuinely engaged. In 2026, as organisations race to rebuild their training strategies around capability rather than compliance, managers are emerging as the decisive — and chronically under-leveraged — lever.
For years, L&D has been positioned as a central function that designs and delivers development to the workforce. That model worked when learning was episodic. It struggles badly when development needs to be continuous, role-specific, and tied to real performance outcomes. The organisations pulling ahead aren’t those with the richest content libraries — they’re the ones treating every manager as an active partner in skills development.
Research across L&D functions consistently points to the same finding: engaged managers are the single biggest predictor of whether learning translates into performance. An employee whose manager supports, discusses, and reinforces development is several times more likely to apply new skills on the job than one whose manager treats training as an HR activity happening somewhere in the background.
The mechanism isn’t mysterious. Managers control the context in which learning is applied. They set the priorities that determine whether there’s time and permission to practise new skills. They give the feedback that tells an employee whether they’re actually getting better. And they decide which opportunities people are stretched into — which, more than any course, is where genuine skill development happens.
Despite all of this, most L&D programmes are still built with a gap at the centre: the manager. Learning is assigned by HR systems, completed by employees, reported in dashboards — and the manager is, at best, copied on a completion notification. They know their team member finished the course. They rarely have a clear picture of what skills the person was meant to develop, how they were developing them, or whether the investment is translating into anything the team actually needs.
This isn’t a failure of intent. It’s a failure of design. Most legacy LMS platforms were built to deliver content to individuals and report on completion — not to support ongoing capability conversations between managers and their teams. As a result, the manager-employee relationship, which is where skills development actually lives, has been systematically under-served.
In a skills-based model, the manager’s role shifts from passive observer to active co-architect of development. That shift is grounded in a few core practices:
KnowHow’s Training Goals were designed with exactly this model in mind. Rather than pushing learning at employees and hoping it sticks, Training Goals begin with a structured conversation between manager and employee, anchored in the real requirements of the role. The goals themselves become the focal point — the shared reference that gives both sides clarity, and gives L&D visibility into what’s actually being developed across the organisation.
One of the most common mistakes in skills-based L&D rollouts is assuming managers will naturally step into this expanded role. They won’t — not without support. Most managers were promoted on the strength of their technical performance, not their coaching ability. Asking them to lead meaningful development conversations without giving them the tools, frameworks, and confidence to do so sets the whole initiative up for uneven execution at best.
This is where the L&D function’s role evolves. Instead of being the sole provider of development, L&D becomes an enabler of a manager-led model: equipping managers with conversation frameworks, surfacing the right data at the right time, and designing platforms that make the manager’s job easier rather than adding to it. The best L&D teams of 2026 aren’t measured on how many courses they’ve delivered — they’re measured on how effectively they’ve activated the thousands of development conversations happening every week across the business.
Skills-based programmes where managers are genuinely engaged share a recognisable signature in the data. Skill progression is faster. Development activity is more consistent across teams. Employees report higher clarity about what they’re trying to grow into — and higher confidence that their development actually matters to the business. Those signals are measurable, and they tell a very different story than a completion rate ever could.
The real shift underway in 2026 isn’t just about moving from completion metrics to skills metrics. It’s about where development actually happens — and who drives it. In the organisations pulling ahead, the answer is increasingly clear: development lives in the relationship between manager and employee, and L&D’s job is to make that relationship as productive as possible. Explore how KnowHow helps organisations build a manager-led skills development model.
01 April 2026
For years, the default measure of L&D success was a familiar one: completion rates. Did your people finish the course? Did they pass the assessment? Tick the box. Move on. But in 2026, that model is finally — and irreversibly — breaking down. Organisations across industries are waking up to a harder truth: completing a course and actually developing a skill are two very different things. The shift to skills-based learning isn’t just a trend. It’s a fundamental rethinking of what workplace learning is for.
Course completion has always been a proxy metric — a stand-in for something we actually care about but struggle to measure. The problem is that proxies have a way of becoming the goal. When HR and L&D teams are measured on enrolments and completions, that’s what gets optimised for. Content gets shorter to improve finish rates. Assessments get easier to reduce drop-offs. And somewhere along the way, the actual purpose — equipping people to do their jobs better — gets lost.
Recent research confirms what many practitioners already suspected: organisations that prioritise skill acquisition over completion metrics report significantly higher performance improvement and stronger return on L&D investment. The gap between training activity and business impact isn’t a mystery — it’s a direct consequence of measuring the wrong things.
Shifting to a skills-first model requires more than rebranding your training catalogue. It demands a different starting point. Instead of “what content should we deliver?”, the question becomes “what capabilities does this role actually require, and how do we know when someone has developed them?” That shift sounds simple. The implications are profound.
It means development goals need to be specific and role-relevant — not generic competency frameworks that apply to everyone and no-one. It means learning needs to connect directly to the work people are doing, not sit alongside it as a separate activity. And it means measurement needs to move beyond completion to track actual capability change over time.
This is the principle behind KnowHow’s Training Goals feature. Rather than assigning learning and hoping it sticks, Training Goals are shaped through a conversation between employee and manager — grounded in real role requirements, agreed on together, and tied to meaningful performance outcomes. It’s not automated target-setting. It’s structured, intentional development.
One of the genuine breakthroughs of 2026 is AI’s ability to make skills-based content creation feasible at scale. The historical barrier was simple: creating tailored, role-specific learning content took too long and cost too much. Generic content was the pragmatic compromise. AI removes that constraint.
KnowHow’s AI-Powered Course Creation Tools allow L&D professionals to rapidly build quality, outcome-aligned courses and assessments — including automatically generating quizzes from existing content using the AI Quiz Generator. The result is content that’s specific enough to be genuinely useful, created quickly enough to stay relevant, and structured around the skills that actually matter for performance.
Skills-based learning only earns its place at the strategic table when it can demonstrate impact in language leadership understands. That means moving beyond completion dashboards to metrics that show capability change, performance improvement, and business outcomes.
KnowHow’s Insightful Analytics are built for exactly this purpose. L&D leaders can track skill progression across teams, identify where development is stalling, and present leadership with clear evidence of how learning investment is translating into workforce capability. It’s the difference between reporting on activity and demonstrating genuine organisational impact.
The organisations winning at L&D in 2026 aren’t those with the most content or the highest completion rates. They’re the ones who’ve made the harder shift: defining what capability looks like, building learning that develops it, and measuring whether it’s actually happening. That’s the work. And the right platform makes it possible. Explore how KnowHow supports skills-based development across your organisation.
25 March 2026
If your L&D strategy is still built around course completion rates and annual training calendars, 2026 has a message for you: that model is running out of runway. Across the globe, HR and L&D leaders are converging on a new approach — one that connects learning directly to skills, performance, and measurable business outcomes. It’s not a trend anymore. It’s the baseline expectation.
This shift is being driven by two forces colliding at speed: the rapid evolution of skills required in an AI-augmented workplace, and mounting pressure on L&D teams to prove return on investment. The organisations that are pulling ahead aren’t those with the most content — they’re the ones who’ve made learning inseparable from performance.
A recent Training Industry report confirmed what many L&D professionals already feel: there’s a persistent gap between training delivery and real-world skill application. Employees complete courses. Managers tick boxes. But when it comes to actual performance improvement, the needle barely moves. The culprit isn’t the people — it’s the model. Training designed around content consumption rather than skill development will always struggle to demonstrate impact.
Skills-based learning flips the equation. Instead of starting with “what content should we create?”, it starts with “what capabilities does this role actually require, and how do we develop and measure them?” It’s a subtle shift in framing, but the downstream effects on design, delivery, and measurement are profound.
One of the most common failure points in skills-based L&D is the absence of a clear, shared understanding between managers and employees about what “growth” actually means for a given role. Without that alignment, development becomes a guessing game — employees pursue content that interests them, managers hope it translates to performance, and L&D has no way of knowing if any of it is working.
KnowHow addresses this through Training Goals — a feature built around the principle that meaningful development starts with a conversation. Managers and employees work together to define specific, role-relevant growth objectives. Those goals become the anchor for learning activity, performance check-ins, and progress measurement. It’s not automated target-setting. It’s structured intentionality — supported by a platform that makes it easy to follow through.
Skills-based L&D only earns its seat at the strategic table when it can speak the language of business outcomes. That means moving beyond completion reports and into territory that answers questions like: which teams are building capability fastest? Where are the persistent skill gaps? What’s the correlation between learning engagement and performance scores?
KnowHow’s Insightful Analytics are designed to surface exactly this kind of intelligence. L&D leaders can track skill progression, identify where development is stalling, and present leadership with evidence-based narratives about how learning investment is translating to workforce capability. It transforms the L&D function from a cost centre into a strategic asset.
One of the most significant enablers of skills-based learning in 2026 is AI — specifically, its ability to dramatically accelerate content creation without compromising quality. Industry research shows that 85% of business leaders expect a surge in skills development needs over the next two years. L&D teams simply cannot create content fast enough using traditional methods to meet that demand.
KnowHow’s AI-Powered Course Creation Tools are designed to address this pressure directly. L&D professionals can rapidly create quality, outcome-aligned courses and assessments — including using the AI Quiz Generator to automatically create quizzes from course content. This isn’t about replacing instructional design expertise. It’s about augmenting it: freeing up your team’s time and energy to focus on the strategic, human-centred work that AI can’t do.
The ultimate goal of skills-based L&D isn’t a better training catalogue — it’s an organisation where learning is woven into the culture. Where people expect to grow, managers expect to develop their teams, and leadership invests in capability as a competitive advantage. That’s not an accident. It’s built through consistent processes, meaningful conversations, and platforms that make it easy to do the right thing.
KnowHow has been helping organisations build this kind of culture since 1999 — with an all-in-one LMS that integrates learning, performance, and skills development into a single, coherent experience. It’s not a generic training repository. It’s a platform built to transform training into business impact.
If you’re ready to move beyond course completion and start building a workforce that genuinely grows — explore what KnowHow can do for your organisation. The shift to skills-based learning starts with one conversation. Let’s have it.
18 March 2026
The conversation in HR and L&D has shifted — and it’s shifted fast. Gone are the days when a completed course certificate was evidence enough of capability. In 2026, the question organisations are asking isn’t “did they finish the training?” — it’s “can they actually do the job?” That’s the essence of skills-based learning, and it’s reshaping how forward-thinking companies build, develop, and retain their people.
With AI accelerating the pace of change in virtually every industry, and global skills shortages showing no sign of easing, L&D professionals are under pressure to move beyond compliance tick-boxes and generic learning libraries. The organisations winning the talent battle are the ones connecting learning directly to real performance outcomes — and backing it up with data.
Several forces are converging at once. AI is disrupting job roles faster than traditional training can respond. Talent shortages mean organisations can’t afford to overlook capable people simply because they lack a specific qualification. And boards are demanding measurable ROI from L&D investment — “we ran a course” no longer cuts it as evidence of success.
According to recent research, the most competitive organisations in 2026 are those that have embedded skills into the core of their workforce strategy — not just into their training calendar. Skills inform how they hire, how they develop people, how they plan for future roles, and how they measure whether investment is working.
Skills-based learning isn’t a platform or a product — it’s an approach. It starts with identifying the specific capabilities that matter for each role, then building learning experiences designed to develop and measure those capabilities directly.
In practical terms, this means:
This is where the right platform makes a significant difference. KnowHow’s Training Goals feature is built around exactly this principle — development goals are shaped through meaningful conversations between employees and their managers, ensuring alignment with both individual growth and real business priorities. The focus is always on skills and outcomes, not just activity.
One of the biggest frustrations for L&D leaders is the inability to demonstrate impact. You know learning is happening. You suspect performance is improving. But when the CFO asks for evidence, the best you can offer is a spreadsheet of course completions.
Skills-based learning changes that equation. When learning is tied to specific competencies, and those competencies are tied to performance data, the evidence becomes visible. You can show which skills have improved, which teams are growing, and where gaps still exist.
KnowHow’s Insightful Analytics are designed for exactly this — turning learning data into actionable insights that help HR and L&D leaders make confident decisions and demonstrate the genuine business value of their work.
The good news is that moving toward a skills-based approach doesn’t require a complete overhaul of your L&D function. Start with one team or one role. Identify the three or four competencies that genuinely matter for performance in that role. Build or curate learning that develops those specific capabilities. Assess application, not just completion. Review progress in performance conversations.
That’s a skills-based learning programme. It’s not complicated — but it does require intentionality, and the right tools to support it.
The organisations that make this shift in 2026 won’t just see better training outcomes. They’ll see better business outcomes — and they’ll be able to prove it. Explore how KnowHow supports skills-based development →