Every company has values. There are usually five of them, they end in "-tion" or "-ity", and they hang in a frame at reception or sit on an onboarding slide. And almost every company has a gap between those values and what happens on a Tuesday afternoon.
That gap isn't hypocrisy. It's a lack of ritual.
Culture is what repeats
A definition that helps me a lot: culture is the set of behaviors a company rewards, tolerates and repeats. Not what it declares.
If the value is "transparency" but the important decisions are made in hallway conversations and announced in a short email, the real culture is "closed decisions". If the value is "growth" but nobody has had a career conversation in six months, the real culture is "every person for themselves".
What turns a value into culture is the repetition of concrete practices, on a defined rhythm. That's what I call ritual.
The rituals that hold a culture up
You don't need to invent much. The rituals that make the biggest difference are well known. The hard part is keeping them alive.
One-on-ones (1:1)
A recurring conversation between a leader and a team member, with the team member's agenda, not the leader's. It's the cheapest ritual and the most neglected one. When it disappears, problems only surface once they've already become a resignation letter.
Continuous feedback
Feedback that only shows up in the annual review arrives late and arrives heavy. The healthy ritual is feedback that's small, frequent and specific: what happened, the impact, what could change (or keep going).
Review cycles
A review doesn't have to be a dreaded event. With conversations and feedback happening throughout the cycle, the review becomes a consolidation of what has already been said, not a surprise.
Recognition
What gets celebrated publicly teaches more about the culture than any handbook. If only hitting targets gets celebrated, the message is "results at any cost". If the person who helped a colleague, who raised a problem early, who learned something also gets celebrated, the message changes.
Why rituals die
Almost every leader agrees that 1:1s and feedback matter. Even so, the rituals die. The reasons repeat:
- Urgent beats important. The 1:1 is the first meeting to be cancelled when the week gets tight.
- Nobody remembers. Without a system, the ritual depends on each leader's memory and goodwill.
- It leaves no trace. What was agreed in the conversation gets lost, and the next one starts from scratch.
- The leader doesn't know how to run it. Many people become managers for being technically good and never learned how to give feedback or handle a difficult conversation.
Culture as a system
If the problem is keeping the ritual alive, the answer is to treat culture as a system, not as an event. A few practices:
- Explicit rhythm. Each ritual with a defined, visible frequency: a 1:1 every two weeks, a monthly feedback cycle, a review every six months.
- Light record-keeping. What was agreed gets written down somewhere both leader and team member can see.
- Reminders and visibility. Who hasn't talked to their team in a long time? Who has never received feedback?
- Support for the leader. Scripts, suggested questions and examples help people who are still learning to run these conversations.
- Health metrics, not surveillance. Track whether the rituals are happening, not what's said in them.
None of this needs a sophisticated tool to get started: a spreadsheet with the rhythm, the owners and a calendar reminder is already better than a wall poster. What matters is that the ritual happens.
Summary
Values say where the company wants to go. Rituals are the road. If you want to change the culture, don't rewrite the values: pick two or three rituals, set the rhythm, create a way to remember and to record, and protect those moments from urgency. Culture is what repeats.
Murilo Anzini
Hands-on writing on engineering, product, data and marketing for people who want to understand, and build, the whole journey of a product.
Discovery in one week: from problem to testable prototype
Discovery doesn't have to be a three-month project. A five-day plan to go from a vague idea to a prototype validated with real users, before writing any production code.
AI in the product without the hype: where an assistant really helps the user
Putting a chat on every screen is not an AI strategy. A way to decide where AI creates real value in the product, how to design the experience and which privacy safeguards belong in from day one.