Why I Am Writing This
Most founders think about culture as something they will get to once the early chaos settles. The product first. The team later. The culture eventually. The problem is that by the time they get to it, the culture has already formed. It just formed without them.
This week: What culture actually is, why it shapes the company more than any strategy does, and what founders can do intentionally to build one that lasts.
A founder I worked with had a team of twelve people who all showed up on time, hit their targets, and never caused any trouble. She told me she had no culture problems. What she actually had was a team that had stopped thinking.
Nobody was taking initiative. Nobody was raising problems early. Nobody was doing anything beyond what was explicitly asked of them. The team was functional and the culture was broken. The absence of visible conflict is not the same as the presence of trust.
What she had built, without meaning to, was a culture of compliance. Everyone was waiting to be told what to do because doing more than that felt risky. That feeling did not come from nowhere. It came from hundreds of small signals she had sent over two years, without realising it, about what was safe and what was not.
Culture is not the values on the wall. It is not the team offsite or the Friday lunch. It is the answer to one question, asked by every person in your company, every single day: what happens here when things go wrong?
If the answer is "someone gets blamed," people stop taking risks. If the answer is "problems get buried," people stop raising them. If the answer is "we figure it out together," people start owning outcomes. Culture is what your team learns is true about this place, through experience, not through what you tell them.
You cannot install culture. You can only model it, consistently, until the people around you start reproducing it without being asked.
That takes longer than most founders expect. And it starts earlier than most founders realise. The culture of a company is set in the first ten hires, the first ten crises, and the first ten decisions the founder makes when no one is watching.
There was a period at VisionVoyage when I was doing a lot of things myself that I should have been delegating. I told myself it was because the quality had to be right. What I was actually doing was signalling to everyone around me that their judgment could not be trusted without my approval.
The culture that created was subtle but real. People started checking in more. Decisions that should have been made without me were being brought to me. The energy that should have been going into the work was going into managing my expectations instead.
I had built a culture of dependency without intending to. And the only way to change it was to change my own behaviour first, not to give a speech about empowerment.
Three Things That Shape Culture
1
Who you hire and who you keep
Every hire is a cultural statement. The person you bring in tells the team what you value. The person you keep despite poor behaviour tells them what you will tolerate. Zoho has spent decades hiring based on potential and curiosity over pedigree, training people in-house, and building a workforce that stays. That is a cultural choice made repeatedly, not once. The team watches every hiring and firing decision closely. They are reading what it means about what is valued here.
2
How you handle failure
The single clearest signal a founder sends about culture is what happens when something goes wrong. If you look for someone to blame, people learn to hide problems. If you ask what can be learned, people learn to surface them early. This is not about being soft on accountability. It is about understanding that the culture you build around failure determines how much honest information you will ever get from your team.
3
What you do when it is inconvenient
Anyone can model good values when it is easy. Culture is set in the moments when doing the right thing costs something. When you are under pressure and you still give someone honest feedback instead of the comfortable version. When you are behind on a deadline and you still make time for the person who needs you. The team is watching those moments most carefully. What you do there is what they learn is really true about this place.
Sridhar Vembu built Zoho into a global software company with over 15,000 employees without ever taking outside funding or hiring primarily from elite institutions. Only 5% of Zoho's founders and senior hires come from tier-one institutes like IIT or IIM. Instead, Zoho built its own schools, trained people from smaller towns and non-traditional backgrounds, and created a culture where learning and contribution mattered more than credentials. That is not a hiring policy. It is a deeply held belief about what people are worth, expressed consistently over decades. The company that resulted reflects that belief at every level.
Culture compounds the same way habits do. A small consistent signal, repeated over years, becomes the invisible architecture that either frees your team or constrains them.
This Week's Reflection
What is your team learning is true about your company, through experience rather than what you have told them? And if you asked your five most honest team members that question, would their answer match yours?
The product can be rebuilt. The strategy can be pivoted. The culture, once it has formed, is the hardest thing in a company to change. Which is also why it is the most important thing to build with intention, from the beginning, before it builds itself.
Start with the question your team is already asking every day. What happens here when things go wrong? Make sure you know the answer. And make sure it is the one you actually want.
See you Wednesday.
Riddhi
Founder, VisionVoyage
Work Directly With Riddhi
Ready to go deeper than a newsletter?
Book a Discovery Call
₹99 for professionals · ₹499 for founders & senior leaders
