Your Skills Matrix Says You’re Covered. Can You Actually Staff the Next Project?

Imagine your company asks every manager to keep a skills matrix for their team (spreadsheet where each person scores themselves on the skills the team needs and updates those scores at their annual review). The finance manager's matrix scores her eight analysts from 1 to 4, and most of the scores under forecasting are 3s and 4s, so when the CFO asks for a new pricing model by the end of the quarter, she tells him the team has the skills to build it.

Two weeks later, nobody has started the model. Ana and Ben, the two analysts with the highest forecasting scores, are tied up with the annual budget until the end of the quarter. Chloe and Eli gave themselves a 3 after a single training course and have never built a model on their own, and a fifth analyst, Farah, is on parental leave. That leaves Dev, whose 3 looks exactly like Chloe's and Eli's, so nothing in the matrix reminds the manager that he has already built a demand model on his own.

The matrix recorded what each analyst said they could do, but staffing the pricing model depended on three things it never captured: who could lead the work at the top level, who had time, and whose scores had been checked against real work. This post explains what a skills matrix is, the six reasons a matrix that looks covered can still leave a project with nobody to run it, and how to build one you can actually staff projects from.

What is a skills matrix?

A skills matrix is a table that lists the people on a team down one side and the skills the team needs across the top, with each cell showing how well that person can use that skill. Managers use it to see where the team is strong, where it has gaps, and who could cover for a colleague or teach a skill to someone else.

Most matrices score each skill on a scale of three to five levels, and a common four-level scale looks like this:

1. Aware: knows the basics but hasn't used the skill on real work yet.
2. Developing: can use the skill with help from someone more experienced.
3. Proficient: can use the skill alone in most situations.
4. Expert: can handle the hardest cases and teach the skill to others.

Using that scale, the finance manager's matrix might look like this:

Read quickly, the forecasting column looks healthy because six of the eight analysts score 3 or higher. The rest of this post explains why that column still couldn't tell the finance manager who should build the pricing model.

6 reasons a skills matrix can say you're covered when you're not

Each of the six reasons below is a piece of information the finance manager needed to staff the pricing model, and that her matrix never recorded.

1. The top level sits with one or two people

A matrix makes a skill look covered when several people have a decent score, but most projects need at least one person who can lead the work at the top level. In the finance team, six analysts score 3 or higher in forecasting, yet only Ana and Ben score 4, so if both of them are busy or leave, nobody left on the team can handle the hardest forecasting work.

Software teams call this risk the "truck factor", which is the number of people who would have to leave before a project stalls. A study of 133 popular open-source projects found that 65% had a truck factor of two or fewer (Avelino et al., 2016), but most business teams never measure theirs, so they only discover it when a key person is busy or resigns. To find it in your own matrix, count how many people sit at the top level for each skill rather than how many sit above the middle.

2. Most scores come from people rating themselves

In many teams, people fill in their own scores and their manager only glances at them, which makes the matrix a shaky basis for deciding who should lead a project. A review of studies covering more than 37,000 employees found that people's ratings of their own performance matched their managers' ratings only weakly, and that people tended to rate themselves more generously (Heidemeier and Moser, 2009). The two analysts who gave themselves a 3 after one training course fit that pattern, because nobody had checked their scores against a model they had actually built.

3. It shows what people can do, not whether they have time

A matrix records what each person can do but says nothing about whether they have time to do it. Ana and Ben have the highest forecasting scores, but the annual budget fills their time until the end of the quarter, and because the matrix never put that next to their scores, it didn't come up when the finance manager answered the CFO.

4. The scores are out of date

Each score describes someone's skill on the day it was given, but most matrices don't show that date, so a score from last year looks as current as one from last week. In the finance team, Chloe's forecasting score dates from October 2025 because she didn't update it at this year's review, and nothing in the matrix tells the manager it is a year old. That matters because skills change quickly, and the World Economic Forum estimates that 39% of workers' current skills will change or go out of date between 2025 and 2030 (WEF).

5. The skills are too broad for the work

A single column labeled "forecasting" covers very different kinds of work, from a monthly cash forecast to a pricing model that predicts how sales change at each price point. The pricing project needed the second kind, but the matrix gave both the same column, so a 3 in cash forecasting looked the same as a 3 in pricing. Broad labels also make people's own scores less accurate, because people judge themselves more accurately on specific tasks than on broad ones (Zell and Krizan, 2014).

6. It only covers one team

The best person to build the pricing model might work in the commercial team or the data team, but the finance manager's matrix can't show them because it only lists her own analysts. When every team keeps its own matrix, nobody can see skills across teams, and companies end up hiring from outside for skills they already have. In a 2026 TalentLMS survey of 1,500 US managers and employees, half said their company hires externally for skills that already exist inside it (TalentLMS).

How to build a skills matrix you can staff projects from

You don't need to throw your matrix away, because each of the six gaps above can be closed by adding information to the matrix you already have. The seven steps below show how, using the finance team as the example.

1. Split broad skills into the work they cover

Start with the projects your team expects over the next six months and list the skills each one needs. When one skill covers very different kinds of work, split it in two, so the finance team's "forecasting" becomes "cash forecasting" and "pricing and demand modeling." A useful test is whether a manager could watch someone use the skill and judge how good they are at it.

