<\/p>\n
Guide \u00b7 14 min read \u00b7 Updated Feb 2026<\/p>\n
Why 150 core skills beat a catalog of thousands \u2014 and how to build a competency model that HR can actually use.<\/p>\n
<\/p>\n
Contents<\/p>\n
\n
\n<\/p>\n
Definition<\/p>\n
A competency model is a structured framework that defines the skills, knowledge, and behaviors employees need to succeed in their roles. It goes beyond a simple list of skills \u2014 it organizes competencies into categories, defines proficiency levels, and maps them to specific positions.<\/p>\n
Think of it as the “operating system” for your talent management. While a job description tells someone what<\/em> to do, a competency model tells them how well<\/em> they need to do it \u2014 and what growth looks like from beginner to expert.<\/p>\n A well-implemented competency model gives your organization a shared language for skills, objective criteria for hiring and promotions, clear development paths for employees, a foundation for gap analysis, and data-driven succession planning.<\/p>\n <\/p>\n Competency Model vs. Competency Framework<\/p>\n The terms are often used interchangeably. Strictly speaking, a framework<\/strong> is the broader structure (categories, levels), while a model<\/strong> is the specific implementation for your organization. In practice, the distinction rarely matters.<\/p>\n<\/div>\n<\/div>\n The Real Challenge<\/p>\n Before we talk about what a good competency model looks like, let’s address the elephant in the room: most companies already have skill data \u2014 and it’s a mess.<\/strong><\/p>\n The traditional approach to skill management is the “skill catalog”: a list of every skill relevant to the company, organized in a tree structure. In practice, 90% of a skill catalog consists of products, technologies, and tools. Since there are thousands of these, the catalog mushrooms into an unmanageable beast.<\/p>\n <\/p>\n Skill catalogs are too detailed to be useful for reporting. Skills must be aggregated. Doing this manually is a daunting task.<\/p>\n \u2014 Lessons Learned from Migrating to AI Skill Management<\/a>, dec\u00eddalo Blog<\/p>\n<\/div>\n This is the reality at many IT consulting and services firms: HR maintains a skill catalog in their HR system. The business needs detailed, up-to-date skill data for sales and staffing. The HR system doesn’t deliver what the business needs. So the business builds its own tools \u2014 Word CVs, Excel trackers, SharePoint lists. Now there are multiple disconnected systems with overlapping, outdated data.<\/p>\n The core issue is that a catalog of 2,000+ skills is too granular for strategic decisions<\/strong> and too rigid for daily operations<\/strong>. HR can’t report on thousands of skills. Employees hate maintaining profiles against a massive list. And the catalog is always behind \u2014 new technologies emerge faster than anyone can curate.<\/p>\n The insight that changes everything: you don’t need to catalog thousands of skills. You need ~150 core skills.<\/strong><\/p>\n These core skills are the competency model. They’re the skills that matter for reporting, gap analysis, and strategic planning. They’re small enough in number to be manually curated and kept meaningful.<\/p>\n Everything below that layer \u2014 the thousands of specific technologies, tools, and products \u2014 can be handled by AI. Large Language Models know more about “Kubernetes” or “SAP S\/4HANA” than any skill catalog ever could. They can extract, classify, and assess detailed skills from free text like CVs, project descriptions, and job postings.<\/p>\n <\/p>\n Your competency model. Manually curated. Used for reporting, gap analysis, role profiles.<\/p>\n<\/div>\n Technologies, tools, products. AI-curated. Extracted from CVs, project data, and free text by LLMs.<\/p>\n<\/div>\n<\/div>\n This two-layer approach is what modern skill management looks like. The competency model (the top layer) is what this guide helps you build. The bottom layer is what AI handles for you.<\/p>\n<\/div>\n<\/div>\n Building Blocks<\/p>\n Every effective competency model has five building blocks.<\/p>\n <\/p>\n Categories group related skills into themes, making the model navigable. A typical model has 5\u20138 categories. For an IT consulting firm, these might be Technical Expertise, Consulting & Advisory, Project Management, Industry Knowledge, Leadership & People, and Business Development.<\/p>\n <\/p>\n These are the specific competencies within each category. Unlike a traditional skill catalog with thousands of entries, you aim for 100\u2013200 core skills total<\/strong> \u2014 the ones that matter for strategic decisions. Each skill needs a clear, concise name and a brief description.<\/p>\n How many core skills is enough?<\/p>\n Fewer than 50 is too superficial for meaningful differentiation. More than 250 becomes another unmanageable catalog. The sweet spot is 100\u2013200 core skills<\/strong> across 5\u20138 categories \u2014 enough for reporting, yet small enough to maintain quality.<\/p>\n<\/div>\n <\/p>\n Proficiency levels define what “good” looks like at different stages. In practice, three levels are enough<\/strong>.<\/p>\n
\n
\n<\/p>\nThe Problem with Traditional Skill Catalogs<\/h2>\n
Why catalogs fail<\/h3>\n
The modern alternative: Core Skills + AI<\/h3>\n
\n
\n<\/p>\nComponents of a Competency Model<\/h2>\n
1. Competency Categories<\/h3>\n
2. Core Skills (~150)<\/h3>\n
3. Proficiency Levels<\/h3>\n