Values That Actually Guide Decisions

What Culture Actually Is made the case that culture is not the poster on the wall — it is the behavior that repeats when no one is checking. This page zooms in on the piece of culture that gets talked about most and understood least: values.

Almost every team has values. They appear on the careers page, the onboarding slides, the mug. And almost none of them do any work. The point of this page is to show you the difference between a value that is decoration and a value that actually steers a decision — and to give you a way to write the second kind, so that when your team hits a hard tradeoff, the value is in the room helping them choose.

The principle: a value is a tiebreaker, not a virtue

Here is the cleanest way to think about it. A value is only useful at the moment two good things pull in opposite directions and you have to pick one. Everyone agrees you should be honest and fast and profitable and kind. That agreement is free and worthless. The question a value has to answer is: when honesty and speed collide, which one wins?

That is why a value that never costs you anything is not a value — it is a preference you were going to act on anyway. “We value quality” means nothing if you have never shipped later, charged more, or turned down a customer to protect it. The words only become real at the exact point they hurt.

So the test for whether a value is real is brutally simple:

A value is real only if you can name a recent decision where it beat a competing priority — revenue, speed, a powerful person’s ego, or your own convenience.

If you cannot name that decision, you do not have a value. You have a nice sentence.

The evidence — stated values vs. lived values

Researchers who study organizational culture (notably Edgar Schein) draw a sharp line between an organization’s espoused values — what it says it believes — and its values-in-use — what its behavior reveals it actually believes. The two routinely diverge. Studies of what actually predicts employee trust and behavior consistently point to the lived version, not the framed one. The practical takeaway is not a precise number; it is a direction: people read what you do under pressure and quietly ignore what you say when it is easy.

Decorative values vs. operative values

Call the two kinds by their function.

A decorative value is a word that sounds good and asks nothing. “Excellence.” “Integrity.” “Customer obsession.” Notice you cannot argue with any of them, and no one ever will — which is exactly the problem. A word no one can disagree with cannot decide anything.

An operative value is one that has teeth. You can tell it is operative because saying it out loud costs you the other option. “We will lose a deal before we mislead a customer” is operative — it explicitly gives up revenue. “We ship on schedule even when the feature is smaller than we hoped” is operative — it gives up scope. Operative values hurt to say, and that ache is the sign they will actually guide behavior.

Decorative                          Operative
------------------------------      --------------------------------------
"We value honesty."                 "We tell the customer about the bug
                                     before they find it, even if it costs
                                     us the renewal."

"We care about our people."         "We do not email staff on their days
                                     off; an on-call rota covers real
                                     emergencies."

"We value quality."                 "A release with a known safety defect
                                     does not ship, even if the date slips
                                     and finance is unhappy."

The right column names a loser. That is the whole trick.

Turning a value into a decision rule

Vague values fail under pressure because pressure is a form of fog — deadlines, tired people, a frustrated boss, an angry customer. In fog you do not want to interpret a value; you want to apply one. So write your values in a form that can be applied without interpretation:

When X conflicts with Y, we choose Z.

That shape forces the two things you actually care about into the open (X and Y) and states which one wins (Z). Compare:

Vague:  "We value safety."
Rule:   "When a delivery deadline conflicts with a driver's legal rest
         hours, we choose the rest hours and move the deadline."

Vague:  "We're customer-first."
Rule:   "When a customer request conflicts with a promise we made to
         another customer, we keep the existing promise and say no to
         the new one."

Vague:  "We value learning."
Rule:   "When shipping fast conflicts with writing down what went wrong,
         we take the extra hour to write the review — every incident, no
         exceptions."

A rule in that form does three things a slogan cannot. It tells a new hire what to do on day one without asking anyone. It settles an argument by pointing at the shared rule instead of the loudest voice. And it makes the value falsifiable — you can check whether you actually followed it, because it names a specific behavior.

In practice — the rule that ends the meeting

A hospital ward agrees on one rule: when a nurse’s read on a patient conflicts with the written protocol’s timing, we pause and escalate rather than push ahead. Months later a junior nurse feels something is wrong with a patient who technically still fits the discharge criteria. Under a vague value (“we value patient safety”) she might have deferred to the senior clinician and the schedule. Under the rule, she has explicit permission — an obligation, even — to stop the line. She escalates. The pause catches a real problem. The value did its job because it had already been converted into a specific action for a specific collision.

Two failure modes: too many, and never conflicting

Even teams that write good rules undermine them in two predictable ways.

Too many values

If you list ten values, you have listed none. The purpose of a value is to break a tie, and a tiebreaker only works if it is ranked above the alternatives. Ten equal values means that whenever two of them collide — which is constantly — you are back to guessing. The discipline is to keep the list short enough that people can hold it in their head and know the order. Three or four is plenty. What matters is not how inspiring the list reads but whether a stressed person at 5 p.m. can recall it and act on it.

Values that never conflict with anything

The second trap is subtler and more common. Teams pick values that are all pointing the same way — “excellence,” “quality,” “high standards,” “rigor” — so they never actually pull against each other. A value only earns its place by being willing to lose to a competing priority. If none of your values ever costs you money, speed, or comfort, they are all decorative, no matter how many you have. A good gut-check: for each value, ask “what does this one make us give up?” If the honest answer is “nothing,” cross it out.

