If It Cannot Hold Up Under Pressure, It Is Not Your Value.
If It Cannot Hold Up Under Pressure, It Is Not Your Value.
At one point I worked for a company that called itself people first, back when declaring that as a value was a popular thing to do. The same company ran its yearly evaluations on a stack ranking. The curve needed people below "meets expectations," so people who had done everything asked of them, and more, were told they had not met expectations.
The same company had a rule I still think about. If a manager missed the deadline to submit an employee's yearly review, the employee lost the raise and the bonus. There was no written penalty for the manager who missed it. The system told everyone exactly where we stood, and in my read, it told us whose side HR was on.
It made me question whether this was a company I wanted to be associated with. I saw it as an ethical dilemma: exit because I disagreed with those policies, or stay and protect my team from them. Leaving would not have changed anything for my team, and it would probably have left them worse off. I genuinely cared about that team, so I drew a line before anyone asked me to cross it: I would stay as long as I could shield them, and I would leave rather than be part of delivering reviews I found morally reprehensible.
I made sure my own reviews were always in early. I also believe in full disclosure, so I told my team exactly what I was protecting them from. They needed to know who they really worked for.
At a dinner in Manhattan last month, a table of technology leaders landed on culture, and I said what that company taught me. I go by what your team and your managers reward under pressure, because that is your culture, and everything you put on the wall is just crap on a wall. If it cannot hold up under pressure, it is not really your value. Someone at the table pushed back: culture, they said, is how people make a real decision, not only what happens under pressure. They were right, and it sharpened the point, because pressure is where the real decisions get made.
The usual story says culture is set by stated values, reinforced by leaders who live them, and measured by engagement surveys. When the surveys dip, the fix is a values refresh: new posters, an offsite, a leadership pledge. Almost every technical leader has worked somewhere that put "people first" on the wall, and most remember the exact moment a review cycle showed them what it meant.
Teams learn values from consequences, not declarations. Every review cycle, the system teaches two things: who pays when something goes wrong, and what gets protected when something has to give. The forced curve taught that a rating was a budget variable, and the late-review rule taught that accountability flows down, never up. Those lessons are learned once and remembered, which is what I call Culture as System Memory, and no poster overwrites them.
This is what I call The Flip: a company shows one value in public and rewards the opposite in private, and only one face is visible at a time, depending on the angle. Nothing forced that company to show the face it did. It could have rated everyone at "meets expectations" or above and still stayed inside its budget, or ranked people for raises and bonuses without retroactively telling them they had failed. No budget logic explains making an employee pay for a manager's late review. Those were design choices, and the design was the value.
The costs arrive quietly. People stop being candid in reviews and start managing their ratings. The people with options leave first, because they can. Every stated value after that is discounted, including the ones that are true.
The leaders who hold a line inside a system like that do not have more authority than anyone else. They decided where the line was before the pressure arrived. When the system routes around you anyway, that is a clear sign it is time to move on.
So treat culture as a design, not a statement. A company that means "people first" keeps the verdict on a person's work separate from the budget for raises, and puts the consequence of a failure on whoever failed, so the manager pays for the late review, not the employee. A leader inside a system they cannot redesign has three moves. Draw your line before the pressure arrives, tell your team the truth about the system they work in, and visibly reward the opposite of the bad design in your own part of it. What you reward under pressure becomes your team's culture, whatever is on the wall.
Take your company's stated values. Next to each one, write the last time keeping it cost something, and what won instead: the money, someone's ego, or a political win. Then do it for yourself: what did you reward the last time your team was under real pressure? If either column does not match the wall, your team already knows. The only open question is whether you have told them what you are protecting them from.
LeadershipOS™ has the full Culture layer: how a team's expectations are encoded by what the system actually rewards and tolerates, and how a leader rewrites them in their own part of the company: https://TheLeadershipOSBook.com
