Outcomes & Aftermath
The point of studying a grand mistake is not to admire the ruin. It is to leave with a sharper sense of how you will handle the next one — the one that is already waiting in your studio, your workshop, or your kitchen.
You stop treating a failed project as a dead end and start treating it as raw material. The essays give you a vocabulary for describing what went wrong, and the confessions from other readers remind you that the feeling of public embarrassment is temporary. What remains is the note you took about the flaw you will not repeat.
The practical shift is small but durable: you begin to keep a "folly ledger" — a private list of missteps with a one-line lesson beside each. That ledger becomes the most honest portfolio you own.
No formula, no checklist. Just a better instinct for the moment when a mistake turns into a story.
Reader Notes & Confessions
Every month, our salon gathers people who have learned to treat failure as raw material. Here is how they describe the shift.
4.8
Average salon rating
Based on 200+ monthly attendee check-ins
1,400+
Folly confessions submitted
From kitchen disasters to abandoned codebases
87%
Say they try again sooner
After reading one long-form failure essay
"I came to Ned's Folly after a product launch collapsed in front of our biggest client. The essay on the Pisa tower reframed how I saw the whole episode. I stopped hiding the post-mortem and started presenting it as a design constraint we had to work around."
Product lead, Copenhagen
"The monthly salon is the only place where I have admitted to the wiring mistake that nearly burned down my workshop. Nobody laughed at the error. They asked what I would change in the next prototype. That question changed how I keep my build log."
Furniture maker, Leeds
"I used to delete every failed draft before anyone could see it. After reading the spaghetti tree piece, I started keeping a folder called 'public mistakes.' My students now bring their broken experiments to class instead of hiding them."
Design lecturer, Bristol
Readers come from architecture studios, home kitchens, engineering firms, and writing workshops. The common thread is not the size of the mistake — it is the willingness to examine it in public.
Why Ned's Folly
Most writing about failure is either a corporate pep talk or a list of vague affirmations. We do the opposite: we dig into the actual mechanics of a mistake, the flawed reasoning behind it, and the messy aftermath. No tidy morals, no forced silver linings, just a clear-eyed look at what went wrong and what that teaches us about trying again.
Each essay reconstructs a specific blunder with the detail it deserves. The Pisa tower's unstable clay, the Boston tank's rushed rivets, the BBC's deadpan narrator. You get the full context, not a sanitized summary.
We look at why smart people make spectacular errors, drawing on real research about cognitive bias, risk perception, and groupthink. The goal is understanding, not blame.
The monthly salon and reader-submitted confessions are where the real work happens. You bring your own misstep, we dissect it together, and you leave with a clearer sense of your next move.
A different way to think about your own stumbles. Instead of hiding them or dressing them up as "learning opportunities," you learn to read them like a historian reads a ruined building. What was the assumption? Where did the logic break? What would you do differently if the ground shifted again?
That habit of mind carries into real work. Designers, engineers, writers, and builders who read these essays start catching their own blind spots earlier, because they've seen the pattern before in someone else's grand mistake.
"The most useful thing I took from Ned's Folly was permission to talk about my failed project in detail, without rushing to the lesson. That changed how I plan everything now."
— Reader note from a March salon
Curious how these essays translate into practical skills? See our capabilities page for the full picture.