Skills matrix
The skills matrix shows your whole team's capabilities in one view — rows are people, columns are skills, cells show proficiency.
Proficiency levels
- 0 — None
- 1 — Awareness
- 2 — Beginner
- 3 — Competent
- 4 — Proficient
- 5 — Expert
Use cases
- Resource decisions — "Who can lead this React project?"
- Gap analysis — "We have 1 expert in EVM, we need 3"
- Hiring brief — "Our skills matrix shows we need a senior data engineer"
- Training prioritisation — pick training based on biggest org-wide gaps
Update process
- Initial ratings during onboarding
- Self-assessment at appraisal time
- Manager validation
- Project-end re-rate (gain skills during delivery)
Filtering and views
The matrix supports:
- Filter by department
- Filter by skill level (show only experts, etc.)
- Add new skills inline
- Export to CSV
Tips
- Honest > inflated. A team where everyone rates themselves expert is worse than honest gaps.
- Don't rate every skill. 15-25 skills per role is enough. 100+ is theatre.
- Use it. A skills matrix that doesn't drive resourcing decisions is just documentation.