Rewards3 min read29 October 2026

Writing a Reward Philosophy Before You Look at the Data

A reward philosophy sets out what you pay for and where you position against the market. How to write one, and why it should guide your benchmark data.

A pattern we see often in recent work: an organisation commissions a benchmark, receives the data, and starts moving every role towards the median. Nobody decided that the median was the right answer. It simply became the default because there was no agreed view of what the organisation wanted its pay to achieve.

A reward philosophy is that agreed view. It is a short statement of what the organisation pays for, how it positions against the market and how it balances different elements of reward. It should come before the data, not after.

Market data informs reward decisions; the philosophy sets the frame

What a reward philosophy covers

A good philosophy answers six questions in plain language.

Question	Example answer
What do we want reward to achieve?	Attract and keep people who can deliver our growth plan, and reward strong contribution
Who is our market?	Regional employers in our sector and comparable-sized businesses in other sectors for support roles
Where do we position?	At the median for most roles; above it for a small number of scarce skills
How do we balance fixed and variable pay?	Competitive fixed pay at all levels; variable pay grows with seniority and is linked to clear measures
What role do benefits and non-pay elements play?	Market-standard benefits; we compete mainly on development and career growth
How open are we about pay?	Employees know their grade, range and how decisions are made

Why it matters

It gives the data a purpose. Benchmark results tell you where the market sits. Only the philosophy tells you where you want to be.

It keeps decisions consistent. When managers push for exceptions, the philosophy is the reference point for saying yes or no.

It makes pay explainable. Employees may not like every outcome, but they can understand the logic behind it.

It survives changes in people. A written philosophy outlasts the leaders who wrote it, so reward does not shift every time the HR or finance head changes.

Writing it

Start with the business strategy. What does the organisation need from its people over the next few years?
Agree the market. Which organisations do you compete with for people, by job family?
Decide the positioning. Where you will sit, and where you are prepared to pay more.
Set the mix. The balance of fixed pay, variable pay and benefits by level.
Test it. Check that the philosophy is affordable and that current practice can move towards it.
Keep it short. One or two pages is enough. If it needs more, it is probably trying to be a policy manual.

Reviewing it

A philosophy is not permanent. Review it when the strategy changes, after a significant acquisition or every few years as a matter of course. But change it deliberately, not because a single year's benchmark data looks different.

How Humatix can help

Humatix helps leadership teams in the UAE and GCC agree a reward philosophy, then uses benchmark data to translate it into salary structures, incentive plans and benefits that fit the organisation's strategy.

← Back to all articles