The Case Against One-Size-Fits-All Skills Taxonomies
The last post in this series walked through why ONET, ESCO, SFIA, and Lightcast each answer a different question. That’s uncomfortable news for anyone asked to pick “the” skills taxonomy for an institution. No single framework serves a community college, a hospital system, and an advanced manufacturer equally well.
Here’s how it usually plays out. An institution adopts a framework, often because a grant or vendor contract assumed it. The team tags the programs that map cleanly, usually business and technology. Then they hit the ones that don’t: an allied health program built on clinical competencies, or a trades program built around an industry body’s own standards. Each needs a crosswalk built by hand, and someone has to maintain it every time the framework updates. Nobody budgeted for that. A year or two later, the tagging is stale, half the catalog was never covered, and nobody trusts the “skills-aligned” label.
The US and the EU describe jobs using different systems, ONET and ESCO. Neither replaced the other. Instead, both were built to line up with a third, international list called ISCO. To find the EU equivalent of a US job, you look up the US job’s ISCO code and find the EU job with the same code. ISCO acts as a hub, so the two systems never have to be reconciled directly. That hub exists for jobs, but nothing like it exists yet for skills, which is why skills tagging keeps breaking down.
The OECD argues that employers and educators need a shared skills language, and they’re right. But shared can mean translatable, the way ISCO makes ONET and ESCO translatable. It doesn’t have to mean everyone uses the same framework. Forcing one framework on everyone fails in predictable ways. A hospital put on SFIA, which was built for technology roles, has no way to describe the clinical judgment that separates an experienced ICU nurse from a novice. A manufacturer hiring CNC machinists needs the shop-floor detail in NIMS standards and gets almost none of it from ONET. A few extra fields won’t fix that, because the framework doesn’t have the vocabulary.
So start from the assumption that hospitals, colleges, and manufacturers will keep speaking different vocabularies, and build the translation between them as core infrastructure from day one.
Naming a skill correctly and having someone else recognize it are two different problems. The next post takes on the second: what makes a digital badge worth an employer’s trust.
Lead Photo by Sahil Singh
References
- OECD. (2026). A Skills-First Labour Market: Positioning skills as the new currency of work. Getting Skills Right, OECD Publishing. Retrieved from https://www.oecd.org/en/publications/a-skills-first-labour-market_2e1b85f0-en/full-report/positioning-skills-as-the-new-currency-of-work_40815b16.html
- National Center for ONET Development. (n.d.). ONET Overview. Retrieved from https://www.onetcenter.org/overview.html
- European Commission, Directorate-General for Employment, Social Affairs and Inclusion. (2025). What is ESCO? Retrieved from https://esco.ec.europa.eu/en/about-esco/what-esco
- SFIA Foundation. (n.d.). About SFIA. Retrieved from https://sfia-online.org/en/about-sfia
- Lightcast. (n.d.). Lightcast Open Skills Taxonomy. Retrieved from https://lightcast.io/open-skills
