The skills matrix: from a list to a decision-making instrument
Echipa HR 365 · reviewed 2026-09-02 · 5 min read
A skills matrix puts people on rows, skills on columns and a level in each cell. Its value is not the inventory but the gaps: columns where a single person knows how to do something are your operational risk, and they show up in no other report.
What goes on the columns
Not qualities and not course titles, but things somebody does that can be verified. “Responsibility” is not a skill; “closes the month in accounting without help” is. The test: if you cannot say who on the team would take the task on tomorrow, the wording is too vague.
The optimal number of columns is between eight and fifteen for a team. Below eight the matrix has nothing to show; above fifteen nobody fills it in properly and every cell lands on the middle level.
The levels: four, with operational definitions
| Level | What it means | The practical test |
|---|---|---|
| 0 — does not do it | Has not worked in this area | You would not give them the task even with supervision |
| 1 — with help | Can do it if somebody checks | You would give them the task, but you would check the result |
| 2 — autonomous | Does it alone, at the expected quality | You would give them the task and not check |
| 3 — can teach it | Does it and explains it, catches other people’s mistakes | You would have them train somebody new |
Three kinds of gap, three different decisions
A gap in the matrix is not a problem in itself. Its shape matters, and the three shapes call for answers with nothing in common:
- A column with a single person at level 2 or 3 — a continuity risk. If that person is away for a week, something stops. The answer is skill transfer, not hiring: somebody at level 1 has to reach level 2 within a few months.
- A column completely empty, but necessary — a capacity gap. Here the answer is recruitment or outsourcing, because there is nobody internally to learn from.
- A row with many zeros — a person in the wrong role, or not integrated. Solved with an individual plan, not a decision about the team. If it appears in somebody with tenure, the question is what changed.
The first kind is the most frequent and the most ignored, because it does not hurt until the day that person takes leave. An honestly completed matrix shows it at a glance — which is why it is worth completing honestly.
How you fill it in without everything landing in the middle
The procedure that produces usable data
- Manager — fills it in first, alone, without asking the team — based on what they have seen, not what they were told
- Each person — fills in their own row, separately, on the same scale
- Manager and person — compare in a one-to-one only the cells differing by two levels; the rest are accepted
- Manager — picks at most two cells per person to move up one level over the next six months
- HR — aggregates across the team and looks for columns with a single 2 or 3 — those go into the training plan
The fourth step is the limit that separates a plan from a wish list. Two cells per person, over six months, is a sustainable pace. Ten means none of them will happen.
What you use it for beyond training
- Leave planning: two people covering the same single-holder column cannot be away in the same period.
- Distributing work: who can take on a new piece without blocking something else.
- Recruitment: the job description is written from the empty columns, not from the previous employee’s description.
- The decision to outsource: a column with zero people and rare demand is almost always cheaper bought than built.
How you avoid level inflation
Any matrix filled in repeatedly tends to drift upwards. Nobody enjoys moving somebody down, and within two years the levels become a list of twos and threes that describes nothing. Three simple measures stop it:
- Level 3 is awarded only if the person has actually trained somebody in that skill. Not “could”, but did — it is the only level with verifiable evidence, and that is why it anchors the whole scale.
- At each update, the manager justifies the increases, not the unchanged levels. The effort goes where the change, and the inflation risk, is.
- If a skill has not been used for over a year, the level drops automatically by one. Not as a sanction — that is simply how unused skills work.
The third rule is the surprising one and also what keeps the matrix useful for planning: somebody who has not done a piece of work for eighteen months will not do it tomorrow at the same quality, and planning that assumes otherwise collides with reality exactly when it is least convenient.
One observation about who owns the matrix. If it is held by HR and filled in by HR, it will reflect what HR heard. If it is held by the manager and nobody else ever sees it, it will go stale. The version that works: the manager fills it in, HR aggregates it and uses it for the training plan, and once a year both look at the columns with a single person.
Do you show the matrix to the whole team?
The columns and the gaps, yes — they are useful operational information for everybody. Named individual levels, no: it turns the instrument into a league table and people start overrating their own cells.
How often is it updated?
Twice a year, plus at every joiner and leaver. Updated monthly it becomes bureaucracy, and levels do not change that fast.
A skills matrix, with levels and gaps calculated across the team
Columns covered by a single person are flagged automatically, so the continuity risk is visible before somebody takes leave.
Free account, every module for 7 days, no card required.