What Makes a Strong Product Culture?
Source: https://www.bringthedonuts.com/essays/what-makes-a-strong-product-culture/ ↗
Norton's essay on product culture is a compressed argument about what distinguishes strong product organisations from the rest — not the rituals or the frameworks, but the shared sense of what good product work looks like.
The piece is useful because Norton is one of the few contemporary voices willing to argue that product is a craft rather than a process, and that culture is what keeps craft alive.
For product direction the essay is a short diagnostic: most organisations that describe themselves as "product-led" are using the words without the underlying culture, and Norton's test is sharper than most.
Pair with Cagan's Establishing a True Product Culture for a complementary take.
Central argument
Norton argues that strong product culture is defined not by ceremonies, frameworks, or org charts, but by a shared, internalized sense of what good product work looks like — what he frames as craft. The central thesis is that organisations claiming to be 'product-led' typically have the vocabulary without the underlying values, and that the difference between genuine product culture and its imitation lies in whether people at every level can recognise and insist on quality without being told to. Culture, for Norton, is the mechanism that sustains craft when no process is watching.
Critique
Norton's framing of product as craft, while compelling, risks romanticising individual and team judgment in ways that underweight structural and systemic constraints. A thoughtful objection is that 'shared sense of what good looks like' is easier to cultivate in well-resourced, relatively autonomous product organisations than in the enterprise or regulated-industry contexts where most product leaders actually operate — where incentive structures, procurement cycles, and risk governance actively erode the conditions Norton assumes. The essay diagnoses culture without fully accounting for the political economy that produces or destroys it.
Why it matters for product
For a CPO, Norton's argument reframes a common diagnostic failure: when delivery is slow or quality is inconsistent, the instinct is to fix process, but Norton's test asks instead whether the organisation has a shared and enforceable standard of good — which is a hiring, onboarding, and leadership modelling problem, not a Jira configuration problem. This is directly relevant to decisions about team structure and senior IC career paths, where the question is whether you are building conditions for craft or just adding coordination layers that substitute for it.