Employee Value Proposition

An employee value proposition states the deal. In return for effort, hours, commitment and constraint, here is what an employee receives: pay of a certain shape, work of a certain kind, development of a certain sort, conditions of a certain quality.

Stating it has an obvious external use in hiring. The less obvious and more valuable use is internal. Once the position is written down, decisions can be tested against it. A proposal to cut a benefit, tighten flexibility or hold pay can be assessed as what it is, a change to the exchange, rather than as an isolated cost decision.

Organisations without one make those decisions individually and discover afterwards that they have altered the deal without deciding to. The EVP's function is to make the drift visible while it is still a choice.

It also gives managers something to say. A manager asked why someone should stay, or join, is otherwise improvising, and improvisation produces promises the organisation has not made.

Most published EVPs describe only what the employer provides. That is a benefits summary wearing a different name.

A proposition states what is asked as well. Some roles require travel, unsocial hours, being on call, working to short deadlines, or operating with less structure than people are used to. Naming these is not a weakness in the statement. It is what makes the rest of it credible, and it filters out people who would discover the requirement later and resent it.

The test is whether a candidate could read the EVP and reasonably decide the organisation is not for them. If nobody could reach that conclusion, the statement is not describing an exchange, and it will not predict who succeeds.

This is also the difference between an EVP and a recruitment message. The recruitment message can emphasise; the EVP has to be accurate, because employees are the ones who check it daily.

Five areas cover most of what employees actually weigh.

The right-hand column is where most EVPs live. The fix is specificity: not competitive pay but where the organisation targets against market and how often it reviews; not opportunities to grow but what training is funded and how internal moves actually happen.

Specific statements are harder to write because they can be checked. That is exactly why they are worth something.

An EVP written by a small group and announced tends to fail on first contact with employees, because they know whether it is true.

• Start with why people actually joined and why they actually stay, from recent hires and long tenures rather than from assumption.
• Ask leavers too. Exit conversations reveal which parts of the proposition were not being delivered.
• Look for what is genuinely distinctive, including things the organisation takes for granted and has stopped noticing.
• Draft it, then test it with employees who will say if it is not recognisable. A statement they do not recognise is worse than none.
• Check it segment by segment, since the proposition for a field role and a head office role are rarely the same, and a single statement covering both often describes neither.

Segmentation is the step most often skipped. Where the workforce spans very different working conditions, one proposition either flattens into generality or quietly describes only the head office experience, which the field workforce notices immediately.

Where the honest answer is that the current proposition is weak, that is a finding rather than a failure. It is more useful than a statement nobody believes.

An EVP decays, because organisations change and the statement does not.

The maintenance question is not whether the words still sound good but whether they are still true. A promise about development written when there was a training budget, and left in place after the budget was cut, is now a specific and checkable falsehood that every employee can identify.

Reviewing it against measurable things helps: whether pay positioning is where the statement claims, whether internal moves happen at the rate implied, whether the flexibility described is the flexibility granted. Where the practice has moved, either the practice or the statement has to change, and deciding which is the point of the exercise.

The failure to avoid is retaining a statement the organisation has stopped honouring. That is worse than never having written one, because it converts a general disappointment into a specific broken promise, and employees are considerably better at remembering specific broken promises.