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.

The Taxonomy Is the Quiet Dependency

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.

Why Frameworks Get Too Big to Use

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.

Borrowed Language, Local Meaning

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.

A Living Framework Needs an Owner and a Rhythm

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.

Small Enough to Be Believed

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.