Skills matrix

Building one that gets used

Rows are people, columns are the skills that matter for the team's actual work, cells hold a proficiency rating on a small, defined scale (0-3 or 1-4, with each level described). Add certification dates where compliance applies. The discipline is in the columns: list the skills the work requires, not every skill anyone possesses, and define levels concretely enough that self-ratings and manager ratings can be reconciled honestly.

What it reveals

Three findings appear in almost every first-pass matrix. Single points of failure: critical skills held by exactly one person, invisible until that person resigns. Hidden depth: capability people were never asked about. And the training mismatch: development budgets flowing to popular courses while the actual gaps sit unfunded. The matrix converts capability from anecdote into a picture a manager can plan against, including succession and cross-training priorities.

From snapshot to system

A spreadsheet matrix decays from the day it is saved. The step-change is making it live: tied to a competency framework so levels mean the same thing everywhere, updated through assessment and training completion rather than annual guessing, and reportable across teams so workforce planning sees the organisation's capability, not just each silo's. That is the difference between a wall chart and an operating capability record.