The Death of Pay Market Rate Thinking
The Death of Pay-Market-Rate Thinking
Why benchmarking alone is intellectually lazy and strategically dangerous
Pay-market-rate thinking persists because it lets leaders avoid judgement. It wraps indecision in the language of objectivity, replaces design with mimicry, and offers the comforting sense that an organisation is being fair simply because it is being consistent with everyone else.
Here’s the problem underneath that comfort.
Culture is the foundation an organisation rests on, and its remuneration architecture is one of the load-bearing systems through which that culture becomes real: the place, more than any other, where an organisation reveals what it actually values.
Outsource that architecture to external averages, and you don’t get fairness.
You get drift: a system that quietly rewards tenure, noise, and negotiating skill rather than capability, contribution, and the complexity of the work.
Benchmarking was never a strategy. It was a way to avoid having one.
The seduction of the benchmark
Benchmarks feel safe. They come with numbers, charts, and quartiles – the aesthetics of rigour without much of its substance. They let leaders say “the market made us do it,” as though the market were a neutral arbiter rather than a statistical composite of other organisations’ compromises.
The deeper issue is structural. Benchmarking quietly assumes that pay is a commodity, that roles are interchangeable, that capability is uniform, and that performance is linear. None of those hold. Organisations don’t compete in the abstract; they compete through the specific capabilities of specific people, and those capabilities vary enormously. An average can’t capture what it was built to flatten. When you pay the market rate, you’re not paying for what your organisation needs. You’re paying for what everyone else settled for.
The politics beneath the numbers
Market-rate thinking claims to remove politics from pay. In practice, it institutionalises it. When pay is anchored to external data rather than internal logic, the gaps, and there are always gaps, because no benchmark maps cleanly onto a real role, are filled by negotiating skill, manager preference, legacy decisions, and emotional narratives about loyalty and tenure.
The result feels objective and behaves arbitrarily. Two people doing work of genuinely different complexity end up being paid the same because the benchmark flattened the difference. Two people doing work of equal complexity end up paid differently because one happened to join in a different year or negotiated harder on the way in. That isn’t fairness. It’s drift wearing the costume of discipline, which is exactly the thing the next wave of pay-transparency scrutiny is built to expose.
The strategic cost of mimicry
This is the part that should concern anyone building a capability strategy. If you anchor your pay logic to the market, you anchor your talent strategy to the middle because that’s what the median is.
High performance depends on differentiation: in expectations, in standards, in capability, and therefore in how those things are rewarded. Benchmarking, used as the deciding logic rather than a reference point, collapses that differentiation into the same narrow bands and generic structures that everyone else uses.
The trap isn’t paying at market levels; an organisation can pay competitively and still win on capability. The trap is letting the market’s averages decide your internal architecture, because you cannot build a differentiated organisation on undifferentiated logic.
The strategic alternative
The coherent basis for remuneration begins with competence, the capability to handle complexity, consequence, and ambiguity, because that is precisely the variable that benchmarking can’t see and the one that most reliably tracks value creation. Competence is observable, measurable, and developable, which makes it something you can actually design a structure around.
But competence is the spine, not the whole skeleton. A sound remuneration architecture rewards capability alongside contribution and consequence, what the role requires someone to be able to handle, what they actually deliver, and what they’re genuinely accountable for. A system built this way doesn’t ask “what does the market pay for this role?” It asks “what level of capability does this work require, in this organisation, at this stage of its evolution, and how do we reward the people who deliver it?”
That is architecture.
It creates internal coherence and external credibility at once.
It takes the emotional volatility out of pay conversations, because the logic is visible and shared.
It aligns reward with contribution rather than with tenure or negotiating nerve.
And it hands leaders a structural language of fairness rather than a statistical one, which matters enormously when they have to explain a pay decision out loud.
Where external data actually belongs
External data still has a job, just not the one orthodoxy gives it.
Market data is a calibration tool, not a decision driver. It tells you whether your architecture has drifted badly out of step with the external environment; it does not tell you what that architecture should be. It helps you spot blind spots and stay competitive. It cannot define fairness, and it cannot stand in for judgement.
When competence and contribution determine pay and the market merely calibrates it, you get a system that’s internally coherent and externally credible at the same time. That’s design rather than drift.
The end of market-rate thinking
Market-rate thinking belongs to an era when organisations believed culture was a feeling and pay was an administrative process.
That era is closing, and the regulatory environment is closing it faster, because a system anchored to external averages can produce gaps it cannot explain, and explanation is now the requirement.
What organisations need is a remuneration architecture that’s designed rather than inherited: one that rewards capability and contribution rather than tenure, and that gives everyone – the employee, the manager, the regulator – a logic they can actually follow.
The organisations that build it first will have structures that are stable, defensible, and strategically aligned. Those that keep benchmarking in its place will continue to confuse the average with an architecture, and will go on wondering why their performance never quite improves.