Most small business values documents don’t change how anyone behaves. They exist on a wall or a website and are referenced at hiring and never again. The gap is not in the values themselves; it is in the specificity. A value that can mean anything means nothing.
A useful values document doesn’t list abstract virtues. It shows what each value looks like in this business’s actual situations. Not “we value integrity” but “here is what integrity means when a supplier asks for an exception.”
Answering those questions is what makes a values document a real thing rather than an aspiration. The Culture Audit from What Culture Actually Is in a Small Business — and How to Build It Intentionally identifies what values the business actually has. This article turns those values into something that can guide decisions.
The Behavioral Values Document is the structure for doing that.
Why Generic Values Don’t Shape Behavior
The obvious problem: “We value integrity.” Everyone values integrity. The value doesn’t help anyone make a decision they wouldn’t have made anyway.
The less visible cost is what generic values do to the onboarding of new hires. A new person reads the values and learns nothing useful. They learn that the company says it values things that every company says it values. The information that would help them is absent: how this business handles value conflicts, or the situation where the easy answer is wrong.
The deepest problem is that generic values are not enforced because they can’t be enforced. A value that is specific enough to describe behavior is specific enough to use as a standard. A value that is vague enough to mean anything is too vague to apply. When a team member behaves inconsistently with the values, you cannot use the values as a standard if they don’t describe the behavior.
The behavioral version of a value names the specific action or decision that the value produces.
The Behavioral Values Document
The document has three parts for each value in the business’s core set. Most businesses have three to five real values: the ones that actually determine how people behave, not the aspirational list.
Part 1 names what the value looks like in practice
For each value, write two or three sentences describing what a team member should actually do, or not do, when this value is relevant.
“Integrity: when a client asks you to do something you believe will harm their interests, you tell them. You don’t do it to keep the relationship comfortable. You tell them because they hired you to tell them.”
That is a specific description of integrity in the context of this business. A team member facing a client request they’re uncomfortable with can now check their behavior against a specific description rather than against a vague principle.
Part 2 names the situations where this value is most tested
Every value has situations where it is easy to uphold and situations where it is difficult. The document names the situations where the value is most likely to be tested in this business.
For a business where billing is complex, integrity gets tested when billing decisions are ambiguous. For a business that serves clients who are sometimes wrong, client-first gets tested when the client is asking for something that isn’t in their interest. For a business with high growth, accountability gets tested when someone misses a target during a period when everyone was stretched.
Naming these situations in the values document tells team members when to pay special attention to a specific value. It makes the value relevant to the actual work.
Part 3 gives an example from the business’s own history
The most powerful element of a behavioral values document is a real example from this business’s past. A decision that was made consistently with the value, and what the outcome was. Or a situation where the value was tested and the business did the right thing even when it was expensive.
Real examples make the values concrete in a way that descriptions cannot. A team member who reads “we walked away from a client because continuing would have required compromising quality” understands what the value means in practice. The example is more persuasive than the principle.
If there is no example that fits, the value is aspirational, not actual.
How the Living Library Maintains Your Behavioral Values
When a new person joins and a difficult decision arises, the Behavioral Values Document is the place they should be able to look.
The Living Library is the part of the Kiluma platform where the business’s accumulated culture knowledge lives. When you add examples of how values were applied in practice, the Library reads them and keeps the document current.
When the next difficult decision happens, the team member opens the document and finds it specific enough to be useful. Not a list of virtues. A set of descriptions, situations, and real examples that make the values actionable in the context of this business.
The Conductor, Kiluma’s context-aware AI, can read the values document to help prepare for conversations about specific decisions. Ask it: “Based on our values, how should we think about this situation?” It reads the Behavioral Values Document and returns the value most relevant to the decision and what the document says that value means in practice.
Write One Value This Week
Take the one value that comes up most often in this business’s actual decisions. Write the three parts for that value only: what it looks like in practice, when it gets tested, and a real example.
Keep it to a single page. Don’t write the whole document. Write one value and see whether the description is specific enough that a team member could use it to guide a decision.
If it is, the document has started. If it isn’t, revise until it is.
The Document That Makes the Culture Speakable
An articulated culture isn’t more bureaucratic than an unspoken one; it is more honest. The Behavioral Values Document turns “this is how we do things” from an absorbed feeling into something given explicitly on day one. The culture becomes speakable because it has been spoken. Try Kiluma free for 14 days at kiluma.ai.