Culture is not the poster in your reception. It's not the values page on your intranet, or the five words in your onboarding deck. Culture is what your people actually do when you're not in the room — and what they do is determined by the systems you built, not the sentences you wrote. I've spent two decades watching leaders confuse the two. They declare a culture. Then they're baffled when the organisation quietly ignores it.
Culture is infrastructure. Not aspiration. Not vibe. Infrastructure. It's designed to tolerances. It's maintained. It's tested. And when it's built well, it runs without you standing over it. That single shift — from declaring culture to architecting it — is the difference between a values statement nobody follows and an organisation that does the right thing consistently, whether the boss is watching or not.
Culture is what people do when you aren't in the room. Architecture is what makes them do the right thing consistently, whether you are or not.Stuart Andrews
Why I Treat Culture as Infrastructure, Not Values
Think about how you'd judge a bridge. You wouldn't paint a slogan about strength on the side and call it sound. You'd check the load it carries, the tolerances it was built to, the maintenance schedule, the failure points. Culture deserves the same rigour — and almost never gets it. We treat behaviour as a mood to be inspired rather than a system to be engineered. So we run another workshop, refresh the deck, and change nothing about what the organisation actually rewards.
Infrastructure has properties a values statement never will. It's designed, not declared. It's built to specific tolerances, so you know what it can and can't hold. It's maintained, tested and upgraded rather than launched once and forgotten. And critically — it works without constant human intervention. That last property is the whole game. If your culture only holds when you're personally present to enforce it, you don't have a culture. You have a performance that ends when you leave the building.
The Culture-as-Infrastructure Lens
- Rituals carry the message, not the memo: What you do repeatedly — how meetings open, how decisions get reviewed, how failure is discussed — teaches the organisation what actually matters. Rituals are load-bearing. Change the ritual and you change the belief far faster than any all-hands speech.
- Decision rights are the real org chart: Who gets consulted, who gets informed, how fast a decision can move, who can override whom. This invisible wiring shapes behaviour more than any title. Slow, over-approved decisions manufacture a risk-averse culture no values page can undo.
- Recognition architecture defines your real values: What you visibly reward, promote and tolerate is your culture — stated or not. If you celebrate flawless execution and quietly punish honest failure, you have a fear culture, whatever the poster says. People read the reward system, not the wall.
- Development investment reveals who you believe in: Who receives growth resources, and for what, tells the organisation who it considers valuable. Invest capability broadly and you build learning and safety. Hoard it for a chosen few and you engineer politics, whatever your slogans claim.
- Accountability holds the standard when you're absent: Culture without accountability is just aspiration; accountability without culture is just fear. The infrastructure must hold clear standards and genuine safety in tension — so the right behaviour persists when no leader is in the room to insist on it.
Culture Is a Leadership Output, Not an HR Function
Let me be blunt about something the sector still gets wrong. Culture is not owned by HR. It's not a programme, a campaign or an engagement survey. It's an output of leadership decisions — every one of them, at every level. When a leader chooses who to promote, which failure to punish, which shortcut to tolerate, they are laying cultural infrastructure. They're doing it whether they intend to or not. The only question is whether they're doing it deliberately or by accident.
This is why I refuse to let executives outsource culture. You can delegate the roll-out. You cannot delegate the design, because the design is written in your own behaviour. If the CEO claims to value collaboration while making unilateral calls, the organisation learns that collaboration is decorative. No HR intervention survives contact with a leader whose actions contradict the stated culture. The infrastructure always tells the truth.
- Map the decision architecture — Work out who makes what decisions, how fast, and by what criteria. Decision patterns are the clearest signal of your actual values, regardless of the stated ones. If everything routes to one desk, your real value is control — not the enablement on the wall.
- Audit the recognition system — Ask what gets celebrated, what gets promoted, and what gets quietly tolerated. Those three answers describe your true culture more accurately than any values statement. Recognition is the most honest document your organisation produces.
- Design the development investment — Decide who receives development resources and for what capability. Organisations that invest broadly — not only in a high-potential elite — build cultures of safety and continuous learning. Where you spend the growth budget is where you place your real bets.
- Build accountability architecture — Hold performance standards and psychological safety in the same structure. Culture without accountability drifts into wishful thinking; accountability without safety curdles into fear. The infrastructure has to carry both loads at once, deliberately.
The Gap Between Stated Values and Real Behaviour
I worked with a global financial services firm that had spent eighteen months building a culture deck around innovation, psychological safety and calculated risk-taking. The values were everywhere. So I sat with their senior team and asked one question: who in this room has failed publicly and been promoted? Silence. Not a single hand. The deck said one thing. The infrastructure said another. And people always follow the infrastructure.
That gap is not a communication problem. It's an architecture problem, and the two require completely different fixes. You cannot declare a culture of psychological safety while your recognition system rewards only flawless execution. You cannot claim to prize innovation while your decision process demands seven approvals and three steering committees. The artefacts and the wiring are in open conflict — and the wiring wins every time, quietly, without anyone announcing the result.
So the fix is never another workshop. It's ruthless alignment between what you say matters and what your systems actually reward, punish and enable. That work starts with the leaders auditing their own behaviour before anyone else's, because if the person at the top contradicts the stated culture, no downstream intervention will hold. Alignment is not a slogan exercise. It's structural repair.
The Culture Audit Question: For each value you claim, ask three questions. What specific behaviour does our recognition system reward? What does it punish? What does it ignore? If the answers don't match the value, your infrastructure is broken — and the only people confused about it are usually in the leadership team.
How Decision Rights Quietly Engineer Culture
Decision rights are the most underrated piece of cultural infrastructure I know. Not formal authority — that's the easy, visible part. I mean the harder questions. Who gets consulted before a call is made? Who gets informed after? How fast can a decision actually move? What criteria genuinely matter, and who can override whom? Answer those honestly and you've described your real culture with more precision than any survey.
I watched a business of 2,400 people run on a single decision right: every operational call above fifty thousand pounds needed the COO's sign-off. On paper, control. In practice, paralysis. Managers stopped proposing. The COO became a bottleneck. Decisions that should have taken two weeks took three months, and the organisation missed real market shifts. Nobody had declared a dependent, risk-averse culture. The infrastructure had built one anyway, silently, one approval at a time.
When we redesigned it, we didn't strip out oversight — we clarified it. Regional managers could approve operational investment up to a defined ceiling if it met three criteria: customer impact, risk mitigation and capability alignment. The COO reviewed decisions quarterly rather than gatekeeping each one. Behaviour changed fast, and it changed for a structural reason. We hadn't given a speech about enablement. We'd made enabled behaviour the path of least resistance. That is what designing culture actually looks like.
- Decision velocity shapes psychological safety — slow, over-approved decisions signal distrust and breed risk aversion
- Consultation patterns reveal who really holds influence, regardless of title or the published org chart
- Override authority that's never used is pure overhead; override authority used constantly signals broken architecture upstream
- Transparent decision criteria reduce politics and build trust, while ambiguous criteria reliably breed gamesmanship
- Decisions pushed to the wrong level create bottlenecks and accountability gaps at the same time
- Documented, asynchronously reviewed decisions scale far better than meeting-dependent, synchronous ones
The Compounding Cost of Culture You Never Designed
Most leaders badly underestimate the cost of cultural misalignment, because they look for it in the wrong ledger. It isn't only turnover, though that's real. It isn't only engagement scores, though those sag. The real cost is the compounding loss of capability and speed. When your stated culture contradicts your infrastructure, your smartest people spend their energy navigating the gap instead of doing the work. They learn to read the room, play the game and protect themselves — and every hour spent on that is an hour stolen from the actual mission.
That drain compounds quietly, which is exactly why it's so dangerous. No single moment announces it. There's no line on the P&L that reads 'capability lost to a culture we declared but never built.' Yet it shows up everywhere — in the initiative that stalls for reasons nobody can quite name, the talented person who disengages long before they resign, the decision that sits unowned for a quarter because owning it feels unsafe. Each incident looks isolated. In truth they share a single root cause, and it lives in your infrastructure. Left unaddressed, that root cause becomes the ceiling on everything else you're trying to build, no matter how good your strategy is. You simply cannot out-strategise infrastructure that's working against you.
Design the Culture, or Inherit the One You Didn't
So here's where I land, and it's the distinction I'd want you to take away. Every organisation already has cultural infrastructure. The only choice you have is whether you designed it or inherited it by accident. There is no third option where culture floats free of your systems, sustained by good intentions and an inspiring poster. Behaviour follows the wiring, always.
That reframe is liberating once you accept it. If culture is designed, then culture is fixable — not through another values launch, but through deliberate changes to rituals, decision rights, recognition and development. You stop hoping people will absorb the values and start building the systems that make the right behaviour the easy behaviour. That's engineering, not evangelism, and engineering you can actually control.
My challenge to every leader I work with is simple, and it's uncomfortable by design. Stop declaring the culture you want and start auditing the culture your infrastructure is quietly producing right now. Look hard at what you reward, who you promote, how fast decisions actually move, and who you choose to invest in. That is your real culture, written in a language your people already read fluently, long before they've finished reading the values on the wall. Change the infrastructure and the behaviour follows within months. Leave the wiring untouched and no amount of declaration, repetition or genuine sincerity will save you. The systems you tolerate are the culture you have.
Culture isn't something you have. It's something your leadership system produces, reliably, every single day, whether you designed it to or not. Treat it as infrastructure and you can build it on purpose, to the tolerances your ambition actually requires. Treat it as a values poster and you'll spend the rest of your career wondering why the wall and the workplace never quite agree — and why the culture keeps reverting to something you never chose.