Why culture is not a set of values on a wall, but a set of decisions made under pressure
You don't build culture through retreats and mission statements. You build it through the decisions you make in the moments when nobody would blame you for deciding differently.
There is a sentence I have used once in a serious conversation with a team member at Futad. I’ve never had to use it twice with the same person. It works not because it is dramatic, but because it is precise: nobody here gets fired for making mistakes. Only for values.
That sentence is the foundation of how I lead. And it took me years of building to understand why it matters more than any hiring criterion, any performance framework, or any company values document ever written.
The Difference Between Mistakes and Values
Mistakes are the operating cost of doing serious work. A campaign that underperforms. An installation that runs late. A proposal that misreads the brief. These are events. They have causes, consequences, and — most importantly — they teach something if you allow them to.
A leader who punishes mistakes trains a team to hide them. Hidden mistakes compound. The cost of a mistake you catch early is a fraction of the cost of one you discover when the client does. So the organisational incentive should always be toward disclosure, not concealment. That requires making it safe to be wrong — and making it explicit that being wrong is not the same as being a problem.
Values violations are different. They are not events. They are signals about who a person is under pressure. The team member who cuts a corner and doesn’t disclose it. The one who shifts the blame before examining the cause. The one who treats a client interaction as an inconvenience rather than a responsibility. These are not mistakes. They are choices — and they tell you something that no skills assessment ever will.
Mistakes tell you what someone doesn’t know yet. Values violations tell you who they become when nobody is watching.
Why Doctrine Over Rules
Most management systems try to solve culture through rules. Employee handbooks. Code-of-conduct documents. HR policies. These are not useless — they create a floor. But a floor is not a culture. A culture is what happens above the floor, in the grey areas that no policy anticipated, when the leader is not in the room and the team has to decide.
Doctrine is different from rules. Rules prescribe behaviour in known situations. Doctrine provides the logic that allows good decisions to be made in situations the rules never covered. A team that has internalised doctrine can operate independently. A team that has only memorised rules stops functioning the moment reality diverges from the rulebook.
At Futad, I defined doctrine once. I expected internalisation, not reminders. The test of whether someone has internalised it is what they do when the incentive to violate it is real — when a client is pushing, a deadline is closing, or the path of least resistance involves a compromise.
I didn’t intervene often. But I observed constantly. And when I did intervene, it was precise and final. Not as punishment. As calibration.
The Decentralised Execution Principle
There is a management temptation, particularly for founders, to hold the reins tightly. To be the decision-maker at every junction. To build a business where things only move correctly when you are watching.
That is not a business. That is a personal services operation with employees. It has a hard ceiling — on scale, on quality, on the founder’s own capacity to think clearly at the strategic level when they are consumed by the operational one.
The architecture I built toward — deliberately, imperfectly, with ongoing iteration — is decentralised execution with centralised principles. Teams are empowered to make decisions. They are not empowered to make decisions that contradict the doctrine. The distinction is not subtle in practice. It becomes intuitive for people who have genuinely understood why the principles exist, not just what they are.
A team that understands why is more autonomous than a team that knows what. The why survives situations the what never anticipated.
What This Asks of the Leader
Doctrine leadership is harder than transactional management in one specific way: it requires the leader to embody the doctrine visibly, consistently, and especially under pressure. You cannot ask a team to hold a value that you are seen to negotiate when it becomes expensive.
The times I’ve been most closely watched — during live events under deadline pressure, in client confrontations where the commercial stakes were high, in internal moments where taking the easy path was genuinely available — were the times when the doctrine was either reinforced or quietly undermined. Teams notice both. They remember the second more than the first.
You don’t build culture through retreats and mission statements. You build it through the decisions you make in the moments when nobody would blame you for deciding differently.
More perspectives.
- Founder mindset · Leadership
The Investigator's Burden
What it costs to think deeply in a market that rewards speed — and how to carry it without breaking the business
- Founder mindset · Leadership · Strategy
Why I Call Myself a Builder-Philosopher — And Why That Label Matters
Build slowly. Think longer. Ship things that last.
- Founder mindset · Leadership
The Day I Realised I Wasn't Building a Company. I Was Building a Mirror.
There is a moment in every founder's journey that nobody prepares you for.