How to Build a Culture That Doesn't Depend on You

There is a specific kind of culture that feels powerful and turns out to be fragile: the culture that is entirely carried by the founder.

It is coherent while the founder is present. The founder models the behaviour, makes the decisions, signals what matters by what they pay attention to, corrects drift when they notice it. The team absorbs the norms by proximity. When the founder is in the room, the culture is real.

When the founder is not in the room — or when the company grows past the point where the founder can be in every room — the culture degrades. Not because the team changes. Because the transmission mechanism was the founder's presence, and that presence has finite bandwidth.

I have seen this pattern on both sides of my work. In executive search, I have seen companies where the culture of the founding team — excellent, careful, values-driven — did not survive the first generation of professional management because it was never encoded into anything that could transmit itself. In building Majhi Group and Majhi OS, I have had to confront the same question in my own work: what happens to this culture when I am not carrying it personally?

What culture actually is

Culture is not the values statement. It is not the culture deck. It is not the ping-pong table or the free lunch or the Glassdoor page.

Culture is the operating norms that govern behaviour in the moments that matter — when there is a conflict, when a decision is unclear, when quality is expensive, when speaking up is uncomfortable. What people actually do in those moments is the culture. What is written on the wall is the aspiration.

MIT Sloan research on organisational culture found that the strongest predictor of culture was not stated values but the pattern of behaviour in high-pressure situations — what leaders rewarded when reward was costly, what they tolerated when intolerance was uncomfortable, what they modelled when modelling was inconvenient. Culture is pressure-tested behaviour, not ambient behaviour.

This matters because it changes what "building a culture" actually requires. It requires designing systems that produce the right behaviour under pressure — not writing values statements that describe the right behaviour in easy conditions.

The founder dependency trap

Founder-dependent culture has a specific failure mode that is worth describing precisely.

The founder, in the early years, is the primary cultural signal. Their behaviour under pressure — how they respond to a difficult client, what they do when quality is expensive, how they handle a conflict between team members — is watched carefully and copied. The culture that forms is a reflection of the founder's actual operating norms, including the inconsistencies.

As the company grows, the founder's direct presence reaches fewer interactions. But the culture has not yet been encoded into anything that transmits itself independently. There is a lag — a phase where the culture appears to be working (because enough of the founding team carries it by osmosis) and then, unpredictably, stops working (because the new hires who joined after the founding team can't absorb what isn't being transmitted).

The failure is not usually visible until it is significant. A client who notices a different standard of work. A hire who behaves in ways inconsistent with what the founder intended but entirely consistent with what the organisation's systems rewarded. A decision made by a capable person using the wrong criteria because the criteria were never written down.

By the time the founder notices, the culture has already drifted.

Culture is the operating norms that govern behaviour in the moments that matter — when there is conflict, when a decision is unclear, when quality is expensive. What people do in those moments is the culture. What is written on the wall is the aspiration.

What transmission actually requires

The Jesuits built an organisation that has operated continuously for nearly 500 years across hundreds of countries and thousands of people. They did not do this by finding exceptional people. They did it by designing a transmission system.

The Jesuit formation process — the multi-year training that shapes a Jesuit before they are deployed into any operational role — is one of the most deliberate culture transmission systems ever built. It teaches the same decision frameworks, the same values hierarchy, the same approach to intellectual and moral reasoning across every cohort, in every country, in every century. The culture transmits because the transmission mechanism was designed as carefully as the culture itself.

Most organisations treat transmission as an afterthought. Onboarding is an introduction to the product and the org chart, not an education in how things actually work. Operating norms are assumed to be obvious or transmitted by proximity. The founding team's cultural knowledge is not codified before they disperse.

What transmission actually requires:

Operating principles with teeth. Not "we value quality" but "a search that does not meet these specific criteria does not advance to client presentation, regardless of timeline pressure." The specificity is the point. Vague principles require interpretation. Specific principles can be applied consistently without the founder in the room.

Explicit quality standards. What does good work look like in this organisation, specifically? Most organisations have a tacit answer to this question — the founder knows it when they see it — but not an explicit one. The gap between tacit and explicit is the gap between culture that transmits and culture that depends on the founder.

Onboarding that teaches the real norms. The first ninety days of a new hire's experience shapes their mental model of how this organisation works more than anything else they will encounter. If that onboarding teaches the product and ignores the operating norms, the new hire will infer the norms from the incentives they observe — which may or may not match the culture the founder intends.

A feedback infrastructure. Culture drifts silently. The founder cannot monitor every interaction. What they can design is a system that surfaces drift early: structured quality reviews, client feedback processes, candid retrospectives that make the gap between intended and actual behaviour visible before it becomes significant.

The Majhi Group version

Building Majhi Group as a retained search firm — rather than contingency — was a culture design decision before it was a business model decision.

The contingency model creates a culture of volume and speed because that is what its incentive structure rewards. The retained model creates the conditions for a culture of quality — but only if the operating systems are designed to reinforce quality at every decision point. The model creates the possibility. The systems make it real.

The quality gate in our search process — the criteria a candidate must meet before being presented to a client — is culture encoded into a system. It is not "the consultant's judgment." It is a written standard that any consultant can apply consistently and that any client can verify. The culture of quality that Majhi Group has is not carried by my personal presence in every search. It is carried by the system that makes quality the default, and makes deviation from it visible.

This took longer to build than a values statement. It took longer to maintain. And it is what makes the culture real rather than dependent on my attention.

Building it before you need it

The time to build the transmission mechanism is before the culture needs it — while the founding team still carries the norms by proximity and the organisation is small enough that the design is simple.

Most founders defer this because it feels premature. The culture seems to be working. The team is aligned. Formalising feels bureaucratic.

It feels premature until the day it doesn't work. And on that day, the culture has usually been drifting for longer than anyone realised.

Building from Odisha accelerated this for me. Without a local ecosystem of peers carrying similar norms, without a professional community that would socialise new hires into the right standards by proximity, the transmission system had to be explicit or it would not exist. The constraint was clarifying.

The culture you want is not the culture you describe. It is the culture your systems produce. The founder who understands this builds the systems. The one who doesn't performs the culture until they run out of bandwidth to perform it.

Sources

MIT Sloan Management Review — The Leader as Culture Manager

Harvard Business Review — Making Your Values Mean Something

HBR — The Culture Factor