Design the Behavior, Not the Slogan

Every values rollout that fails, fails in the same place: the word never becomes a behavior. "Ownership" goes on the wall, everyone nods, and nothing about Wednesday changes. The fix is a translation practice you can run on any value in about ninety minutes.

The three columns

For each value, you need three things: observable behaviors, the systems that make those behaviors the easy path, and the signals that tell you whether they are happening.

Column 1: observable behaviors

A behavior passes the test if two people watching the same week would agree on whether it occurred. "Cares about the customer" fails. "Replies to the customer with a date, even when the answer is not ready" passes.

Column 2: supporting systems

Behavior follows the path of least resistance. If the behavior requires courage every single time, it is not designed — it is being subsidized by a few unusually brave people, and it will leave when they do.

Column 3: measurable signals

You do not need a metric so much as a place to look. A signal is any recurring artifact where the behavior would leave a trace: a decision log, a promotion write-up, a retrospective, a customer thread.

Worked example: ownership

Take the most over-claimed value in the corporate world and put it through the columns.

Behaviors

• Says "I own that" in a meeting, with a date, when a gap is found.
• Reports their own slipped commitment before someone else notices it.
• Fixes a problem one step outside their remit rather than routing it.
• Names the decision-maker when they are not it, instead of leaving it ambiguous.

Systems

• Every project has one named owner, visible to everyone, with no co-owners.
• A written decision log where the owner's name sits next to the decision.
• Status reviews that ask "what changed since we committed?" rather than "is it on track?"
• A response protocol for self-reported misses: the first reaction is a question about the system, not the person.

Signals

• Share of commitments where a slip was self-reported before the review.
• Number of items in the decision log with no owner name — the target is zero.
• Promotion write-ups that cite a specific ownership behavior with an example.
• Time between a problem being visible and someone claiming it.

If a value has no owner, no system, and no place you look for it, you have written a slogan and scheduled a disappointment.

How to run this with a team

1. 1Pick one value. One. Rolling out five at once guarantees none of them lands.
2. 2Spend thirty minutes generating candidate behaviors, then cut to four that pass the two-observers test.
3. 3For each behavior, ask what currently makes it harder than the alternative. That answer is your system change.
4. 4Choose one signal per behavior and name where it will be reviewed, and by whom, in ninety days.
5. 5Publish the table. A value people can read as behaviors is a value they can hold you to.

The part leaders skip

The system column is where the work is, and it is the column that requires authority: changing promotion criteria, changing what a review meeting asks, changing what gets rewarded. Behaviors without system changes are a request for volunteers.

Do this once and you have a culture-design practice rather than a values project. The next value takes an afternoon, and everyone already knows what a finished translation looks like.