How to choose which skills to map

Content aligned to the Capability Guide PDF for this topic. Q2 2026 refresh.

Why is choosing columns harder than building the grid?

World Economic Forum research finds that 39% of workers' core skills will change by 2030, and 63% of employers cite skills gaps as the top barrier to transformation (World Economic Forum, 2025). That shift makes your column list a strategic choice, not a catalogue exercise. Ask anyone who has built a skills matrix what was hardest, and they rarely say the spreadsheet — they say deciding what goes in the columns.

Map too few skills and you miss cover risk and training priorities. Map everything and the grid becomes unmaintainable fiction within a year. This guide shows how to choose the vital few — usually ten to twenty capabilities — using a simple priority quadrant: criticality against how widely each skill is held today.

What does "the vital few" actually mean?

The instinct when building a matrix is to capture every tool, task, and trait. Resist it. A matrix of a hundred skills is never kept current and is exhausting to read; a matrix of the ten to twenty skills that genuinely matter gets scored, maintained, and used.

Choosing skills is therefore an exercise in leaving things out as much as putting them in. The goal is the smallest set of columns that still tells you what you need to know: where capability is thin, where work would stall if one person left, and where training spend will change outcomes.

Hard skills, behavioural skills, and compliance skills all belong — if they pass the same tests. The question is never "hard versus soft"; it is whether the skill is critical, at risk, definable, and decision-driving.

Which two questions decide every candidate skill?

For every candidate skill, two questions settle whether it earns a column.

How critical is it? How much does the work, the quality, the strategy, or regulation depend on this skill? Most skills are useful; only some are genuinely critical.

How widely is it held? Is the skill everywhere in the team, or resting on one or two people? You do not need exact data yet — a rough sense from the team is enough for selection. A critical skill held by only one person is a flashing warning light.

Together these axes sort candidates into clear priorities. They are the basis of the priority quadrant at the heart of this method — and they replace endless debate with a defensible rule.

How do wrong columns sink a good matrix?

A skills matrix can be perfectly built and still fail if it maps the wrong things. The choice of skills determines whether the matrix surfaces real risks and decisions or just generates tidy, useless data — and whether anyone will still be updating it a year from now.

Finance and operations leaders often approve matrix projects because the template looks professional. Without a disciplined column choice, the same leaders later cannot explain why re-scoring takes days or why the heat map never changes hiring or training decisions. The grid becomes a compliance artefact rather than a management instrument.

Two failure modes pull in opposite directions, and both come from poor skill choice. Map too many and the matrix becomes unmaintainable — a sprawling grid that ages into fiction because no one can keep it current. Map too few, or the wrong ones, and it misses the gaps that actually matter, generating data that changes no decision.

Choosing the right skills — the critical, at-risk vital few — is what lets a matrix stay both maintainable and meaningful. It is the difference between a tool that earns its place and one quietly abandoned within a year.

What are the seven steps to a defensible shortlist?

This turns a daunting blank column into a clear, defensible shortlist. Work through it in order.

1. Start from the work and the strategy. Before listing skills, be clear on what the team must deliver today and as the business changes. A new market, system, or regulation on the horizon should shape your list.
2. Brainstorm candidate skills widely. List every skill that might matter — technical, behavioural, compliance — without filtering yet. Involve the team; they know what the work really turns on.
3. Judge each skill on criticality. Ask how much the work depends on it. Force the distinction between critical and merely useful.
4. Assess how widely each is held. Roughly how many people already hold each skill? Judge coverage by who actually does the work, not by job title alone.
5. Plot them on the priority quadrant. Criticality up the side, coverage across the bottom. Critical and thin sits top-left; peripheral and universal sits bottom-right.
6. Keep the vital few. Select columns for critical skills (thin and covered), plus important should-haves you have room for — aim for ten to twenty total. Leave peripheral and universal skills off.
7. Review and evolve the list. Revisit columns on the same cadence as re-scoring. Add what has become important; retire what no longer is.

What do the four zones of the quadrant tell you?

Plotting candidates on criticality against coverage produces four zones, each with a clear instruction.

• Top-left — map first. Critical, held by only one or two people. Single points of failure; highest mapping and cross-training priority.
• Top-right — map and maintain. Critical and widely held. Map to confirm strength holds; risk is erosion, not absence.
• Bottom-left — monitor. Not critical but thinly held. Usually leave off a focused matrix; keep a watching brief.
• Bottom-right — leave off. Neither critical nor scarce. Mapping adds maintenance for little insight.

The top half almost always earns a place; the bottom-right almost never does. Judgement calls cluster in the bottom-left — how much watching-brief detail is worth the maintenance cost.

How should you read a plotted quadrant in practice?

