Why Values Statements Fail

"Be respectful."

Two words. Printed on a lanyard. Pinned to a noticeboard. Dropped into an appraisal form. And somewhere in the building, a meeting is being steered by the two people who always speak first - while half the room has stopped trying to contribute.

The value is on the wall. The behaviour isn't in the room.

This gap - between what an organisation says it values and what people experience day to day - isn't new. But it's worth asking why it persists, because the answer isn't that organisations don't care about their values. Most care deeply. The problem is in how values get designed: as labels rather than tools.

The label problem

Walk into almost any organisation and you'll find a set of values displayed somewhere prominent. Usually between four and seven words. Usually some combination of integrity, respect, innovation, teamwork, accountability. Sometimes with a verb added for energy. "Be bold." "Act with integrity." "Deliver excellence."

When researchers at MIT Sloan reviewed the stated values of 689 large organisations, they found the same words appearing again and again. Integrity was the most common, appearing in the values of more than half the organisations studied. Respect and innovation were close behind. The researchers identified 62 distinct values across the whole sample - but most organisations were drawing from the same narrow pool.

This isn't because organisations are lazy. These are genuinely important things. Integrity matters. Respect matters. But when every organisation in a sector shares the same values, those values stop describing anything distinctive about the culture. They describe what's expected of any functioning workplace. Lencioni called these "permission-to-play" values - the minimum standard for operating, not the thing that makes this organisation different from the one down the road.

And here's the deeper issue: a value expressed as a single word is a label, not a tool. "Respectful" tells you what to be. It doesn't tell you what respect looks like when someone disagrees with their director in a room full of peers, or when a deadline means overriding someone's carefully considered objection, or when one team's priorities consistently take precedence over another's. It doesn't connect respect to anything the organisation exists to do.

A label creates obligation. It doesn't create understanding.

Why stated values and lived culture drift apart

Edgar Schein spent decades studying what makes organisational culture work, and one of his clearest observations was this: what an organisation says it values and what it operates on are often two different things. He described three layers of culture. The visible layer - logos, office layouts, dress codes - is easy to spot. The stated values - mission statements, values posters, annual reports - are easy to read. But the layer that drives behaviour is deeper: the underlying assumptions that people have absorbed about how things work around here.

When someone joins an organisation and quickly learns that the real way to succeed is to avoid challenging senior decisions - despite a stated value of "openness" - they've discovered the gap between the espoused and the enacted. And they've learned something important: the values on the wall aren't the operating system. The operating system is the set of unwritten rules that everyone follows and nobody discusses.

This is where the cynicism comes from. The MIT Sloan research found no correlation, on average, between a company's official values and how well those values are practiced day to day. The researchers noted that employees are, in their words, "generally and rightly cynical" about their employer's values statements. Not because employees don't want values to mean something - but because experience has taught them that the poster and the practice don't match.

What values-as-labels do

When values are expressed as single words or short commands - "Be innovative," "Show respect," "Act with integrity" - they do something subtle but important. They prescribe behaviour. They tell people what to be, without giving them the conditions, the context, or the reason.

This turns values into a compliance exercise. They become something assessed in an appraisal ("demonstrate respect: meets expectations / does not meet expectations") rather than something that helps a person make a better decision in a real moment. The value lives in HR systems, not in the work.

It also creates an uncomfortable dynamic. When an organisation names respect, or integrity, or inclusion as a value, it almost always signals a gap. Organisations rarely name the things they're already good at. They name the things they want to become. Lencioni distinguished between core values - the things so deeply embedded they'd persist even if the market punished them - and aspirational values, which name what the organisation hopes to be but isn't yet.

There's nothing wrong with aspiration. But when an aspirational value is presented as a label, it highlights the distance between where the organisation is and where it wants to be, without offering a path between the two. "Be respectful" doesn't close the respect gap. It just makes the gap more visible.

From compliance to commitment

This points to the deeper problem with values-as-labels. They prescribe behaviour. "Be innovative." "Show respect." "Demonstrate integrity." Direct instructions. No context. No agency.

The implicit message is: here is what you should be, and if you're not being it, that's a performance issue. And the response, understandably, is compliance. People perform the value without feeling it. They tick the box in the appraisal. They use the language in meetings. But the behaviour is surface-level because the understanding isn't there.

Genuine behaviour - the kind that shapes culture - doesn't emerge from instruction. It emerges from conditions. When people understand why something matters, when the system supports it, when there's a reason beyond "because the poster says so."

Consider the difference between these two sentences:

"You need to show more initiative."

"The people we serve are counting on us to get this right - so when you see something that could work better, say so. We'll make space to try it."

