The Evolution of Useful Things: How Everyday Artifacts — From Forks and Pins to Paper Clips and Zippers — Came to Be as They Are
Source: https://www.penguinrandomhouse.com/books/163057/the-evolution-of-useful-things-by-henry-petroski/ ↗
Petroski dismantles the myth that form follows function by tracing the actual histories of forks, paperclips, zippers, and other everyday objects.
What he finds is that design evolves not from function but from failure — each generation of an artifact is a response to the shortcomings of the previous one, not a direct expression of purpose.
The fork did not emerge because someone analyzed the function of eating; it emerged because knives were inadequate for certain foods, and then forks themselves were refined through centuries of dissatisfaction with their own limitations.
The implication for product development is profound: innovation is not invention from first principles but iterative correction driven by the perceived failures of what already exists.
This reframes product roadmaps, competitive analysis, and the entire concept of "disruption" as variations on an evolutionary process that Petroski documents with meticulous historical evidence and accessible prose.
Central argument
Petroski argues that design evolution is driven not by function but by failure: each iteration of an everyday artifact — forks, paperclips, zippers — emerges as a corrective response to the perceived shortcomings of its predecessor, not as a rational derivation from first principles. This directly challenges the 'form follows function' orthodoxy by showing that designers throughout history were reacting to dissatisfaction with existing objects rather than reasoning forward from purpose. The implication is that innovation is fundamentally a negative process — defined by what the previous version got wrong — rather than a positive expression of optimal utility.
Critique
Petroski's framework, compelling for physical artifacts with long evolutionary timescales, may overfit to objects where iteration unfolds across decades or centuries with relatively stable user contexts. In digital products, failure signals are often ambiguous, manufactured, or strategically misread — teams declare something 'broken' for competitive or organizational reasons rather than genuine functional inadequacy — which means the failure-driven model can describe the rhetoric of innovation without capturing its actual mechanisms. The theory also struggles to account for discontinuous shifts where an entirely new category displaces the old one rather than refining it, a dynamic more common in software than in cutlery.
Why it matters for product
For a CPO, Petroski's model reframes competitive analysis: the most productive question is not 'what does the market want' but 'what specific failures in the current dominant product are users living with and rationalizing away' — a much sharper framing for discovery work and opportunity sizing. It also has structural implications for roadmap governance: if innovation is iterative correction rather than vision-led invention, then the teams closest to failure signals — support, customer success, power users — should have disproportionate input into prioritization, not just the teams closest to strategy.