From Poster to Practice: What One Value Looks Like All Week

Values fail at the same point every time: the moment they'd cost something. The gap isn't belief, it's translation. Nobody has written down what the value looks like in the five or six recurring moments where it would actually apply.

So here's one value, traced through one week. The value is 'we tell the truth early.' The company is a 40-person software business — but nothing here is software-specific.

Monday — Hiring

A hiring panel debriefs on a strong senior candidate. Two interviewers liked her; one flagged that when asked about a failed project, she described it entirely in terms of what other teams did wrong.

Under a decorative value, that flag gets softened — 'everyone's a bit defensive in interviews' — because the pipeline is thin and the role has been open ninety days. Under a practiced value, the panel treats it as directly disqualifying evidence against a named behavior, and says so in the notes.

What made it possible: their interview scorecard has a line item literally called 'tells the truth early,' with a required prompt — 'tell me about something you got wrong and when you told someone.' The rubric distinguishes three answers: told someone immediately and unprompted, told someone when asked, or discovered by others. That's the whole mechanism. The value is enforceable because someone wrote the question down.

Tuesday — Prioritization

Planning meeting. A commitment made to a customer three weeks ago is going to slip by roughly two weeks. Everyone in the room knows it. The question is whether it goes in the notes today or gets 'reassessed next week.'

Their rule: any slip greater than 20% of the original estimate is communicated to the affected party within 48 hours of the team knowing — not within 48 hours of certainty. Certainty is a delaying tactic.

The cost is real. The customer was unhappy on Tuesday instead of pleasantly surprised on Friday and furious two weeks later. The organization accepted that trade explicitly, in writing, before it came up — which is the only time you can make that decision honestly.

Wednesday — Feedback

A team lead has been avoiding a conversation with a strong engineer whose code reviews are dismissive enough that two juniors have stopped submitting work to him.

'Tell the truth early' applies most expensively here, to a manager, about a high performer. Their operational rule: feedback about behavior that affects someone else's work is delivered within five working days, not saved for a review cycle. They give managers a script — describe the observable behavior, name the effect on someone else, ask what they saw, agree on one change.

The five-day rule matters more than the script. Deadlines make courage administrative, which is the only reliable way to get it.

Thursday — A customer decision

Support discovers a bug that has been quietly miscalculating a report for eleven customers over six weeks. Nobody has complained. Nobody would notice.

This is the value's actual test — a case where silence is free and disclosure is expensive. They notified all eleven, with what happened, the corrected numbers, and what changed to prevent recurrence. Two customers were annoyed. One replied that it was the reason they'd renew.

What made the decision fast rather than agonizing: a pre-written rule that disclosure decisions of this type are made by the support lead and don't require executive sign-off. Requiring escalation would have created a day of hesitation, and hesitation is how organizations discover their values are aspirational.

Friday — Recognition

In the weekly appreciation round, the person recognized most specifically is the support engineer who raised the bug — not for fixing it, but for surfacing it when she could have quietly patched it.

This closes the loop. Everything above is only credible if the person who paid the social cost of telling the truth early gets visibly rewarded for it. If she'd been thanked privately and the celebration had gone to the fastest fix, the whole week would have taught the opposite lesson.

What the week reveals

• Every enactment was a pre-written rule, not an act of individual character: a scorecard prompt, a 48-hour disclosure trigger, a five-day feedback deadline, a delegated decision right, a recognition ritual.
• Each rule has a cost the company agreed to accept in advance — a longer search, an earlier unhappy call, an awkward conversation with a top performer, eleven emails nobody demanded.
• None of it required believing anything. It required deciding in calm conditions what you'd do in expensive ones.

The template: do this for one of your values

Pick one value. Only one. Then answer these six questions in writing, with a named owner for each:

1. 1Hiring — what interview question would reveal this, and what does a failing answer sound like? Add it to the scorecard.
2. 2Prioritization — what trade-off does this value force when time or money is short? Write the rule and the threshold.
3. 3Feedback — what behavior would violate this, and within how many days must it be raised?
4. 4Customer decisions — where does this value cost us money or comfort, and who is authorized to pay that cost without escalating?
5. 5Recognition — what act, specifically, gets celebrated publicly? Name a recent example.
6. 6Consequence — what happens the third time someone senior ignores this? If the answer is nothing, the value is decoration and you should either fix the answer or delete the value.

That's a two-hour exercise per value. Do it for one, run it for a quarter, and you'll learn more about your culture than any survey will tell you — mostly from watching which of the six rules your organization quietly declines to follow.