Design Lessons: Embracing Failure for Success
What Is Good Design?
Today’s Lens: Henry Petroski — “Form Follows Failure”
“Form follows failure.” — Henry Petroski, To Engineer Is Human (1985)
Petroski’s deep claim: what we call “good” in a design is the visible sediment of past mistakes made safe. Chairs gain cross‑braces after collapses; bridges earn redundant members after winds teach hard lessons; software patterns harden where bugs once lived. If Rams taught us to subtract the non‑essential, Petroski reminds us to add the hard‑won—structures that exist precisely because something once broke. Good design is the conscience of prior errors, abstracted into reliability.
A few moves to chew on
- Build a “failure bill of materials”: list the last five breakdowns (technical or social) your product caused; add a design element that specifically prevents each from recurring.
- Prefer evidence over elegance: if a seam, warning, or redundancy evolved from a real incident, keep it—beauty can emerge from earned safety.
- Make regressions expensive: encode tests and tripwires where failure actually happened, not where it might happen in theory.
- Surface lineage: annotate one UI or component with its “failure history” so new teammates inherit the memory, not just the code.
Sources
- Petroski, H. To Engineer Is Human: The Role of Failure in Successful Design (Vintage, 1992 ed.). Publisher | Google Books
- Petroski, H. The Evolution of Useful Things (1992) — extended argument that artifacts improve by responding to failure. Harvard University Press
- Duke Engineering remembrance summarizing Petroski’s thesis on learning from failure. Duke Pratt School of Engineering