Below is an illustrative plot for a customer-operations team. Positions are judgement calls of criticality and current coverage; the quadrant turns that judgement into a shortlist.

Top-left is where to start: Compliance and Data analysis are critical and held by very few — the must-map skills and the most urgent cross-training priorities. Top-right still earns columns to confirm strength. Bottom-right skills are deliberately excluded so the matrix stays focused.

Which four tests settle borderline skills?

When the quadrant leaves a skill on the borderline, four questions settle it.

The last test is as important as the first three. A skill can be critical yet impossible to map well if you cannot describe each level — vague traits erode trust in the whole grid.

What mistakes make skill lists unusable?

Mapping everything. An exhaustive list never gets maintained. Choose the vital few and leave the rest off.

Ignoring the strategy. Skills mapped out of habit miss what is coming. Start from what the team must deliver now and next.

Treating all skills as critical. If everything matters equally, the matrix cannot prioritise.

Judging coverage by title. A senior title does not guarantee a skill. Think about who actually does the work.

Mapping the unmeasurable. If you cannot describe each level, the column will erode trust in the data.

Freezing the list. The skills that matter change with the business. Revisit columns periodically.

What if different roles need different columns?

Edge case: one matrix serving multiple role families. You can either maintain one shared grid with Level 0 marking skills out of scope per person, or split into role-specific matrices with overlapping skills synced for required levels.

When HR owns a role-template view and the line manager owns a named team view, agree which record is authoritative for allocation. Sync required levels between them; do not run duplicate scoring rounds without reason. Level 0 on the Upleashed scale exists precisely so a skill some roles need and others do not can still sit in one matrix — excluded from the wrong rows, not deleted from the model.

Why does good selection make 0–5 scores worth collecting?

Once you have chosen skills, you score them on a defined scale. Map the critical, at-risk ones and a column like Compliance or Data analysis, scored across the team, immediately reveals coverage risk worth acting on. Map a peripheral skill and accurate scores still tell you nothing useful.

Worked example: Compliance (KYC) is critical (regulated) and thinly held (one expert) → top-left, map first → scored across the team → coverage of one — a clear single point of failure to act on. That is why selection precedes scoring in how to build a skills matrix and pairs with writing competency descriptors before the first rating round.

Which site tools support choosing which skills to map?

• Free 5×5 mini-matrix builder
• Upleashed 0–5 methodology
• 0–5 descriptor generator
• Skills audit checklist
• How to build a skills matrix
• How to write competency descriptors

How should you score cells on the 0–5 scale?

Define each level in observable behaviours before anyone rates. Level 3 is the usual required standard: capable, consistent, unsupervised work to the agreed definition of done.

Capability percentages use Upleashed weightings (Level 1 = 25%, Level 2 = 50%, Level 3 = 75%, Levels 4–5 = 100%; Level 0 excluded). See competency scale 0–5 explained for the full framework.

How does this guide connect to the rest of the site?

Keep choose-which-skills-to-map.pdf for offline briefings. Online, you get searchable structure, tables, and pointers into the wider methodology.

If descriptors drift between managers, reset them against the methodology pillar and republish from the descriptor generator.

Publish descriptors beside the grid so new managers inherit the same meaning of each level, not their own interpretation.

Frequently asked questions

How do I choose which skills to put in a skills matrix?

Start from what the team must deliver, now and as the business changes, and brainstorm candidate skills. Judge each on how critical it is and how widely it is held, plotting them on a priority quadrant. Map the vital few — the critical skills — starting with the ones only one or two people hold.

How many skills should a matrix have?

Aim for ten to twenty. That range is focused enough to keep current and broad enough to be useful. Fewer can be fine for a first pilot; many more becomes unmaintainable. The discipline is to map the vital few that matter, not every skill the team possesses.

Should I map soft skills as well as technical ones?

Yes, if they meet the bar. Behavioural skills like coaching, influence, and communication can be critical and worth mapping, provided you can describe what each level looks like. The test is not hard versus soft, but whether the skill is critical, at-risk, and definable enough to score consistently.

What is the priority quadrant?

It is a simple grid that plots candidate skills on two axes: how critical the skill is, and how widely it is held. The four zones give clear instructions — map-first (critical and thin), map-and-maintain (critical and covered), monitor, and leave off — turning a long list into a confident shortlist.

Which skills should I prioritise mapping first?

The critical skills held by only one or two people, the top-left of the quadrant. These are single points of failure: vital to the work yet fragile. Mapping them makes the risk visible, and they are usually your first cross-training priority once the matrix is built.

How often should I review the skills I map?

Revisit your skill list whenever you re-score the matrix, and whenever the strategy shifts — a new market, system, or regulation. Add skills that have become critical and retire those that no longer matter, so the matrix keeps tracking what the business actually depends on.