Everyone is going skills-based. Almost nobody has arrived.
The strategy decks agree. Gartner found that 74% of HR leaders believe most organisations are moving to a skills-based talent model. Then the same research asked how far they had actually got: 2% had adopted a skills-based approach across all their talent processes. 41% had managed some. Half were still thinking about it and had not started.
That is not a rounding error. That is a category-wide failure to convert intent into an operating model.
The pressure driving the intent is real. Deloitte's research — 1,021 workers and 225 business and HR executives — found that 63% of the work being performed today falls outside people's core job descriptions, 81% say work is increasingly performed across functional boundaries, and 36% say work is increasingly done by people outside the organisation who have no defined job at all. The job description has quietly stopped describing the job.
The prize is real too. Organisations that get past the intent stage report being 79% more likely to provide a positive workforce experience and 63% more likely to achieve results.
So the destination is attractive and the pressure is genuine. Why does almost everyone stall?
Because "becoming skills-based" gets treated as a data project — build the taxonomy, populate the profiles, buy the platform — when it is actually a decision project. A skills-based organisation is not one that holds a list of everyone's skills. It is one where real decisions about people are made on proof of capability rather than proxies. Everything else is inventory.
Why it stalls: three failure modes
1. The taxonomy trap
The programme starts by buying or scraping a large skills list and tagging everyone against it. This feels like progress because it produces something visible quickly. But a list of skill names has no levels, no relationships and no evidence rules — so it can name a skill and never assess one. Teams end up with a beautiful vocabulary and still cannot answer "is this person's Python good enough for this role?" We have written about the gap between a taxonomy and an ontology in detail; it is the single most common place these programmes die.
2. The unverified-inventory trap
The graph gets populated from self-assessment, manager ratings and résumé inference. Now you have data about everyone and trust in none of it. Self-ratings are miscalibrated in both directions. Manager ratings encode proximity and recency as much as capability. Inference from a profile is educated guessing at scale. The moment a real decision rests on that data and someone challenges it, the whole thing collapses — and the programme loses its mandate along with it.
3. The big-bang trap
The transformation is scoped as "re-architect every role in the company around skills." That is a multi-year effort whose payoff arrives long after the sponsor has moved on. It is also the version most likely to be cancelled in the first budget squeeze, precisely because it has produced no decision-level result yet — only artefacts.
The transformation in five moves
Move 1 — Start from a decision, not an inventory
Pick one decision that is made repeatedly, made badly today, and has an owner who feels the pain. Good candidates: who gets shortlisted for this role, who is ready for the next level, who can we redeploy instead of backfilling, did that training actually change anything.
A decision gives you scope discipline, which is the scarcest resource in these programmes. You do not need every skill for every person — only the skills that this decision turns on. In practice that is eight to twenty skills, not three thousand. Write down the decision, what currently feeds it, and exactly how it currently fails.
Move 2 — Turn the list into a model
For that narrow set of skills, define what the proficiency levels actually mean and what evidence would count as proof at each level. This is the step from taxonomy to ontology: hierarchy, levels, relationships and evidence rules.
It is the least glamorous move on this list and it is the whole ballgame. A scale without evidence rules is just an opinion with numbers attached to it — and it will not survive contact with a disappointed candidate or a challenged promotion.
Move 3 — Get proof for the few skills that matter
Now measure, and be honest about what each method actually yields. Inference predicts. Testing samples. Completion records attendance. Only proof survives a challenge.
Match the method to the skill, because not all skills prove the same way: objection-handling shows up inside a single call, whereas negotiation only proves out across a whole deal. Applying one instrument to both measures neither of them well.
The bar to hold yourself to is simple: could you defend this rating, with evidence, to the person it disadvantaged? If not, it is not proof yet.
Move 4 — Wire proof into the decision, and let it change the outcome
Put the evidence in front of the decision-maker at the moment of the decision — inside the shortlist, the succession review, the staffing conversation — not in a dashboard they would have to remember to visit.
Then watch for the only signal that matters: does the decision come out differently? If your shortlists are identical to what gut feel would have produced, you have built reporting, not a skills-based organisation. Record the rationale alongside the decision, so the reasoning is auditable a year later when someone asks why.
Move 5 — Re-verify, so the graph does not rot
Skills decay. An unrefreshed skills graph becomes a liability within about eighteen months — and a worse one than having no graph at all, because by then people have started trusting it.
Set a freshness policy per skill; fast-moving technical skills expire far quicker than durable ones. This is also where compounding begins: each decision generates fresh evidence, which sharpens the next decision. One proven loop that compounds beats forty roles mapped once and never revisited.
What "done" actually looks like
Most organisations that describe themselves as skills-based are in the left-hand column below. The distance between the columns is not tooling — both look identical in a product demo. It is whether anything underneath the rating can be produced on demand.
Tagging jobs with skills is not the same as deciding on skill. That distinction is most of the distance between 74% and 2%.
The sequencing mistake that costs a year
Almost every stalled programme did Move 2 before Move 1 — built the ontology for the whole enterprise before knowing which decision it had to serve.
You cannot define "what evidence would count" in the abstract. Evidence is only ever sufficient relative to a decision. Choose the decision first, and most of the modelling questions answer themselves.
The second most expensive mistake is doing Move 3 for every skill at once. Proof costs real time and money to produce. Spend it where a decision actually turns on it, and accept lighter signals everywhere else.
Where to start on Monday
Key takeaways
- 74% of HR leaders say they are going skills-based; only 2% have adopted it across their talent processes. The gap is execution, not intent.
- The transformation fails as a data project and succeeds as a decision project — start from one decision that is made repeatedly and badly.
- Scope to the eight to twenty skills that decision turns on, then define what each proficiency level means and what evidence would prove it.
- Match the measurement method to how the skill actually shows up in work; hold the bar at "could I defend this to the person it disadvantaged?"
- You have succeeded when the decision changes — not when the dashboard exists. Then re-verify on a policy so the graph does not rot.
Name one people decision your organisation makes repeatedly and badly. List the skills it turns on. For those skills only, write down what each level means and what would prove it. Measure them with a method that fits how each one shows up in real work. Put the result in front of the person making the decision — and check next quarter whether the decision changed.
That is one loop. A skills-based organisation is that loop, repeated, until it is simply how the place runs.