Your Team Already Knows Your Real Values. Your Systems Taught Them.

The promotion went to the wrong person, and I was the one who signed it.

He was the engineer everyone called when a system went down at two in the morning. He always answered. He always fixed it, pulled the all-nighter, walked out a hero by sunrise. What I didn’t see for too long was that he was the reason the system kept going down. He kept the critical pieces in his own head, undocumented, so that he stayed the only person who could put them back together. Every save was a problem he had quietly built.

Down the hall sat an engineer who had spent the year making other teams faster. She documented the messy systems nobody wanted to touch. She unblocked three departments that had been stuck for months. She trained two junior staff well enough that the late-night calls to her had stopped. Her year produced no heroics, because she had removed the need for them. She got a solid review and stayed exactly where she was.

I promoted him. I told myself it was about talent and visibility and trust earned in the trenches. By that Friday, every person on my team had quietly updated their understanding of what I actually valued. Not from the statement on our wall, which said service and collaboration. From the promotion.

What Your People Actually Read

You’ve probably done the values work. The offsite, the statement, the all-hands where everyone nodded. Here’s the part that stings. A values statement is the easiest thing in the world to write, and the easiest thing for your people to see through. They don’t learn what you stand for from the wall. They learn it from your systems. Who gets promoted. What the review form actually scores. Which requests your policies make easy, and which ones they bury under three approvals. Drop a new hire into your shop, give them two weeks, and they can recite your real list back to you. It’s almost never the one hanging in the frame.

The statement on the wall is a footnote to the budget. Culture is taught by what you measure, what you reward, and what you quietly tolerate. I didn’t learn that from a book. I learned it watching a good engineer update her résumé three months after I handed the title to the wrong man.

Load-Bearing Values

Here’s the test I use now. A value is load-bearing when something would fall down if you removed it. A hire you would refuse to make, even for real talent. A behavior you would not promote, no matter how visible the save. A budget line you would defend when the money gets tight. A policy you would have to rewrite by tomorrow. If nothing in how you actually operate depends on a value, it’s not a value. It’s decoration.

My IT shop had service and collaboration on the wall and not one system that depended on either. Nothing would have changed if I had taken the words down. That’s the tell. The value my engineer lived, making other teams better, was real to her and invisible to my org chart. The value I rewarded, the dramatic solo save, was the one my people learned to chase.

Decoration isn’t harmless. An empty values statement breeds a quiet kind of cynicism, and it spends the credibility of the leader who hung it. Wells Fargo is the textbook case. The company built its stated values around the customer, then paid and promoted people for opening as many accounts as they could. Staff opened millions that nobody asked for. The statement said one thing. The incentives said another. The incentives won, the way they always do.

Stop Editing the Statement. Start Auditing the Systems.

The fix isn’t a better sentence. It’s taking the one value you most want to be true and forcing it to carry weight everywhere a decision actually gets made. Say the value is this: we serve the departments as partners, not as gatekeepers. Here’s what that looks like when it’s load-bearing instead of laminated.

Hire for it. Screen for the candidate who asks about the people they will serve, not only the stack they will run. The question someone asks in the interview tells you which job they think they’re taking.

Onboard into it. Make week one the story of getting a caseworker back online, not a login and a handbook. The first real thing a new hire does is the thing they learn the job is about.

Score it. Put it on the review form. Rate whether a person made other teams better, not only what they personally shipped. People optimize for what gets measured, every single time.

Write it into policy. Build your intake around the partner’s problem, not your queue. A policy that’s easy to comply with and serves the end-user is worth more than any value posted above the printer.

Design for the worst day. Build the service around an end-user’s worst day, not around your org chart. The user doesn’t care how you’re organized. They care whether it holds when their deadline is looming and the system is down.

An IT leader I mentored did exactly this with one line on a review form. He started scoring his engineers on how much they helped other teams, and he said it out loud in every one-on-one until they believed he meant it. It felt small. Within a year, the two people who used to hoard systems to look indispensable were the ones running toward other departments’ problems, because that had become the behavior that got you noticed and promoted. He never rewrote his values statement. He rewrote what the organization rewarded, and the values came true on their own.

The Stakeholder Never Reads the Statement.

Here’s what took me too long to understand. Stakeholders will never read your values statement. They experience it, in whether the service held up on the worst day of their year. Your people won’t recite it either. They’ll live whatever your systems reward, the same way mine learned to chase the midnight save instead of the quiet fix that would have prevented it.

So stop polishing the words and start auditing the systems that carry consequences. Build the value into your hiring, your onboarding, your review form, your policies, and the way you design a service, and the words on the wall come true without anyone having to memorize them.

That’s what integrity means. The word comes from whole. A vision has integrity when it’s the same thing on the wall, in the budget, and in the performance review.

Make it load-bearing. The rest is just paint.