The board that approved the values statement without reading it

Most organisations have a values statement. It lives on the website, usually near the bottom of the About page. It appears in the annual report, in the onboarding pack, occasionally on a wall in the reception area in a font chosen to suggest permanence. It lists four to six words: Integrity. Excellence. Collaboration. Respect. Sometimes Courage, which is always the most optimistic inclusion. Beneath each word, two or three sentences of elaboration that elaborate nothing.

Almost nobody wrote it. Almost nobody owns it. And in a significant number of cases, the board that formally approved it did not read it carefully enough to have noticed if a word had been changed.

This is not a scandal. It is a process. And that is precisely the problem.

How values statements are made

Values statements are rarely discovered. They are commissioned. There is usually a consultant, or an internal working group, or a facilitated leadership workshop. There is a synthesis document. There is a round of revisions in which the language is adjusted until it is smooth enough to pass without friction, which is to say, until it is vague enough to offend nobody, which is to say, until it commits to nothing that could later be held against anyone.

The resulting document is not dishonest, exactly. The words chosen are words the organisation would genuinely like to be associated with. Nobody in the room argued for Mediocrity or Selective Accountability. The problem is not the aspiration. The problem is what the production process produces: language that has been optimised for approval rather than for meaning.

By the time it reaches the board agenda, it is a formality. It was a formality three drafts ago.

The approval moment

I have been in rooms where this happens and rooms where people describe it happening. The pattern is consistent. The values statement is tabled. Someone may observe that it looks good, or that it captures the spirit well, or that it is clear and accessible. There is no substantive discussion, because there is nothing substantive left to discuss: the language has been worked until it is frictionless, and frictionless language offers nothing to grip. It is approved. The meeting moves on.

What did not happen: anyone asking what Integrity means when it conflicts with a commercial priority. Anyone asking who is responsible for upholding Respect when a senior leader demonstrably doesn't. Anyone asking what Courage has ever required of this institution, and what it might require next year.

Those questions were not asked because they were not the point. The point was the document. The document is now approved.

What language without ownership does

Language that nobody owns is available for any use. This is its defining feature, and its most significant consequence.

If the values statement belongs to everyone in general, it belongs to nobody in particular, which means it can be deployed by anyone, for any purpose, without accountability. It becomes available to describe the organisation as it wishes to be seen, regardless of what the organisation is actually doing. The values statement written in the wake of a trust crisis becomes, in the next annual report, evidence that the trust crisis has been resolved. The word Integrity is cited in the same quarter a decision is made that tests it.

Nobody is lying. The words are right there, approved by the board, published on the website. The words are simply doing no work.

This is what institutional performance looks like at its most stripped-back: not the elaborate performance of culture, but the minimal compliance with its paperwork. The form completed. The box ticked. The document filed under Approved.

When language is actually owned

The opposite of a values statement that nobody reads is not a better values statement. It is a different relationship to language, one in which the words used to describe the organisation are words someone is prepared to be held to.

I have heard versions of this. A charity trustee board. Two non-executive directors had actually read the draft before the meeting, unusual enough that it changed the room. One flagged that accountability appeared in the document but the organisation had no mechanism by which anyone was held accountable for anything it described. She asked what accountability meant, specifically. The chief executive said it was about culture, not process. She said she would like to understand what that meant in practice before approving. The item was deferred.

It came back the following quarter, largely unchanged, and was approved. But the deferral mattered. Something had been named. A person in the room was now on the record as having asked a question the language could not answer.

That is the smallest version of language ownership. Not transformation. Not accountability perfectly designed. Just: someone prepared to say what the word requires, in front of the people responsible for it.

Language that can be held against you is language that means something. The board that reads the values statement carefully, asks the uncomfortable question, and forces a revision nobody wanted, that board has done something the other one hasn't.

It has made a commitment. Small, perhaps. Partial. But genuinely its own.