Framing any organizational initiative as “culture change” is a show-stopper. It lets you see yourself as a visionary and everyone else as obdurate idiots. It provides an abstract scapegoat when the initiative fails. And it replaces hard, context-specific analysis with lazy thinking. The phrase “culture change” needs to be eliminated from your vocabulary and replaced with actual diagnosis.
Simple Picture
You cannot change the weather by arguing with it. You can move to a different climate, build shelter, or wait for the seasons to change. Organizations work the same way: the culture is the weather. It is the emergent result of who is there, what they are incentivized to do, and what they have survived together. Telling the weather to be different is not a strategy.
Why Culture Change Is Nearly Impossible
The only real process for cultural shift is Darwinian natural selection — displacement of a central culture by a marginal one. The odds against this happening in a healthy business are astronomical. Slightly better odds exist in companies facing strategic crises that require new business models — but even then, you must argue both that the new model demands a different culture AND that your initiative enables that culture.
This is the bad Nash equilibrium applied to culture: everyone may agree the current culture is suboptimal, but no individual can unilaterally change it, and coordination to change simultaneously is too hard. The Dead Sea Effect adds the biological mechanism: cultural shift happens through generational turnover, not through convincing the current inhabitants. The people who don’t fit the culture leave. The people who fit it stay and reproduce it. Changing the culture means changing who stays — which is a hiring and retention problem, not a messaging problem.
Five Ways Out of the Trap
1. The Churn Argument. Change happens through turnover, not persuasion. The naysayers will not be converted. They will be replaced — slowly, through attrition, as the organization hires differently and the old guard ages out.
2. Don’t blame culture for UX issues. If new tools or processes are not simple and convenient enough, that is an engineering problem, not a culture one. The Milo Criterion applies: if adoption fails, the product exceeded the user’s absorption rate. Fix the product, not the people.
3. Don’t blame culture for misaligned incentives. Figure out who benefits from the status quo and who pays its costs. Align incentives accordingly. This is the Theory of Constraints applied to change: find the actual bottleneck (usually an incentive structure), not the convenient scapegoat (culture).
4. Ponder what “culture” actually means. Cultures are about social connections and shared values. Competing for the right hires helps but has limits. If the culture you need is truly incompatible with the one you have, the honest answer may be: find a startup that already has it. The problem definition matters: “we need culture change” is almost always the wrong framing of a problem that has a more specific, more actionable description.
5. “Culture change” signals victim mentality. Smart, productive people hear the phrase and classify you as a hand-wringer. The feedback pipe closes. Your credibility drops. You lose the very influence you would need to produce the change you are advocating.
Dimwit / Midwit / Better Take
The dimwit take is “culture eats strategy for breakfast — you have to change the culture first.”
The midwit take is “culture change requires top-down commitment and a clear transformation roadmap.”
The better take is that “culture change” is not a thing you do — it is a thing that happens as a side effect of changing who is there, what they are incentivized to do, and what tools they have. Every time you are tempted to say “culture change,” substitute the specific mechanism: is it a hiring problem? An incentive problem? A tooling problem? A trust problem? If you cannot name the specific mechanism, you do not understand the problem — you are using “culture” as a label for your confusion.
Main Payoff
The deepest insight: retooling costs money, and gatekeepers protect rivers of money, not systems. Before trying to replace a legacy system or process, add value to the legacy first. Build credibility within the existing culture before attempting to change it. The importance drive operates here: the people who built the current culture have their identity invested in it. Displacing their culture without acknowledging their contribution is an attack on their importance — and the defensive response will be swift, total, and disguised as reasonable objections.
References:
- Venkatesh Rao, There Is No Such Thing as Culture Change, Ribbonfarm