Map the skills that run the business
Not every skill, the fifteen or twenty that operations and the year’s plan actually depend on: the systems only some people can run, the client-facing crafts, the processes with quality stakes, the capabilities the strategy assumes will exist by summer. Derive the list from work, incidents, bottlenecks and the plan, not from job descriptions, which describe intentions.
Score simply, none, basic, works independently, can teach, because finer scales invite arguments the grid does not need, and can-teach is the level that matters for resilience.
Score honestly, read the risks
Self-assessment plus manager calibration in one short conversation per person keeps the grid honest and non-political; the discussion of disagreements is itself useful development data. Then read the two risks the matrix exists to expose: columns with one name at works-independently or above, key person risk with a vacation problem attached, and columns the plan needs that are thin everywhere, the gap between strategy and staffing.
Date the grid and keep versions, because the comparison across quarters, gaps closing, depth building, is the learning program’s progress made visible.
Gaps become assignments, not reports
The matrix pays only when it drives the calendar: each red column gets a decision, train someone toward it, cross-train a backup, hire it, or accept the risk explicitly, with a name and a date. Cross-training the second person on every single-point skill is usually the highest-return learning investment available, and the can-teach scorers are your faculty for it.
One review a quarter, thirty minutes, matrix against plan: it is the meeting where learning stops being a benefit and becomes capacity planning.
The matrix lives where the training is assigned
On the Learning Desk, learners, levels and paths sit in Teams and Seats, so the matrix conversation ends in assignments with due dates rather than a spreadsheet with intentions, and progress tracking shows the gap actually closing by the next quarterly look.
Velora reads your team and plan description and proposes the skills worth mapping and the cross-training priorities. Capacity planning through learning, from the Plus membership.
Frequently asked questions
What skills belong in a skills matrix?
The fifteen or twenty the business actually runs on: systems, crafts, quality-critical processes, and what the year’s plan assumes, derived from work and incidents rather than job descriptions.
How do you score a skills matrix fairly?
Four levels ending at can-teach, self-assessed then calibrated with the manager in one conversation. The disagreements are development data, not disputes to avoid.
What do you do with skills gaps once found?
Decide per gap: train, cross-train a backup, hire, or accept explicitly with a name and date. Cross-training second people on single-point skills usually pays first.