Culture is behavior, repeated
Culture is not your values poster. It's what people actually do — in meetings, in code reviews, in hard conversations. The repetition is the culture.
Foundations
A short, practical primer on what culture is, what it isn't, and how to start shaping it on purpose.
Culture is not your values poster. It's what people actually do — in meetings, in code reviews, in hard conversations. The repetition is the culture.
The way a senior leader handles disagreement in a meeting teaches more than any all-hands. Culture is taught by what's tolerated, rewarded, and ignored.
If you reward heroics, you'll get burnout. If you reward learning, you'll get experiments. Look at what gets promoted, paid, and praised.
Founders and leaders set the floor and the ceiling. You can't outsource culture to HR or hope it forms on its own.
The real test of culture isn't the all-hands or the values poster — it's Tuesday afternoon, no one senior in the room. Does the team still ship honestly? Do they still flag the bug they caused? Culture is the behavior that survives the absence of an audience.
Onboarding paperwork teaches process. The first two weeks teach culture — what gets praised in their first standup, what happens when they ask a "dumb" question, whether their manager's calendar has room for them. New hires absorb the real rules before they've read the handbook.
Every "just this once" exception is a loan against your culture. Let one person skip the process, tolerate one missed deadline without conversation, and you've just taught everyone watching what the real rules are. The interest comes due later, and it's expensive to unwind.
Values don't turn into behavior by themselves — rituals carry them. How you run retros, how promotions get decided, what gets said out loud in a standup: these are the pipes values flow through. If you want different behavior, don't rewrite the values doc. Change the ritual.
Dashboards announce priorities louder than any values statement. If you say "we value quality" but only ever review velocity, the team will optimize for velocity — and they'll be right to.
If the people leaving describe a different culture than the one leadership believes exists, that gap is the truth. Exit interviews are one of the few moments people finally say what they'd been managing around.
A brilliant strategy executed by a culture that doesn't support it doesn't fail loudly — it fails quietly, in a hundred small compromises, until it collapses all at once. Check culture fit before you bet on the plan.
Tolerating one "brilliant jerk" because of their output teaches everyone else what's actually rewarded — no matter what the values doc says. The cost shows up later, in the people who quietly leave because of them.
What works at 10 people — osmosis, proximity, everyone in one room — breaks at 100. Culture that isn't made explicit and re-taught deliberately doesn't survive growth; it just dilutes.
The "small moments" model assumes hallway proximity. Without it, async rituals — how you write updates, how you handle disagreement in a thread — have to do that work instead, on purpose.
Skip the survey. Look at meeting recordings, promotion decisions, who got let go and why, and the tone of your team's Slack on a bad week. That's your culture — the survey just tells you what people think they're supposed to say.
Don't try to overhaul culture with a new values doc. Pick one behavior you want repeated — "we surface bad news early," say — and visibly reinforce it for a quarter. Behavior change is how culture actually moves.
Culture forms whether you shape it or not. The only real choice is deliberate versus accidental — and accidental culture tends to reward whoever's loudest or most tenured, not whoever's right.
Culture is the set of behaviors your organization repeats — especially under pressure. Mission sets direction. Values name what matters. Rituals and systems are how those values become behavior at scale.