2. Describe what each level looks like in real work

For each skill, write one sentence that describes what each level looks like on the job, so everyone scores against the same standard. For pricing and demand modeling, "Expert" might mean "has built a pricing model that was used to set real prices and can explain how it works to the finance leadership team."

3. Check each score and note when it was given

Ask people to score themselves first, then have their manager or a project lead confirm or change each score, ideally by pointing to work the person has delivered, such as a model they built. Write the date next to every score, and when the two ratings are more than one level apart, talk it through with the person instead of taking the average.

4. Add a column that shows who has time

For each person, note how much of their time is booked over the next quarter, or the date their main project ends. With that one column, the matrix can answer "Who can start this?" as well as "Who could do this?"

5. Count the experts behind each skill

For each skill, count how many people score at the top level, and treat one expert or none as a risk and two as a warning. Where you find a risk, pair your expert with the strongest person one level below on the next project, so the team builds a second expert before it needs one.

6. Ask what people want to work on

Interest isn't one of the six gaps, but it makes staffing easier because it shows who would welcome a stretch project and who would take it on reluctantly. Add a simple yes or no for each skill to show whether the person wants to use it more.

7. Keep scores current and use the same skill names across teams

Update a person's score when they finish a project, complete a course or earn a certification, and review the whole matrix at least once a quarter. Ask other teams to use the same skill names and level descriptions, so that a score means the same thing in every team and can be compared when a manager borrows someone from another team.

What the finance manager's matrix shows after these changes

After these changes, the finance manager's view of the pricing project looks very different:

Splitting forecasting into two skills shows that Ben's 4 came from cash forecasting, and his manager scores him a 2 on pricing because he has never built a pricing model. Nobody at expert level is free this quarter, but Dev has a score his manager confirmed after he built a demand model, half his time free, and an interest in the work. Chloe and Eli are free as well, but they scored themselves a year ago, so the manager would want to check their skills before relying on them.

With that information, the finance manager can make a real decision. She could ask Ana to spend a few hours a week coaching Dev through the model, look for a free expert in another team, or agree a later deadline with the CFO, and her original matrix couldn't have supported any of those choices. If you want to build your own version, you can copy this layout into a spreadsheet.

When a spreadsheet stops being enough

A spreadsheet matrix works well for a single team of up to a few dozen people with one manager keeping it current. It starts to break down once the questions you need answered cross team lines, and these signs suggest it's time to move to a skills platform:

• Managers need to find people with a skill in other teams, not just their own.
• Teams use different skill names or scales, so their scores can't be compared.
• You need a record of who gave each score, when, and based on what work.
• Availability lives in a separate project tool, so the matrix and the calendar never meet.
• You want each gap to lead straight to a gig, a mentor or a course.

By that point, keeping several spreadsheets in sync takes more of your managers' time than the spreadsheets save, and the scores start drifting out of date again.

How Fuel50 helps you staff projects from your skills data

Fuel50 records the information a spreadsheet matrix leaves out, such as shared skill definitions, checked scores and availability, and connects it to the decision of who should do the work.

• Shared skill definitions. Skills Architecture draws on a library of more than 5,000 skills, each defined by Fuel50's in-house team of people scientists with set levels and development actions, so every team scores against the same names and descriptions.
• One current record of skills. The Skills Inventory brings skills data from across your company into one place, where you can search and filter it by business unit or job family, and every change to a skill is logged and approved.
• Availability built into staffing. When a manager posts a project in Gigs, they set the skills, time and location it needs, and Fuel50 matches it to people based on their skills and availability, so people across your company can see work that fits them.
• Early warning on thin skills. Insights tracks skill supply and gaps across teams and predicts which skills are at high risk because the people who hold them may resign or retire, which takes step 5 further by showing the risk before anyone leaves.

In the finance team's case, the manager would post the pricing model as a gig asking for an expert in pricing and demand modeling, half time, until the end of the quarter. Dev would appear as a close match, along with anyone in the commercial or data teams who has the skill and the time.

That view across teams often turns up people nobody knew about. As Kian Colestock, Chief Information Officer at UC Irvine, put it, "We have many silent skills within our org chart that we're not using because that's not what that person was hired for" (UC Irvine story).

See how Fuel50 helps you staff projects with the skills you already have.

Frequently asked questions

What is a skills matrix?

A skills matrix is a table that lists a team's members against the skills the team needs, with each cell showing how well that person can use that skill. Managers use it to spot strengths and gaps and to see who can cover or teach a skill.

What should a skills matrix include?

At minimum, it should list the skills your team's work needs, a score for each person on each skill, and a clear scale. If you want to use it to staff projects, also record who gave each score and when, how much time each person has free, and whether they want to use the skill more.

What rating scale should a skills matrix use?

Three to five levels work best, as long as each level is described in terms of real work. A common four-level scale runs from Aware and Developing to Proficient and Expert.

How often should you update a skills matrix?

Update a person's score whenever they finish a project, complete training or earn a certification, and review the whole matrix at least once a quarter.

What's the difference between a skills matrix and a competency matrix?

A skills matrix scores people on specific skills, such as SQL or financial modeling, while a competency matrix scores them on broader qualities that combine skills, knowledge and behavior, such as leadership or customer focus.