Structural vs. Cultural Root Cause Analysis¶

Why It Matters¶

Faced with organizational dysfunction, the default diagnosis is often cultural: "people don't care enough," "we lack accountability," "the culture is risk-averse," "we need to shift mindsets." Culture change initiatives are then launched: new values statements, leadership speeches, training programs. These typically fail because the problem wasn't cultural—it was structural. The "risk-averse culture" is actually a rational response to incentive structures that punish failures. The "lack of accountability" stems from unclear decision rights. The "siloed mindset" reflects information systems that don't cross boundaries. Attempting cultural change without structural change creates cynicism when people are exhorted to behave differently while incentives remain unchanged.

The Key Move¶

When diagnosing a problem attributed to culture, first check for structural explanations: What are the actual incentives? What information is available? What constraints exist? If you changed structures (incentives, metrics, information systems, decision rights) to support the desired behavior, would behavior change without any cultural intervention? If yes, it's structural. Culture change should be a last resort after structural fixes are exhausted. When culture change is necessary, it must be accompanied by structural alignment—you can't sustainably change culture while structures incentivize the old one.

Classic Application¶

Gerstner's IBM turnaround (1990s). When Gerstner became CEO, IBM was characterized as having a culture of arrogance, insularity, and mainframe obsession. The default diagnosis: cultural problem requiring cultural transformation. Gerstner's insight: the culture was a rational response to structural incentives. IBM's compensation tied to mainframe revenue, promotion depended on defending existing businesses, information systems reported by product line reinforcing silos, and metrics measured internal processes not customer outcomes. Gerstner restructured: changed compensation to reward customer satisfaction, reorganized around customer industries not product lines, replaced internal metrics with market metrics. Culture shifted because structures changed—people responded rationally to new incentives. Had he only attempted cultural exhortation while keeping old structures, nothing would have changed.

Surprising Application¶

"Not Invented Here" syndrome in engineering teams. Teams are reluctant to use external libraries, frameworks, or solutions, preferring to build custom solutions internally. This is often diagnosed as cultural problem: engineers' arrogance or desire to solve interesting problems. Structural analysis reveals: career advancement requires demonstrable individual technical contributions; using external solutions doesn't generate promotion-worthy artifacts; failures of external dependencies are highly visible while failures of internal systems are contained. The incentive structure rewards building over reusing. Addressing this structurally: give credit for successful integration of external solutions, measure total delivery speed not just individual technical complexity, explicitly penalize "not invented here" decisions in architecture reviews. Culture shifts when structure changes.

Failure Modes¶

Assuming everything is structural—some dysfunction does stem from genuine cultural assumptions and tacit norms not explained by incentives. Using "it's structural" to avoid the hard work of culture change when it's actually necessary. Ignoring that structures and culture coevolve—changing structures creates temporary culture-structure misalignment that can undermine change. Treating structures as easy to change—deeply embedded structures (especially informal ones) can be as resistant as culture. Over-engineering structural solutions when simple cultural conversation would suffice.

Go Deeper¶

Gerstner, Who Says Elephants Can't Dance? (2003); Sull & Eisenhardt, "Simple Rules for a Complex World," Harvard Business Review 90(9), 2012.