Design Lessons from Failure: Petroski's Insight
What Is Good Design?
Today’s Lens: Henry Petroski — “Form Follows Failure”
“Form follows failure.” — Henry Petroski, engineer and historian of everyday things. Petroski argued that artifacts evolve not from abstract “function,” but from the specific ways earlier versions let us down—and from the lessons we draw when they do. (today.duke.edu)
Petroski’s deep take: success is a poor teacher; it proves only that “this” version worked “here.” Good design treats every launch as a hypothesis about how something might fail—mechanically, ethically, operationally—and builds in the ability to discover, learn, and adapt. That is why his reframing endures: if you don’t study failure, you quietly re‑import it. (dau.edu)
- How to use it today
- Build a “failure ledger”: track near‑misses, workarounds, and user frustrations with the same rigor as feature requests. Patterns here are tomorrow’s roadmap. (americanscientist.org)
- Design for repair, not perfection: make rollbacks trivial, logs legible, and ownership clear so that failure becomes fast feedback, not an outage of trust. (dau.edu)
- Instrument negative metrics: time‑to‑recovery, escaped defects, support contacts per task. If only “good” numbers move, you may just be masking fragility. (dau.edu)
Carry this line today: good design advances by confronting where things break—and making those breakpoints safe, visible, and corrigible. For more, see Petroski’s The Evolution of Useful Things and To Engineer Is Human. (American Scientist, Duke Today, ASCE, DAU). (americanscientist.org)