Competency-Based Pay

Traditional pay structures value the job. A grade is assigned to a position, a range attaches to the grade, and the person occupying it is paid within that range. Move to a bigger job and your pay can rise; stay in the same job and it largely cannot, beyond increments.

Competency-based pay values the person's demonstrated capability. Acquiring and demonstrating a defined competency raises pay whether or not the job title changes.

The problem it solves is real. In organisations where the only route to higher pay is a bigger job, excellent specialists become mediocre managers, and the ones who refuse that path leave. Paying for depth is the alternative.

• A competency framework that is specific enough to assess. Vague behavioural statements produce arguments; observable capability at defined levels produces decisions.
• Assessment that is evidence-based and consistent between assessors. If two managers would reach different conclusions about the same person, the framework is not ready to drive pay.
• A defined relationship between competency level and pay. Employees need to know what acquiring a competency is worth before they invest in acquiring it.
• Genuine access to development. Paying for competencies that people have no route to acquire produces resentment rather than capability.
• A cost model. Capability accumulates in one direction, so the paybill drifts upward unless the framework caps levels or ties them to organisational need.
• A position on what happens when a competency is no longer needed, or has decayed. Most frameworks are silent, which is why costs only go up.

The second of these is where implementations actually fail. Organisations build a framework, skip the assessor calibration, and end up with a scheme in which pay depends on how generous a manager is, now with documentation.

It works best where capability is technical, observable and directly related to value: engineering and technical specialisms, clinical roles, skilled trades, and professional services where depth is what clients buy.

It works poorly where output is collective, where the valuable capabilities are relational and contested, or where roles are highly standardised and capability beyond the standard adds little. In those settings a job-based structure with good progression is simpler and no less fair.

Hybrid arrangements are the common resolution and are usually the right answer. A job-based grade sets the range, and demonstrated competency governs progression within it. That keeps cost control while giving specialists a route that does not require managing people.

One caution. Because competency-based pay produces different pay for people in the same nominal role, it makes internal comparison sharper. The equal remuneration provisions turn on the same work or work of a similar nature, so the assessment record has to be capable of explaining why two people doing the same job are paid differently. Where it cannot, the scheme has created an exposure that a job-based structure would not have.

• Cap the levels that carry pay, and require organisational need rather than personal interest to justify acquiring a paid competency.
• Calibrate assessors before each cycle, on real cases, and check outcomes for consistency afterwards.
• Separate the assessment conversation from the annual appraisal. Mixing capability assessment with performance rating collapses both.
• Publish the framework and the pay consequences. A scheme employees cannot see is a discretionary scheme.
• Model the paybill effect over three years, not one. The cost of the scheme is not the first year's increases.
• Keep the evidence. The assessment record is what explains a pay difference between two people in the same role, and that explanation is needed more often than organisations expect.