The Craftsman
Source: https://yalebooks.yale.edu/book/9780300151190/craftsman/ ↗
Not a technology book, but its central thesis resonates deeply: good work is born from making, not from planning.
The craftsman learns by doing, develops judgement through practice, and their knowledge is inseparable from their experience.
Sennett connects with Hayek (the tacit knowledge that cannot be centralised) and with the "just for fun" ethos (experimentation as method, not slogan).
When AI compresses the distance between idea and execution, the craftsman's ethos becomes more relevant, not less.
Central argument
Sennett argues that craftsmanship — the drive to do a job well for its own sake — is a fundamental human capacity that generates a specific kind of knowledge inseparable from physical and repeated practice. He challenges the Enlightenment split between head and hand, contending that skilled practitioners do not first think and then execute; rather, thinking and doing are fused through thousands of hours of engagement with resistant material. The craftsman's judgment, taste, and problem-solving ability cannot be extracted into a procedure or a plan — they are embodied and accumulated, not transmitted.
Critique
Sennett's account is most persuasive when describing individual mastery in stable, bounded domains — the luthier, the glassblower, the medieval mason — and it struggles to account for how craftsmanship scales or survives coordination across large, distributed teams. A CPO might reasonably ask: what happens to the craftsman's ethos when the 'material' is a sociotechnical system shaped by hundreds of people, none of whom can hold the whole in their hands? The book valorises depth of practice without fully confronting the structural conditions — economic precarity, deskilling, platform fragmentation — that routinely make sustained craft engagement impossible.
Why it matters for product
For a product leader, Sennett's core insight is a direct challenge to the dominance of process over practice: if judgment is built through making, then a team insulated from real execution — through excessive abstraction, proxy metrics, or layers of hand-offs — is a team that cannot develop genuine product intuition. This reframes hiring and team design: craft-level product thinking is cultivated through repeated, close contact with the problem, not through frameworks. It also sharpens the curator's point about AI — when tools collapse the distance between intent and output, the differentiator is no longer execution speed but the quality of judgment brought to the prompt, the prototype, the decision.