What is competency mapping?

Most HR teams know what competencies are. Fewer can explain how they fit together inside a framework that actually drives assessments, development plans, and hiring decisions. What is competency mapping? It is the process of defining the specific knowledge, skills, and behaviors required for each role in your organization, then organizing them into a structured hierarchy that HR can assess against. Without it, every assessment is built from scratch and every development plan is a guess.

What is competency mapping? Competency mapping is the process of identifying and organizing the knowledge, skills, and observable behaviors required for each role into a structured framework. It connects job requirements to assessment criteria and development actions, giving HR a single reference point for evaluating and growing talent across the organization.

The three layers of a framework

A competency framework is not a flat list. It operates on three levels, each serving a different purpose.

The top layer holds root categories. These are broad domains like “Leadership,” “Communication,” or “Technical Operations.” Huneety’s master taxonomy includes 20 root categories drawn from SFIA 9 and Korn Ferry methodologies. Root categories help HR teams organize hundreds of skills into a navigable structure.

The middle layer holds competencies. Each root contains between 5 and 25 competencies. A competency is a specific, assessable capability: “Stakeholder Management,” “Data Analysis,” “Conflict Resolution.” Across all 20 roots, the Huneety taxonomy includes 300+ competencies, each with a 20-50 word definition written in observable language.

The bottom layer holds skills. Each competency breaks down into 3-15 skills. A skill is the most granular unit: “Facilitates cross-functional alignment meetings” or “Writes SQL queries for reporting dashboards.” Huneety’s library contains 1,700+ pre-built skills.

Knowledge, skill, and behavior

Every competency contains a mix of three elements, and confusing them is one of the most common mapping mistakes.

Knowledge is what someone knows: regulatory requirements, industry standards, product specifications. Knowledge is necessary but not sufficient. Knowing the theory of conflict resolution does not mean someone can de-escalate a live dispute.

Skill is what someone can do: run a financial model, configure a CRM workflow, facilitate a workshop. Skills are observable and measurable. They show up in outputs.

Behavior is how someone applies knowledge and skill in context. It covers judgment, consistency, and interpersonal patterns. “Proactively shares project risks with the team before escalation” is a behavior. It cannot be taught in a classroom alone. It develops through practice, feedback, and reinforcement.

The reason this distinction matters for mapping: assessment items must target the right element. You test knowledge with questions. You test skills with tasks. You test behaviors with multi-rater observation, which is why 360-degree assessments are the standard tool for behavioral competencies.

Behavioral vs. technical split

Each skill in a mapped framework falls into one of two categories: behavioral or technical.

Behavioral skills describe how someone works. Communication, collaboration, decision-making, coaching. They apply across roles and industries. Technical skills describe domain-specific capabilities. Python development, clinical trial management, HVAC system design.

The rule is a floor, not a ratio: at least one third of competencies must be behavioral. Core behavioral competencies predict long-term performance more reliably than technical skills alone, especially at management levels and above. Technical skills can be trained. Behavioral patterns are harder to shift. Past the one-third floor, the mix depends on the role and the industry.

Why competency mapping matters for HR

Without a mapped framework, three problems repeat across every HR function.

Assessments have no anchor. Raters evaluate people against personal standards rather than shared definitions. One manager’s “exceeds expectations” is another’s “meets.” Results are not comparable across teams, and gaps cannot be aggregated at the organization level.

Development plans are disconnected from business needs. When there is no framework linking roles to required competencies, IDPs become wish lists. Employees pick training they find interesting rather than training that closes a verified gap. The 70/20/10 model (70% on the job, 20% through others, 10% formal learning) only works when the target competencies are defined first.

Hiring criteria drift with every recruiter. Job descriptions list requirements, but without a mapped framework, interviewers evaluate candidates against different mental models. Structured interviews require structured competencies behind them.

Competency mapping solves all three by giving HR a shared, assessable vocabulary. It does not need to be complicated. It needs to be specific, observable, and maintained.

Three paths to a mapped framework

Organizations typically build their framework through one of three approaches.

Import an existing standard. Frameworks like SFIA 9 or Korn Ferry provide a validated starting point. The risk is that industry-standard language may not match your organization’s vocabulary. A “translation model” maps your terms to the standard.

Build manually from job descriptions and SME interviews. This produces the most culturally accurate framework but takes 3-6 months for a mid-size organization. Quality depends entirely on the HR team’s discipline in writing observable definitions.

Generate with AI. Huna, Huneety’s AI assistant, generates framework drafts from job descriptions in minutes. HR reviews and adjusts rather than starting from a blank page. The AI handles the structure; the HR team owns the judgment.

Most organizations use a hybrid: start from a standard or AI-generated draft, then customize the vocabulary and add role-specific skills.

If your team is planning a competency mapping project or needs to update an existing framework, start with a conversation about your requirements. Huneety’s team can scope the project and recommend the right approach for your organization.