An open fabric case holds a tool with a blue collar and two additional tips in pockets.

What are we paying for when we pay for skills

Acquiring a skill, keeping it available, using it and producing a result are different commitments. Pay needs to specify which one it recognizes and what it expects in return.

Alejandro Mayorga6 min read

Paying for a capability that is not being used can be a sensible decision. A company may want people who can cover different functions, respond to a contingency or take on work it does not yet need to perform. That possibility has a value distinct from the volume produced during the month. The problem arises when an agreement to pay for broader capabilities is later judged as though it had promised an immediate increase in production.

That distinction is part of the tradition of skill-based pay. In the description used by Jason Shaw and his colleagues (opens in a new tab), the increase recognizes having learned and demonstrated proficiency in a new skill, even if it is not yet used in everyday tasks. This does not mean paying for any knowledge a person chooses to acquire. The organization selects which capabilities it wants to recognize and needs to explain what it hopes to achieve with them. That is where a decision begins that the expression “paying for skills” leaves much too open.

The commitment contained in pay

Recognizing the acquisition of a capability may be intended to prepare people for work the company expects to need. The relevant milestone is achieving a defined proficiency, not attending a training activity. Learning to operate a second production line, for example, can broaden the work someone is prepared to take on without yet changing their assignment. Valuing that learning requires checking the capability acquired. How often the company later chooses to use it answers a different question.

Paying for the exercise of a capability places the discussion in the work actually taken on. Knowing how to operate the second line is no longer enough: what matters is whether the person is expected to take charge of it, with what authority and under which additional demands. The same person may retain their repertoire while receiving different assignments. If those assignments change the responsibility they bear, reducing the conversation to how many skills they have leaves out part of what is being asked of them.

It is also possible to link a component of pay to a contribution or result. In that case, what will be recognized and how it relates to the person’s work need to be established. Acquiring a skill does not guarantee that result, which may depend on materials, equipment and other people’s decisions. A design can combine these purposes, but must retain their differences: recognizing learning and rewarding results are not two names for the same expectation.

The distinction even changes what we would consider a failure. If the decision was to pay for a repertoire that makes it possible to cover several functions, a month without assignment changes does not prove the pay is pointless. If the expectation was to use that repertoire systematically and assignments never change, a question about work design arises. If the aim was a specific result, that will need to be examined. The same observation—a skill that was not used—takes on different meanings according to the commitment it was intended to sustain.

Flexibility also needs an organization that can use it

There is favorable evidence for these plans that deserves to be taken seriously. The comparison by Atul Mitra, Nina Gupta and Jason Shaw, published in 2011 (opens in a new tab), found positive associations between skill-based pay, workforce flexibility and work attitudes. It combined two sets of surveys from 1991 and 1994 to compare 214 sites, with results reported by organizational managers. This is a basis for examining their potential, not a causal estimate of what any policy called skill-based pay would produce today. The favorable relationship does not tell us how much should be paid for a particular capability either.

For a company, gaining more assignment alternatives can be an important improvement. Its value becomes concrete when it allows work to be reorganized without always depending on the same people, or opens a development path that previously required waiting for a vacancy. But broadening someone’s repertoire and allowing them to contribute through it are different decisions. As when an organization has the skills but its operating model prevents their use, a pay incentive may address one part of the problem without resolving the conditions of the other.

An empty room with mats and practice equipment on shelves, an examination table and a table with chairs.

The opportunity to acquire the recognized capabilities is also part of the design. If pay progression depends on a certification accessible only to those who receive a certain assignment, the distribution of those assignments affects who can progress. It matters how people obtain the opportunity to learn and demonstrate proficiency, what support it requires and what alternatives exist for those who do not receive it. Otherwise, a policy presented as recognizing capabilities may end up rewarding a difference in access that it leaves unexamined.

These questions are not resolved by turning an assessment level into a pay rate. Evidence about a capability helps clarify what is being recognized; the amount and form of pay also require decisions about compensation, equity and working conditions. Nor does the company’s loss of interest in a skill automatically determine what can change in someone’s salary. Reviewing that situation requires considering the applicable agreements and rules, not treating a catalog update as though it changed the pay commitment on its own.

The starting point is being able to explain what justifies the pay and what each party expects: what is recognized when the capability is acquired, what must remain available and what depends on the company assigning the work. Salary is already a real commitment, even when it pays for a possibility. The explanation of what is expected in return cannot remain hypothetical.