← Insights

People

Find your single points of failure before a resignation does

July 2026 · 6 min read

Somewhere in your operation there is a person who is the only one who can set up a particular machine, calibrate a particular gauge or run a particular test. Everyone vaguely knows it. Nothing is written down. And the day that person hands in their notice, a month of chaos gets scheduled that no risk register saw coming.

A skills matrix is the one-page tool that finds those people while there is still time to do something about it. Done properly, it answers the three questions that matter - who can do what, where are the gaps, and where is the operation one person deep - and it does so with numbers rather than folklore.

The two ingredients most matrices miss

A grid of names against skills is easy. Two design choices separate a working matrix from wall art:

A defined competency scale. Ticks and crosses cannot distinguish "did it once on a course" from "could teach it". A 0-4 scale can: 0 no exposure, 1 trained but needs supervision, 2 works independently, 3 fully competent to the standard, 4 can train and assess others. The words matter more than the numbers - they are what stops two supervisors scoring the same person differently, and they give the matrix its audit credibility.

A required level per skill - not per person. This is the step most teams skip, and it is where the matrix becomes analytical. A skill is not "needed" in the abstract; the line needs, say, two people at level 3 for final inspection and one at level 2 for goods-in. Set the required level per skill, and every cell below it becomes a gap - visible, countable and prioritised. Without required levels, the matrix shows what people can do; with them, it shows what the operation is missing.

Reading it: three views, three audiences

• Down a column (one skill): how much cover does this capability have? This is the operations manager's view, and the one that finds single points of failure.
• Across a row (one person): where can this person grow? This is the development conversation, with the training plan already drawn in red cells.
• The whole grid: how resilient is the team? This is the auditor's view - ISO 9001 clause 7.2 asks you to determine necessary competence, ensure it, and keep evidence. A live matrix with required levels and assessment dates is precisely that evidence.

The SPOF hunt

The most valuable output is the column-count nobody computes by hand: for each skill, how many people are at or above the required level?

Zero people: the operation cannot actually do something it believes it can. One person: a single point of failure - one resignation, one long illness, one holiday clash away from a line stop.

Every skill in those two states deserves a named backup in training now, while the expert is still there to do the training. Cross-training against the SPOF list is the cheapest resilience an operation can buy - and the matrix, refreshed quarterly, shows the count of one-deep skills falling as proof it is working. That count belongs beside your risk register's people risks; "loss of key personnel" stops being an unquantified worry when the matrix can tell you exactly which skills it would strand.

Do not forget the expiring tickets

Some competencies are not assessments but certificates with clocks on them: forklift licences, first aid, welding qualifications, internal auditor training. These need a different mechanism - completion date plus validity period gives an expiry date, and the matrix should warn while there is still time to rebook (60 days works well). The alternative is the audit-morning discovery that your only qualified crane operator has been unqualified since March - which is both a finding and a line stop in one.

Keep both mechanisms in one file: the competency grid for skills, the expiry tracker for certificates, and one dashboard that surfaces gaps, expiring tickets and one-deep skills together. That single page is the training plan, the succession risk report and the clause 7.2 evidence, all at once.