What You Do Is Who You Are: How to Create Your Business Culture
Source: https://www.harpercollins.com/products/what-you-do-is-who-you-are-ben-horowitz ↗
Horowitz's second book is about culture — but told through unusual case studies: Toussaint Louverture's slave revolution in Haiti, the samurai bushido code, Shaka Senghor's prison gang, and Genghis Khan's meritocratic army.
The argument is that culture is not what you say or what you believe but what you do repeatedly, and that programming it requires the same kind of specific, deliberate action as programming software.
For product direction the most useful idea is the framing of culture as a code with bugs — misbehaviour in an organisation is usually a cultural bug, not a people problem, and debugging it requires looking at the system rather than at the individual.
Read alongside McCord's Powerful and Benedict's Patterns of Culture for complementary approaches to the same question.
Horowitz writes with the same honesty as in The Hard Thing; the historical examples are its distinctive feature.
Central argument
Horowitz argues that organizational culture is not defined by stated values or beliefs but by repeated, specific actions — and that creating it requires the same deliberate, systematic design as writing software. Drawing on radical historical case studies (Toussaint Louverture, the bushido code, Genghis Khan's army, Shaka Senghor's prison gang), he shows that durable cultures are engineered through precise behavioral codes, not through aspiration or rhetoric. The central finding is that misbehavior in organizations is typically a cultural bug — a systemic failure — rather than an individual character flaw, and that leaders must debug the system, not just remove the person.
Critique
The historical case studies are the book's most distinctive feature but also its most contested: drawing leadership lessons from a prison gang or a genocidal conqueror risks stripping atrocities of their moral weight in service of a management thesis, and Horowitz never fully reckons with how context-dependent those cultures were — they were forged under extreme coercion and existential threat, conditions that do not translate cleanly to knowledge-work organizations. A thoughtful reader might also note that the 'culture as code' metaphor, while appealing to a Silicon Valley audience, understates the emergent and contested nature of culture: unlike software, organizational culture is written simultaneously by everyone, not just by those at the top.
Why it matters for product
For a CPO, the 'cultural bug' framing is directly actionable: when a product team consistently skips user research, ships without instrumentation, or treats discovery as optional, the instinct is to address the individuals involved — but Horowitz's logic points instead to the rituals, incentives, and decisions that made that behavior rational in the first place. This reframes organizational design questions — how ceremonies are run, what gets celebrated in a retrospective, which metrics leaders actually review — as the real levers of product culture, not hiring profiles or value statements.