What a value refuses.
A company's values are usually written down somewhere, but written down is not the same as in force. Part of that gap is expected. A value is allowed to be something you reach for, that's part of what makes it one. But that gap used to be forgiven as aspiration, and now it reads as a reason not to trust.
These days, it’s easy for people to check the values page against what a company actually does. That suspicion now carries over to everyone, including careful people who meant every word. A gap once seen as hypocrisy has now become structural.
A company’s values usually come out of some form of work session. The room surfaces words that feel true, and then they're carefully crafted until they sound like the company. These values are built to define the company and state the beliefs that should govern how the work gets done. They can be entirely accurate and still decide nothing.
The company’s values usually don’t answer to anything above them. When a decision arrives that cuts against them, nothing consults them and nobody notices. The trouble was never that the “values page” was aspirational. It's that nothing on it could tell the company when it had fallen behind.
That was easy to miss when writing the words took work. The work read as a signal. Now that signal is gone.
A convincing values page now takes about as long to make as it does to ask for. The language, the tone, the coherence — none of it costs anything anymore.
So do a company’s stated values prove anything? Then what does?
The scarcity used to sit in the writing, but it's moved. It now sits in whether those words actually bind anything. There is a test that separates written from in force.
A value becomes governance the moment it is written as a refusal.
"We believe in quality." has no refusal. Nothing is excluded by that. There's no decision it could lose.
Take a belief you mean to decide by, and write what it will not permit. What is the specific thing that you will not do? State it plainly enough that doing it would register as a breach.
Now the sentence has teeth, and those teeth do the work. A belief you can violate without noticing can’t govern you.
That's one half. The other half keeps it from becoming a preference in a firm voice.
A refusal has to derive from something upstream, otherwise it's just arbitrary.
What conviction did you already hold before the refusal was needed? If you can't state it, you haven't written a standard. You've written a rule that you like. A rule you happen to like is the first thing to go when things get expensive.
The two halves are one instrument. Each one fails alone. A refusal with nothing above it is preference. A conviction with no refusal below it is toothless.
One of ours reads:
Not everything that can be built should be built. Capability is not permission. The fact that something can be built is never the reason to build it.
The first sentence is the belief. The second sentence is the refusal. The second is why the first one can lose an argument.
This raises a fair question: does it hold when holding it becomes expensive?
The conviction in this case came first. It was written down before any choice ever arrived.
… the work draws its resonance from the felt connection to its maker, and without origin and intent it can impress at a sensory level while staying hollow at a semantic one.
The refusal, quoted above, was written from it.
Then the decision arrived, at the worst moment. The first system Verstoa built needed to create images. Generating them was free, instant, and what nearly everyone was doing. The refusal held, and not by willpower: the system was built so that it could not reach for the capability.
Every mark is made by hand. It is intentional. It doesn't scale easily, and the advantage it gave up was real and known.
Three links, all published: the conviction, the refusal, the decision. The first and third are in What We Didn't Build; the second is in How We Decide. Read them in that order, and you can check whether the third follows from the first.
That's what the chain is for. It’s not to showcase a good decision. It's to show that the decision was already determined before it arrived, by something written down and built-in. It's the difference between something built with good instincts and something built with a standard, in force.
A track record still asks for your trust. A chain like this shows you, so you don’t have to worry about being asked.
So open whatever your own company has written down. Find the lines you expect to decide things. For each one, ask: what does this line refuse? If a line excludes nothing, if there's no decision it could lose, it's a description.
Then, for the lines that do refuse something, ask: where does the refusal come from? If the answer is that it seemed right, it's a preference. It won't survive the first time where holding it gets expensive.
Two questions. No process underneath them. No part of them needs us.
Written down is easy now, and getting easier. In force is the same price it’s always been.