What is a competency matrix?
A competency matrix is a table that lists competencies (such as communication or problem solving) against roles, career levels or employees, with each cell stating the proficiency expected or demonstrated. A competence matrix, the spelling used in some countries, means the same thing.
A competency matrix — sometimes called a capability matrix or skills-and-competency matrix — is a structured table that maps either roles or employees against a defined set of competencies. Each cell in the grid contains a proficiency level: either what is required for a role at a given career level, or what a specific employee has currently demonstrated.
Used well, a competency matrix serves three distinct purposes. It makes promotion criteria explicit so employees understand exactly what the next level expects. It surfaces skill gaps so development plans target the right things. And it gives calibration sessions a shared reference point so managers across teams apply consistent standards.
Key components of a competency matrix
A well-built competency matrix has four elements working together:
- Competency list. The rows of the matrix. These should be drawn from your competency framework — not invented per review cycle. Typical competencies include communication, technical depth, problem solving, delivery, ownership, collaboration, and leadership. The list for an individual contributor matrix differs from a management matrix.
- Proficiency scale. A 1–5 scale (Foundational → Developing → Proficient → Advanced → Expert) works well across most organizations. Each number maps to a behavioral description in the framework, not just a vague label.
- Role or employee axis. The columns. A role-based matrix shows required levels per job level (L1–L5); an employee-based matrix shows each person's current ratings.
- Gap indicators. Calculated as required level minus demonstrated level. A positive gap means a development need; zero or negative means the employee meets or exceeds expectations for that competency at their current level.
Competency matrix vs. competency framework vs. skills matrix
| Term | What it is | Primary use |
|---|---|---|
| Competency Framework | Defines competencies, behavioral descriptions per level, and job families | Source of truth — governs all evaluation |
| Competency Matrix | Grid of roles/employees × competencies with required or actual proficiency scores | Review calibration, promotion decisions, IDP targeting |
| Skills Matrix | Inventory of current team capabilities against required skills | Staffing, training planning, hiring gap analysis |
A competency matrix requires a competency framework to exist first. A skills matrix is a standalone snapshot; it does not require level definitions or behavioral rubrics. Both tools are useful and complementary — many organizations maintain both. See our competency matrix template and skills matrix template to start with either.
Competency matrix vs skills matrix: what is the difference?
A competency matrix measures behaviors against the standard set for a role or level, while a skills matrix inventories what people can do today. The two share a grid shape but answer different questions.
| Competency matrix | Skills matrix | |
|---|---|---|
| What it measures | Observable behaviors against expectations for a role or level | Current ability in specific tools, methods or knowledge areas |
| Who uses it | HR and managers, for reviews, promotion and development | Team leads and project managers, for staffing and training |
| Typical scale | 1 to 5, each level tied to a behavior description | 0 to 4, from no knowledge to can teach others |
Competency map vs competency matrix
A competency map shows which competencies a role, team or organization needs, usually as a list or diagram grouped by theme. A competency matrix adds the proficiency level for each competency, so a map says what matters and a matrix says how much of it is expected or shown. Many teams draw the map first, then turn it into a matrix.
Competency matrix example for employees
A competency matrix for employees rates each person against the same competencies and level descriptions. The example below is a generic role with four competencies and three levels.
| Competency | Level 1: Developing | Level 2: Proficient | Level 3: Advanced |
|---|---|---|---|
| Communication | Shares updates when asked | Gives clear, timely updates without prompting | Adapts message to audience and aligns stakeholders |
| Problem solving | Solves defined problems with guidance | Finds root causes and proposes fixes independently | Solves ambiguous problems and prevents repeat issues |
| Ownership | Completes assigned tasks on time | Drives work to completion and flags blockers early | Owns outcomes across teams and unblocks others |
| Collaboration | Works well with immediate teammates | Shares knowledge and asks for input across the team | Builds working relationships across functions and mentors others |
To use it, mark the level each employee shows for each competency, then compare it with the level required for their role. The difference is the gap.
How to use a competency matrix in performance reviews
The most common application is to rate employees against the competency matrix during a review cycle. The process works as follows:
- Pull the matrix for the employee's role and level. A senior engineer should be evaluated against senior-engineer expectations, not the average across all engineers.
- Collect self-ratings first. Ask the employee to rate themselves before seeing the manager's ratings. Self-manager divergence above one point on any competency is a signal worth discussing.
- Manager rates based on observed behaviors. The behavioral descriptions in the framework anchor the ratings — "has she consistently demonstrated L3 ownership behaviors?" not "how do I feel about her performance?"
- Use the matrix in calibration. When multiple managers discuss employees together, the matrix makes the conversation concrete. Disagreements surface as specific cell-level disputes, not vague impressions.
- Use the gaps to drive IDPs. Any competency with a gap of 2 or more points is a natural focal point for the employee's development plan.
Common mistakes
Three patterns cause competency matrices to become shelfware:
- Too many competencies. A matrix with 20+ competencies takes hours to complete and produces little signal. Eight to twelve competencies — divided between core (everyone) and functional (role-specific) — is the practical ceiling.
- Vague behavioral descriptions. If the level-3 descriptor for "ownership" reads "takes responsibility," it is useless for calibration. Descriptions must be observable: "drives projects to completion without prompting and surfaces blockers before they become critical."
- Reviewing the matrix once a year. A competency matrix becomes stale as roles evolve. A quarterly check-in — even just a 15-minute 1:1 discussion of one competency — keeps it alive and prevents review-season surprises.