BlogCase Study

From Poster to Practice: Living a Value All Week

November 4, 2026 · 12 min read

The short version

Values fail at the moment they'd cost something. Follow one value through a working week and a six-month turnaround, then use the template to wire one of yours into the work.

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 each manager improvises, and employees can't predict which version will be rewarded.

This guide traces two examples. The first follows one value through one week at a 40-person software business. The second follows a composite company, Northstar Labs, through six months of turning a poster value into practice. Nothing in either is software-specific.

Part 1: One value, one week

The value: "we tell the truth early."

Monday — Hiring

A panel debriefs on a strong senior candidate. One interviewer flags that, asked about a failed project, she blamed it entirely on other teams. Under a decorative value, that gets softened because the role has been open ninety days. Under a practiced value, the panel treats it as evidence against a named behavior. What made it possible: a scorecard line called "tells the truth early," with a required prompt — "tell me about something you got wrong and when you told someone" — and a rubric for three answers: told someone immediately and unprompted, told someone when asked, or discovered by others.

Tuesday — Prioritization

A customer commitment is going to slip by two weeks, and everyone in planning knows it. Their rule: any slip over 20% of the estimate is communicated to the affected party within 48 hours of the team knowing — not of being certain. Certainty is a delaying tactic. The customer was unhappy on Tuesday instead of furious two weeks later, a trade the company accepted in writing before it came up, which is the only time you can make that decision honestly.

Wednesday — Feedback

A lead has been avoiding a conversation with a strong engineer whose dismissive code reviews have made two juniors stop submitting work. The rule: feedback about behavior that affects someone else's work is delivered within five working days. The script — describe the behavior, name the effect, ask what they saw, agree one change — matters less than the deadline. Deadlines make courage administrative, which is the only reliable way to get it.

Thursday — A customer decision

Support finds a bug that has miscalculated a report for eleven customers over six weeks. Nobody has noticed. They notified all eleven with what happened, the corrected numbers and the prevention fix. Two were annoyed; one said it was why they'd renew. The decision was fast because a pre-written rule let the support lead make it without executive sign-off. 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. If 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 disclosure trigger, a feedback deadline, a delegated decision right, a recognition ritual.
  • Each rule had a cost the company agreed to 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.

Part 2: Six months at Northstar Labs

At 180 employees, Northstar had five polished values, including candor. Leaders called the culture direct; employees called it friendly, fast and careful around senior people. Product concerns surfaced late, hiring panels avoided strong negative signals, and reviews celebrated delivery while leaving avoidable mistakes unnamed.

Before: candor meant personality

  • Managers each defined it differently — bluntness, transparency after a decision, or raising concerns privately to keep meetings positive.
  • Interviewers asked whether candidates valued honest feedback, a question with one socially acceptable answer.
  • Leadership meetings invited questions after the decision had effectively been made.
  • High performers who withheld information faced no consequence if they still delivered.

Step 1: Define the behavior at a moment of pressure

Three behaviors replaced the abstract definition: raise a material concern within two working days; state the evidence and the risk, not an accusation; and tell the person affected before escalating around them, unless safety or misconduct is involved. They also set boundaries — candor was neither permission to be careless with people nor a duty to confront someone privately when that would be unsafe.

Step 2: Put the value into hiring

The new question: "Tell us about a time you raised a concern that could have made your work or relationships harder. What did you say, what happened, and what would you do differently?" The scoring guide looked for timely action, specific evidence, ownership of impact and learning — not forcefulness or a particular style, which kept the value from becoming a disguised personality filter.

Step 3: Redesign a leadership routine

The Monday operating review gained a ten-minute red-team segment: the decision owner names the strongest risk to their plan, one colleague adds a risk they think is underweighted, and the executive sponsor speaks last. The first month was awkward and vague. By month two it improved, because every concern had to end with evidence, possible impact and the next question to answer.

Step 4: Make recognition and consequences agree

Managers named candor in performance conversations only when they could cite the behavior and result. A product manager was recognized for raising an integration risk two weeks early, even though it delayed a launch. More importantly, a senior leader who repeatedly withheld known delivery risks lost ownership of the program. That carried more weight than a year of recognition posts: employees watch what happens when a value conflicts with status and results.

After six months

  • Material risks appeared earlier in weekly reviews, while anonymous escalation fell.
  • Interview notes contained behavioral evidence instead of culture-fit impressions.
  • Retrospectives distinguished directness from disrespect and named both when needed.
  • Employees could explain what candor required, where it had limits, and what happened when leaders ignored it.

The four gaps both stories expose

  1. 1Language without a moment: a value must say when the behavior is most needed.
  2. 2Behavior without a system: hiring, meetings, performance and consequences must reinforce the same definition.
  3. 3Recognition without cost: a value becomes believable only when following it is inconvenient.
  4. 4Accountability without leadership: senior people must face the same consequence, visibly.

The template: do this for one of your values

Pick one value — only one. Define three observable behaviors for it, then answer these 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 it, and within how many days must it be raised?
  4. 4Leadership routine — which recurring meeting will give this value a standing slot, and who speaks last?
  5. 5Customer decisions — where does it cost money or comfort, and who may pay that cost without escalating?
  6. 6Recognition — what act, specifically, gets celebrated publicly? Name a recent example.
  7. 7Consequence — what happens the third time someone senior ignores it? If the answer is nothing, fix the answer or delete the value.

That's about two hours per value. Run it for a quarter and you'll learn more about your culture than any survey will tell you — mostly from watching which rules your organization quietly declines to follow. Every empty space in that chain is where the poster stops and the real culture begins.

Related resource

Core Values Worksheet

Turn abstract values into observable behaviors, with prompts for hiring, feedback, and recognition.

Get the Core Values Worksheet

Free download

Get the Culture Starter Kit

Mission worksheet, values worksheet, and team norms template — delivered to your inbox.