Values and Behaviours: Making a Values Statement Change Decisions

Most companies have values they can recite and cannot use. They were chosen carefully, they are true of the founders, and they have never once settled an argument. That is not a communication failure. It is a design failure: the values were written as adjectives, and adjectives cannot be applied to a decision.

The work is turning each one into something a manager can point at when a real choice is in front of them.

The test a value has to pass

Take any value on your wall and ask two questions. First: can I describe what someone doing this well actually did, in a specific situation? Second: has this value ever caused us to make the more expensive choice?

A value that has never cost anything has not been tested. It may still be true, but nobody in the company has evidence for it, and evidence is what people act on. "We value quality" is unfalsifiable until the day you slip a deadline for it, and then everybody knows what it means.

A value nobody has ever paid a price for is a preference. People can tell the difference, and they calibrate to the decisions rather than to the poster.

Write behaviours, not adjectives

The translation layer between a value and a decision is a small set of observable behaviours: things you could see someone do, or fail to do, and agree on afterwards.

Write each behaviour twice: what it looks like when it is happening, and what it looks like when it is not. The second half is the one that does the work, because it is what a manager needs in the conversation they have been avoiding.

Wire the behaviours into decisions

This is where culture work usually stops and where it starts mattering. A behaviour that appears nowhere except in an onboarding deck will be gone within a year. A behaviour that appears in the assessment a manager has to complete will not.

There are four places to connect them, in rough order of leverage:

1. Promotion. The clearest signal a company sends. If someone is promoted whose behaviour contradicts a stated value, that value is now understood to be optional. This is the decision people watch most closely and discuss most privately.
2. Performance assessment. Behaviours sit alongside outcomes in the performance framework, with the same evidence standard. If they cannot be evidenced, they should not be in the framework.
3. Hiring. Each behaviour gets a question and a way of scoring the answer. Otherwise "culture fit" becomes a word for whether the interviewer enjoyed the conversation.
4. Recognition. What gets mentioned publicly teaches faster than what gets written in a policy, and it costs nothing.

Name the tensions

Real values conflict. Speed and craft conflict. Directness and kindness conflict. Autonomy and consistency conflict. A values statement that pretends otherwise is not describing a culture, it is describing a wish, and people learn to distrust it the first time they have to choose.

The useful move is to state the tension and say how you resolve it. "We prefer speed, except where a mistake would reach a customer" is a sentence a manager can act on at four in the afternoon. "We value both speed and quality" is not.

What this looks like when it has worked

You know the translation has landed when the values start appearing in ordinary sentences without ceremony: in a hiring debrief, in a promotion discussion, in someone declining a piece of work. Nobody quotes them. They are just the shape of the argument.

You also know it when a value gets removed. A company that has genuinely examined its values usually finds one it does not act on, and deleting it is more honest than keeping it. Five values you enforce beat eight you admire.

This is the substance of culture and values work: not a new statement, but the connection between the statement you already have and the decisions you already make.