Image Credit: <www.forbes.com>
Today I want to talk about “skill based” pay structures versus “job based” pay structures.
First things first:
In “Compensation” 1 Milkovich and Newman define the terms as follows:
So the question here (I suppose) is which of these methodologies is best?
To quote a wise man, I would submit to you that: “It depends.”
First of all, to a certain extent every job is “skill/person based”. While a minority of companies compensate strictly based on the job (basing where an external applicant or existing employee should fall in the pay range based strictly on job content) most companies pay in some part based on what an internal employee and/or external applicant made in their prior job. 2 In this sense employers are paying for the person as opposed to the job, since over time a person’s skills and experiences will (generally speaking) naturally move their pay up as a product of market forces.
Put another way: If a candidate applies to a position with a pay range of $60k-$90k – and she made 100k in her last job – her prior salary will (generally) have an impact on the offer extended by the employer that is disproportionate to the job duties and responsibilities of the role (i.e. she will likely receive an offer near the top of the range even if it isn’t necessary to pay at that level to attract an otherwise adequate talent to do the work). 3
With that said, I generally answer the question of rather to take a “skill based” or “job based” approach to hiring by answering two questions:
1. Is the company’s pay philosophy to “pay for potential?”
2. If the company doesn’t pay for potential, is the candidate being hired being brought in expressly to take over a bigger job?
If the answer to either of the above questions is “yes”, then a “skill based” (or “person based”) approach is probably best. If not, I’d err on the side of taking a “job based” approach.
Saplings can become massive trees one day, but what is the their value before hand? Image credit: <keredria.blogspot.com>
Why, you ask? 4
1. The truth of the matter is, while companies generally pay based on experience, their most valuable/coveted employees (over the long run) are those that may or may not be the most experienced, but can learn new skills quickly.
Put another way, if an employer has to choose between a middle manager who is moderately experienced – but has the pedigree to move into an executive level role one day – or a much more experienced middle manager who has already hit his/her ceiling, the company will (generally) value the high potential middle manager much more (or if they don’t they should). To do so is simply good succession planning.
To this point, some companies are fixated on salary compression – they don’t want new/less experienced hires making more than experienced hires.
I don’t think this is generally a bad approach to compensation, but if a company values “potential” then it can’t let salary compression completely dictate the way it pays its HiPos.
Some companies “pay for potential” while others don’t. Those that don’t tend to experience turnover issues over the long run since HiPos understand their market value (and often go and get it). 5
2. Furthermore, sometimes the job a company hires an employee for isn’t the job the employee is going to end up in “X” months/years later. In these cases, paying an employee based strictly on job content isn’t always practical.
There are some employees that will take this on (low pay in the short term for a long term pay off), but far more often (particularly if it’s an external hire) an employee being groomed for a bigger job expects to see something in his/her compensation to reflect the fact that he or she is being groomed for a larger role.
Anyway, this post has creeped up over 1,000 words so I’m going to wrap it up now. I may revisit this topic at a later date, however, as I have a lot of energy around it.
As always, please share your thoughts below.
If you have questions about something you’ve read here (or simply want to connect) you can reach me at any of the following addresses:
SomethingDifferentHR@gmail.com OR firstname.lastname@example.org