The Model
In the 1980s and 1990s, sociologist Ron Westrum studied how organizations in high-stakes industries — aviation, healthcare, nuclear power — handled safety-critical information. He observed that the way an organization treats information is a direct reflection of its culture, and that this information-handling behavior predicts safety outcomes. His typology was later adopted by the DevOps research community and is now a core framework in the State of DevOps Reports.
Westrum identified three organizational culture types, defined not by their stated values but by their actual behavior around information.
Type 1: Pathological (Power-Oriented)
The primary goal in a pathological organization is personal power and survival. Information is a political resource — hoarded, weaponized, or suppressed depending on what serves the individual's position.
| Dimension | Behavior |
|---|---|
| Information flow | Hoarded or used as leverage |
| Failure response | Covered up; blame assigned |
| Messenger treatment | Punished ("shot") |
| Collaboration | Actively discouraged; turf wars |
| Primary goal | Personal power and glory |
A pathological culture is not necessarily malicious. It often emerges from environments where individuals have been repeatedly punished for transparency, so self-protection becomes rational. The culture is a rational response to a broken incentive system.
Type 2: Bureaucratic (Rule-Oriented)
The primary goal in a bureaucratic organization is following the rules and protecting the department. Information flows, but only through official channels and only when procedures require it.
| Dimension | Behavior |
|---|---|
| Information flow | Restricted to official channels |
| Failure response | Justice sought ("who broke the rule?") |
| Messenger treatment | Ignored or tolerated |
| Collaboration | Modest; only when procedures mandate it |
| Primary goal | Departmental protection and rule compliance |
Bureaucratic cultures are not inherently bad — rules and procedures exist for good reasons. The failure mode is when the rules become the goal rather than the means. A team that won't deploy a critical security patch without a three-week change approval process because "that's the procedure" is exhibiting bureaucratic dysfunction.
Type 3: Generative (Performance-Oriented)
The primary goal in a generative organization is the mission — getting the right outcome. Information flows freely to wherever it is needed, regardless of hierarchy.
| Dimension | Behavior |
|---|---|
| Information flow | Actively shared; reaches where needed |
| Failure response | Inquiry; treated as a learning opportunity |
| Messenger treatment | Trained and thanked |
| Collaboration | High; cross-functional by default |
| Primary goal | Mission success and organizational performance |
Key Point: The DORA research consistently shows that teams in generative cultures have significantly better software delivery performance — higher deployment frequency, lower change failure rates, faster recovery from incidents — than teams in pathological or bureaucratic cultures. The culture type is not just a "vibe." It is a leading indicator of system reliability.
A common staff-level interview question is: "How do you know what kind of culture you're walking into?" The Westrum framework gives you a concrete diagnostic: ask how the organization handles bad news. Specifically: "Tell me about the last time a junior engineer raised a concern that turned out to be correct. What happened to them?" The answer tells you almost everything about where on the Westrum spectrum the organization sits.