"Culture eats strategy for breakfast."... Peter Drucker
You can have the best strategic plan in the world, the best processes, and the best tooling. If your culture is broken, none of it will save you. Culture is the operating system of the company. When the operating system is corrupted, every application running on top of it eventually crashes.
Warning signs of a sabotaging culture
1. Fear in the room
When people only say what leadership wants to hear, the organization is flying blind. Healthy disagreement is a sign of trust, not insubordination.
2. Blame always finds a target
When something breaks, the first question is "who did this?" instead of "what in our system allowed this to happen?". A blame culture kills innovation and encourages people to hide problems.
3. Heroes are required to survive
If the business only runs because one or two people pull off miracles every week, that is not high performance... it is fragility disguised as dedication.
4. Processes exist only on paper
There are certifications, playbooks, and internal wikis, yet nobody follows them in practice. Processes are treated as decoration rather than how work actually gets done.
Signs of a culture that sustains growth
1. People make honest mistakes and keep their jobs
Gross negligence has consequences, of course. But honest mistakes made by people trying to move the business forward are protected and turned into organizational learning, not punished.
2. Feedback flows in every direction
Not just top-down, but bottom-up and peer-to-peer. Feedback is treated as a calibration tool, not a weapon.
3. Decisions are explained
Even unpopular decisions are communicated with clear context. Transparency builds trust; silence breeds cynicism.
4. People stay (and bring their peers)
The simplest test of culture is straightforward: would your team recommend working here to people they respect? If the answer is no, something fundamental is broken.
How do you change culture?
Culture does not change with a town hall speech or a new slide deck. It changes through example, consistency, and the courage to confront behaviors that contradict your stated values.
If you are a leader, your real culture is defined by what you tolerate. It is not what is painted on the office wall. It is what happens when nobody is watching.
Westrum’s Typology: Pathological, Bureaucratic, or Generative?
Sociologist Ron Westrum, whose research forms the cultural backbone of the DORA State of DevOps studies, demonstrated that organizational cultures fall into three distinct patterns based on how they process information, risk, and failure:
| Cultural Dimension | Pathological (Power-Oriented) | Bureaucratic (Rule-Oriented) | Generative (Performance-Oriented) |
|---|---|---|---|
| Information Flow | Hoarded for personal political leverage | Filtered through rigid departmental silos | Shared openly to solve the mission |
| Messengers of Bad News | Shot / punished when raising risks | Ignored or buried in committee tickets | Trained and rewarded for early detection |
| Response to Production Failure | Scapegoating and firing an individual | Writing a new 20-page compliance rule | Root-cause architectural inquiry |
| Cross-Department Collaboration | Threatened and adversarial | Allowed only via formal sign-off | High-trust, direct problem-solving |
How to Turn a Sabotaging Culture Around in 90 Days
You cannot fix a sabotaging culture by hiring a branding agency to rewrite your company values. Cultural turnarounds happen through three visible leadership actions:
- Kill the sacred cows: Take one widely known point of bureaucratic hypocrisy, such as a weekly status meeting that wastes twenty people’s time or a chronic architectural bottleneck everyone complains about, and fix it in Week 1.
- Model public vulnerability: When the CTO or VP of Engineering openly says in an all-hands meeting, "I made the wrong call on that Q1 priority, here is what the data showed, and here is how we are adjusting," it gives the entire organization permission to be honest about facts.
- Align promotions with real delivery and collaboration: Make it unmistakable that advancing to Senior or Staff levels requires elevating the team’s reliability and business impact, never hoarding knowledge.
Good ideas keep the conversation going.
Share this article or publish the visual deck to your Stories and Feed.

Cesar Zanis
15+ years leading software architecture, database performance, FinOps, and applied AI across enterprise operations. Built and scaled an engineering organization from zero to 20+ developers.
Enjoyed this article?
I publish practical analyses on software architecture, FinOps, data, AI, management, and economics directly on LinkedIn.
Continue Reading
Take this analysis further with data and sources
All visual cards of this article are ready above to share on your Stories, Feed, WhatsApp, or LinkedIn with full sources.



