One table that shows you who to call when someone's out, and where you have no backup at all. A skills matrix lists your team down one side and the skills their work actually requires across the other, then rates every person against every skill on a simple scale.
Most teams only find out about a skills gap when the one person who could do something goes on leave, or leaves the company. A matrix turns that into something you can see coming, and plan for, months in advance instead of finding out the hard way.
- List the skills that actually matter. Pull from real work, not a generic competency list. If nobody's used a skill in six months, question whether it belongs on the matrix.
- Define a simple scale with plain definitions. A 0 to 4 scale works well. Write one plain sentence for what each level looks like in practice, not just a label.
- Self-rate first, then calibrate with the manager. People are often harder on themselves than a manager would be, or the reverse. The conversation matters more than the number.
- Look for single points of failure. A column with only one person at level 3 or higher is a risk, not a strength, flag it before it becomes an emergency.
- Turn it into development plans and a hiring brief. Every gap you find becomes either something to train internally or something to hire for next.
A working example for a client implementation team. Replace the names, skills, and ratings to match your own team.
The download computes the backup count per skill automatically as you edit ratings.
| Team member | Client Implementation |
Integration Config |
Data Migration |
Project Management |
Client Communication |
Reporting & Analytics |
|---|---|---|---|---|---|---|
| M. Alvarez | 4 | 3 | 2 | 3 | 4 | 1 |
| J. Chen | 2 | 4 | 4 | 1 | 1 | 2 |
| S. Boone | 3 | 1 | 0 | 4 | 3 | 1 |
| D. Farah | 1 | 0 | 1 | 2 | 2 | 4 |
| K. Whitfield | 3 | 2 | 1 | 1 | 3 | 3 |
| R. Patel | 1 | 1 | 0 | 0 | 2 | 1 |
| Backups (level 3+) | 3 | 2 | 1 | 2 | 3 | 2 |
Data Migration has only one person at level 3 or higher, a single point of failure worth addressing.
- Keep the scale to five levels or fewer, more than that and ratings stop being consistent between people.
- Revisit it twice a year, or after a big project wraps.
- Use it out loud in one on ones, not just filed away after a single pass.
- Don't tie it directly to compensation, that makes every rating defensive instead of honest.
- Don't list every possible skill, a matrix with forty columns gets filled out once and never again.
- Don't let a gap sit for a year once you've found it, that's the whole point of finding it.
The download includes a second tab, "Why & How to Use," with the same guidance above plus the use cases, so you don't have to come back to this page while you're building it out.