Redefining Failure: Insights from Art & Design
The Daily Interesting — Art & Design Edition
February 20, 2026
The idea
“What form does follow is the real and perceived failure of things as they are used to do what they are supposed to do.” (barnsworthburning) (barnsworthburning.net)
Who said it (and the context)
Henry Petroski (1942–2023) was a civil engineer and historian of technology at Duke University. Across books like The Evolution of Useful Things (1992) and To Engineer Is Human (1985), he reframed design not as the pursuit of an ideal form but as an endless response to breakdowns—chips in fork tines, bridge collapses, confusing interfaces. His shorthand: not “form follows function” but “form follows failure.” (en.wikipedia.org)
A small expansion
Petroski’s claim does two useful things for artists and designers:
- It replaces static briefs (“optimize function”) with dynamic ones (“hunt the failure and redesign around it”).
- It explains diversity: forks and chopsticks solve the same problem differently because people noticed different shortcomings at different times. That’s not noise—it’s culture encoded in form. (barnsworthburning.net)
Another lens on the idea
Louis Sullivan’s famous dictum—“form ever follows function”—still shapes studios and schools. Read narrowly, it can imply one “right” outcome. Read against Petroski, it becomes a productive tension: we begin from function, but we move by failures. Even Sullivan’s successors argued with the slogan’s rigidity, and historians note the richer interpretation behind the line. (en.wikipedia.org)
A practical bridge between the two comes from Donald Norman: design for error. If “failure drives evolution,” then good design anticipates slips and makes recovery easy—ideally turning near‑misses into moments of clarity. (connexions.org)
Why this matters across art and design
- Visual identity
- Run a “failure pass” on brand assets. Where do misreads, collisions, or reproduction errors happen (tiny favicons, low‑ink CMYK, dark‑mode inversions)? Let those failure modes set constraints for letterform simplifications, alternates, and color ramps. Treat smearing, moiré, and aliasing as test benches rather than afterthoughts.
- Product & UX
- Instrument and narrate errors. Make undo the default, escalate warnings only when the system is confident, and design “soft landings” for edge cases. Consider Norman’s maxim: if users can make the error, the system is complicit—so rework mappings, labels, and visibility to make the right action the easy action. (connexions.org)
- Architecture
- Prototype failure at model scale: glare studies at different hours, acoustic spill between program zones, wayfinding dead ends. Let those findings tune apertures, section, and material joins—where leaks, echoes, or confusion occur, reshape the detail. Sullivan’s function begins the brief; Petroski’s failures steer iterations. (en.wikipedia.org)
- Studio art
- Treat “mistakes” as generative rules. When oil underbinds or clay slumps, don’t only correct—catalog the behavior and compose with it. Series emerge when you formalize recurring breakdowns (dry‑brush chatter, glaze crawling, sensor noise) into deliberate techniques.
Two quick drills
- Failure Map
- Pick a work‑in‑progress.
- List 10 concrete failure modes you’ve actually seen (not hypotheticals): misread caption, muddy mid‑values, glare on glossy stock, confusing back button, acoustic flutter, etc.
- For the top 3, design one “guardrail” (prevents) and one “graceful degradation” (softens) and ship a test variant in 24 hours.
- Red Team the Default
- Invite a colleague to “break” your piece for 15 minutes: misuse it, stress it, display it wrong, view it in bad light.
- You may fix one thing only by subtraction, one only by addition, and one only by re‑sequencing. Note which change delivered the largest error‑reduction per unit effort.
Thread to remember
We’ve been turning constraints into delight; today adds a lens for what to do next: pursue the failure. In Petroski’s world, progress is a choreography of near‑misses. The practice is simple and humane—make it hard to do the wrong thing, easy to do the right one, and generous when people (or materials) inevitably err. (barnsworthburning.net)
Sources
- Central idea and excerpt: “Form follows failure.” (barnsworthburning) (barnsworthburning.net)
- Background on Henry Petroski: ASCE remembrance; The Evolution of Useful Things (1992) reviews and notes; biography. (asce.org; Kirkus; Wikipedia) (asce.org)
- Counterpoint and context for “form follows function”: overview and history. (Lapham’s Quarterly; Wikipedia) (laphamsquarterly.org)
- Kindred perspective on error‑centric design: Donald A. Norman, The Design of Everyday Things (2013 revised ed.)—principles and “design for error.” (catalog/summary references) (ined.metabiblioteca.com)
Optional reference: Contemporary critique of minimal, recipe‑driven design that neglects detail—useful as a caution next to failure‑driven iteration. (barnsworthburning) (barnsworthburning.net)