The skills matrix, explained

What a skills matrix is

People down one side, skills across the top, a rating in each cell. That is the whole format, and it has been used from factory floors to engineering teams for decades because it answers the questions a lead asks every week: who can take this on, who could teach it, and what will we be missing when this person is on leave?

Read across a row and you see one person's profile. Read down a column and you see the team's depth in one skill: a column with a single Proficient is a risk; a column with an Expert and a few Beginners is a mentoring opportunity.

Why most skills matrices die

Almost every team has tried one. Almost every one is a spreadsheet nobody has opened in a year. The pattern is the same each time:

• Someone filled it in alone. A manager rates twelve people from memory, and the result is a list of impressions the team never agreed to.
• The scale meant nothing. Beginner / Intermediate / Advanced, or 1–10, with no definition of what a 7 looks like — so no two people rate the same way and nobody trusts the numbers.
• The skill list came from outside. A company-wide taxonomy with two hundred entries, of which the team uses fifteen and calls half of them something else.
• Nothing brought people back. It was made for a reorg or an audit, the occasion passed, and with it the reason to keep it true.

How to build one that lasts

1. Let the team name the skills. Ask each person what they have, what they are best at and what they want to learn, in their own words. A team's vocabulary is small and consistent; near-duplicates can be merged as they appear. You do not need a taxonomy first.
2. Use a scale with observable levels. Five levels, each describing something you could watch a person do (below). “Handles the unusual cases; others rely on them” gets the same rating from two people; “advanced” does not.
3. Fill it in together, once. Self-ratings are systematically off — newcomers rate high, experts rate low. Doing it in one session, where teammates can say “you also have…”, corrects that on the spot. The Market of Skills is a 60–90 minute format for exactly this.
4. Leave the learning goals in. A skill someone wants to learn belongs in the matrix as an unrated cell. Matched against a colleague's Expert, it is the cheapest development plan you will ever write — and Kunska writes the rest.
5. Use it every week, redo it every quarter. Staffing, one-to-ones, hiring: each is a reason to open it. A short session each quarter keeps it true.

The rating scale

Names from the Dreyfus model of skill acquisition, definitions from the ILUO matrix used for cross-training in lean manufacturing. Rate what someone can be seen doing today.

0 None

Hasn't done it yet.

1 Beginner

Does it with guidance or a checklist.

2 Competent

Does it alone on routine work.

3 Proficient

Handles the unusual cases; others rely on them.

4 Expert

Sets the standard and teaches it to others.

Why these five levels, where they come from and how to rate well.

Free skills matrix template

A workbook for Excel, Google Sheets or Numbers: skills down the side, people across the top, every rating colour-coded by level, the scale as a legend and a few example rows to replace. It is the format above and nothing more — which is the point.

Running a software, support or production team? There are templates by role with the skills those teams usually start from.

When the spreadsheet stops being enough — because you want the team to fill it in together, see it change in real time, spot the single points of failure and turn it into a development plan — Kunska does all of that for free.

Frequently asked questions

What is a skills matrix?

A skills matrix (or competency matrix) is a grid with the people on a team down one side and the skills the team needs across the other. Each cell holds a rating of how well that person does that skill. Read across a row and you see one person; read down a column and you see who on the team can do a thing, who could teach it and where the gaps are.

What is the difference between a skills matrix and a competency matrix?

For one team, nothing that matters: both name a grid of people against abilities with a level in each cell. The difference shows at the scale of an organisation. A competency matrix usually belongs to an HR framework and sets out the level each role should reach, behaviours included; a skills matrix records what the people on a team can do today. Kunska uses both words for the team kind.

What rating scale should a skills matrix use?

Five levels with observable definitions: 0 None, 1 Beginner (does it with guidance), 2 Competent (does it alone on routine work), 3 Proficient (handles the unusual cases; others rely on them), 4 Expert (sets the standard and teaches it). Three levels leave too wide a middle; ten invite arguments about the difference between a 6 and a 7. Each level should describe something you could watch a person do.

Who should fill in a skills matrix?

The people whose skills it maps, with their teammates watching. A matrix filled in by a manager alone is a list of impressions; one filled in by each person and corrected by colleagues who have seen them work is evidence. A Market of Skills session is a way to do that in one meeting.

How often should a skills matrix be updated?

Once a quarter is enough for most teams: long enough for skills to have changed, short enough that the map is still trusted. A matrix nobody has touched in months is treated as stale, and rightly so. Kunska flags one that has gone untouched.

Is there a free skills matrix template?

Yes: the template on this page is an Excel workbook that also opens in Google Sheets and Numbers, with every rating colour-coded on the five-level scale and the scale itself on a second sheet. When the spreadsheet stops being enough — because the team wants to fill it in together, keep it current and see the gaps — Kunska does the same thing for free.