The first prescribes a behaviour and leaves the person wondering what they did wrong. The second creates the conditions for exactly the same behaviour - but now the person understands why it matters and has permission to act. Both want initiative. Only one is likely to get it.

This is the distinction that separates values that change culture from values that don't. Prescription creates compliance - people performing a behaviour because they've been told to. Conditions create commitment - people choosing a behaviour because they understand why it matters. The difference shows up in every meeting, every decision, every moment where someone decides whether to speak up or stay quiet.

What values-as-tools look like

There's a different approach. Instead of naming a value as a label, you express it as a statement that connects to purpose and comes with a question people can use.

In an organisation I worked with previously, the leadership team developed what they called "common sense principles for how we do things around here." Not values. Principles. The language was deliberate - less corporate, more practical.

Each principle was a statement, not a word. Where a label might say "Respectful," the principle said something closer to: "We never forget our impact - every decision, big and small, leaves a trace. So we're mindful about their impact, collaborating with the right people in the right way." And alongside that statement sat a guiding question: "Have we engaged with the right people, in the right way?"

Someone could take that question into a meeting and use it. Not as a compliance check, but as a genuine prompt for better decision-making. The value wasn't something to be assessed against. It was something to think with.

Several things made this approach different from the typical values exercise.

The principles pointed outward toward purpose - toward the people the organisation served - not just inward toward how staff should treat each other. This matters because when values only describe internal relationships, they become self-referential. "Be respectful to your colleagues" is less powerful than "be mindful of impact because what we do affects people's lives." The first is a workplace rule. The second is a reason.

The principles were road-tested before being adopted. Teams used them in real situations - actual meetings, actual decisions - and fed back on what worked and what didn't. They were piloted, not launched. The language used at the time was revealing: "a good place to start," "see how they work." This wasn't a values roll-out. It was a values experiment.

And the principles were framed as "how we do things around here" rather than "what we must be." This matters more than it seems. "How we do things" describes practice. "What we must be" describes character. One invites reflection on behaviour. The other invites judgement of the person.

Values as part of a connected system

Values don't exist in isolation. They sit within a dependency chain, and each level flows from the one above.

Purpose explains why the organisation exists - who it serves, what difference it's trying to make. The operating model describes how the organisation is configured to deliver on that purpose: its structure, how decisions get made, how teams relate to each other, where authority sits. Values describe the behaviours that make that operating model work. Ways of working turn those values into daily practice. And culture - the thing everyone wants to change - emerges from the whole chain.

When this chain is coherent, values feel obvious. Of course we work this way - it's how the whole thing is designed to function. When it's broken, values feel arbitrary. "Be innovative" means nothing if the operating model doesn't create space for experimentation, or the performance framework rewards compliance, or the strategy doesn't require innovation at all. The value says one thing. Everything else says another. And people, being sensible, follow the system rather than the poster.

This is where values work most often goes wrong. Not in the wording - the wording might be excellent - but in the connection. Values get designed in a workshop, printed, launched, and then expected to change behaviour inside a system that was never adjusted to support them. The operating model stays the same. The performance framework assesses the same things it always has. The decision-making architecture hasn't shifted. The values are new, but everything they need to sit within is old.

It's the organisational equivalent of changing the signage without changing the roads. People read the new signs, note the direction, and then follow the road they're already on - because the road is what determines where they end up.

Gallup's research consistently shows that employees who feel strongly connected to their organisation's purpose are far more engaged than those who don't - roughly five times more engaged, by their most recent data. But that connection doesn't happen because of a values statement. It happens when the whole system - purpose, operating model, values, ways of working, how contribution is recognised - tells a coherent story. When people can trace a line from why the organisation exists, through how it's structured, to what's expected of them and why, the values stop being words and start being logic.

This is probably the most important thing about values work: it's system work, not communications work. Values are one element in a connected system. When they're treated as standalone - designed, launched, and then expected to change culture on their own - they're set up to fail.

Starting with a different question

Most values exercises start by asking: "What do we want our values to be?" It's a reasonable question. But it might be the wrong one.

A better starting point might be: "What would help our people make better decisions about the things that matter most?" That question leads somewhere different. It leads toward purpose, toward practical tools, toward guiding questions that people can carry into real moments. It leads away from posters and lanyards and toward the actual work.

The organisation I mentioned earlier never called their principles "values." They called them principles. They tested them. They connected them to purpose. They gave people a question to carry into a meeting. And the behaviours that emerged - the mutual respect, the ownership, the care - emerged because people understood why they mattered, not because they were told to show them.

Values that change behaviour aren't labels. They're tools. And the difference between the two is the difference between a word on a wall and a question in a room.