How to build a skills matrix for critical knowledge
A skills matrix for critical knowledge lists your critical tasks against your people and records, per cell, whether someone can do the task independently, with help, or not yet — and whether that was ever tested on a real case. It shows at a glance where only one name can do a task, who the natural back-up is, and which transfers to start first. The value is in the testing column: a matrix built on self-assessment alone looks safer than reality.
Before you start
Prerequisites: a list of your core processes or a process map, the people involved, and a sponsor who treats the matrix as a planning tool, not a performance review. Say that openly to the team before you start.
Use this guide when someone important is approaching retirement, when the same person is always called for the same problem, when holidays have to be planned around one colleague, or before a reorganisation that changes who does what.
The steps
Step 1 — List the critical tasks
From your core processes, pick the tasks where a mistake or a delay hurts customers, safety, quality or cash. Name them concretely: “price a custom installation”, not “sales”.
Pitfall: Listing job titles instead of tasks. A role hides the few tasks inside it that only one person can do.
Step 2 — Define simple levels
Keep three or four: can do it independently; can do it with guidance; knows the basics; cannot do it. Add one column: tested on a real case, yes or no.
Pitfall: Ten-point scales. Fine distinctions nobody applies consistently.
Step 3 — Fill it in with people, not about them
Ask each person together with their lead. Where they disagree, note both views and settle it with a real case.
Pitfall: Filling it in behind people's backs. It destroys the trust you need for the transfers that follow.
Step 4 — Mark the single points of failure
Every critical task with only one independent name is a key-person dependency. Rank them by impact and by how soon that person could be unavailable.
Pitfall: Counting “with guidance” as cover. Guidance from whom? Usually from the same person.
Step 5 — Choose back-ups and test the transfer
For the top dependencies, name a back-up, capture the knowledge the task needs, and let the back-up handle a comparable case on their own. Only a passed test changes the cell.
Pitfall: Upgrading a level after a training session. Attendance is not competence.
Step 6 — Keep it alive
Review the matrix when people join or leave, when tasks change, and on a fixed rhythm. Track which transfers are planned, in progress and tested.
Pitfall: A one-off spreadsheet. It is out of date by the next hire.
An example
Take a machine builder that lists its critical tasks, from commissioning a machine on site to quoting a retrofit of an older installation. The team fills in the matrix together, task by task.
Three engineers say they can quote a retrofit independently. The tested column tells a different story: in the past year only one of them did it alone; the other two always checked with that colleague before sending. The task moves to the top of the list.
A younger engineer is named back-up. The pricing logic and the exceptions — which older control systems cannot be reused, when a site visit is needed — are captured from the senior engineer, with their sources. The back-up quotes the next retrofit alone, and the senior engineer reviews it afterwards. Only then does the cell change to tested.
Where MentX comes in
MentX captures how your company really works: the knowledge of your key people and the processes they run. We offer both a hands-on service approach — mapping your processes and capturing the knowledge behind them, from meetings, workshops and a guided intake — and our own personality-aware knowledge base, with full source attribution, in your own Knowledge Space. We build on the tools you already use and add best-practice solutions where they fit.
The matrix shows where to start. The approach does the rest: capture the knowledge the task needs, then test the transfer as part of operational excellence.
Checklist
- Critical tasks named concretely
- Three or four clear levels plus a tested column
- Filled in with the people, openly
- Single points of failure marked and ranked
- Back-ups named; transfers proven on a real case
- Reviewed when people or tasks change
Questions people ask
Is this the same as an HR competence framework?
No. A competence framework describes what a role should be able to do. This matrix records who can do which critical task today, and whether that was ever proven on real work.
Should everyone see the matrix?
Share it with the people in it and their leads. Openness helps the transfers; ranking people in public does not, and it quietly turns a planning tool into an appraisal.
Where do we start when the matrix shows many gaps?
With the task where a single name meets the highest impact and the shortest horizon — for example, a critical task held by someone who retires next year. Close that transfer fully before you open the next one.