The common trap — the values that only bind other people

A frequent failure is a value that applies to the team but not to the person who wrote it. “We value work-life balance” while the founder emails at midnight. “We value candor” while feedback to the boss quietly ends careers. People calibrate to the exception, not the rule — the moment a value visibly bends for someone powerful, everyone learns the real rule is “the value applies unless it’s inconvenient for leadership.” The fix is not more communication; it is the leader visibly paying the cost of the value first, in a case where it hurts them. That single act teaches more than a year of all-hands slides.

A worked example: ship it now vs. do it right

Here is the tradeoff nearly every team faces in some form. A café is opening a second location; a software team is pushing a release; a warehouse is onboarding a new sorting process. The pattern is identical: there is pressure to launch now, and a quieter voice saying it is not actually ready.

Watch how a decorative value and an operative rule handle the same moment.

The situation
-------------
Launch is Friday. The team finds a real problem on Wednesday: not
catastrophic, but it will hurt some customers and it will be embarrassing.
Fixing it properly means slipping to the following week. Sales has already
told two clients "Friday." The room is split and everyone is tired.

With a decorative value — “we value quality” — the argument goes in circles, because both sides can claim it. The ship-it camp says “quality also means delivering on our commitments.” The fix-it camp says “quality means not shipping a known defect.” The value settles nothing, so the decision defaults to whoever is most senior or most insistent. That is not a values-driven decision; it is a power-driven one wearing a value as a costume.

Now suppose the team had already written the operative rule:

When a launch date conflicts with a known defect that will visibly harm customers, we move the date. We would rather be late than sorry. Sales commitments are made with this rule known, and we un-promise honestly.

The Wednesday conversation is short. The rule names the exact collision (date vs. known customer-harming defect) and names the winner (the date moves). Sales does the uncomfortable call because the rule already accounted for it. No one has to relitigate the company’s soul at 6 p.m. on a Wednesday. Notice what made this work: the rule was written before the pressure, in calm conditions, and it explicitly chose to lose something — the Friday date, and a little credibility with two clients. That cost is not a flaw in the rule. It is the proof that the value is real.

And critically — the next time this happens, the team does not start from zero. They point at the rule. Over time that is what a real value buys you: fewer exhausting debates, faster and more consistent decisions, and a team that trusts the choice was principled rather than political.

Case study — Netflix’s culture deck, 2009

When Netflix published its internal culture document in 2009, the line that drew the most attention was blunt: values are only real if they are matched by “who gets rewarded, promoted, or let go.” The deck argued that most companies’ stated values are aspirational at best and hypocritical at worst, precisely because the espoused words and the promotion decisions point in different directions. Whatever you make of Netflix’s specific practices, the lesson is durable and testable in your own team: look at your last few promotions and exits, and you will read your actual values far more accurately than in any values statement.

How it connects

Operative values are the machinery behind the culture described in What Culture Actually Is — repeated behavior under pressure. They are also the raw material of Trust and Fairness: people trust a team whose values hold up when they are expensive, and distrust one whose values bend for the powerful. And several of the hardest values to honor — protecting rest over output, saying no to a lucrative-but-wrong request — get their own treatment in Sustainable Pace and Ethics and Integrity.

Try this

Take one value your team actually claims — pick the most-repeated one. This week, do three things. First, find a recent decision where it beat a competing priority (revenue, speed, or someone’s ego); if you cannot find one, that is your answer, and the value is decorative. Second, rewrite it as a single rule in the form “when X conflicts with Y, we choose Z,” naming the thing you are willing to lose. Third, run it past one teammate and ask: “Is this actually how we behave, or how we wish we behaved?” Their answer tells you whether you have a value or a wish.

Reflect

1. Name one value your team states out loud. Can you point to a recent decision where honoring it cost you money, speed, or comfort — and if not, what does that tell you?
2. Pick a real tradeoff your team keeps re-arguing. Written as “when X conflicts with Y, we choose Z,” what is X, what is Y, and have you ever actually agreed on Z?
3. Which of your stated values never conflicts with anything — and so is doing no work at all?
4. Is there a value that binds the team but quietly bends for whoever holds the most power? What has that taught everyone about the real rule?
5. Think of the last hard decision that got settled by seniority or volume rather than a shared rule. What rule, written in advance, would have settled it on principle instead?

Show reflections

1. The useful move here is honesty about the absence of a cost. If you truly cannot find a decision where the value lost you something, you have surfaced a decorative value — which is worth more than pretending otherwise, because now you can either make it operative or drop it.
2. This forces the two competing goods into the open. Teams re-argue the same tradeoff precisely because they never named the collision or agreed on the winner. Getting X, Y, and Z on paper once, in calm conditions, is what ends the loop.
3. A strong answer names a value that only ever agrees with your other goals — usually a synonym for “be good.” Those are safe to say and useless to apply. Cutting them makes the remaining values sharper.
4. This is the trust-killer. The lesson people take from a bent value is not the value itself but the exception — “it holds unless leadership finds it inconvenient.” The fix is a leader visibly paying the cost first; look for whether that has ever happened.
5. This is the whole point of the page. If the last hard call was settled by who was loudest or most senior, a pre-written rule would have replaced power with principle — and, just as importantly, made the decision faster and more trusted the next time the same collision arrives.