Sharing a Failure So Other Makers Can Use It

The kiln opens and the pot has cracked straight down the middle. The print came out muddy. The jacket you spent three weekends sewing does not fit. Every maker knows the feeling, and most of us quietly bin the evidence and move on. That is a shame, because a well-told failure is one of the most useful things you can publish.

Success posts tell readers what worked once, for you. Failure posts tell them where the edges are, and that is the knowledge people usually have to learn the hard way. This guide is about writing up something that went wrong in a way that helps others, without turning it into either a confession or a pep talk.

Why failures deserve a post of their own

When a project goes wrong, you learn things a smooth project never teaches. You find out how far a material can be pushed, which shortcuts do not work and which warning signs you ignored. That knowledge is valuable precisely because it is hard to find. Most published work shows only the finished, successful version.

Failure posts also make a community feel human. Beginners often assume that experienced makers never mess up. Seeing someone they admire write calmly about a ruined batch is reassuring, and it makes it easier for them to keep going after their own mistakes.

And for you, writing it up turns a frustrating afternoon into something with a purpose. The cracked pot still cracked, but now it has helped someone avoid the same mistake.

Wait a little, then write it down

Timing matters. Writing in the heat of the moment tends to produce either a rant or a list of excuses. Waiting too long means you forget the details that make the post useful. A day or two is often about right: enough to cool down, not enough to forget.

Before you write the post, write raw notes while things are still fresh:

• What you were trying to make, and what you expected to happen.
• What actually happened, in as much physical detail as you can remember.
• Every variable you can think of: materials, temperatures, timings, tools, conditions.
• Anything you did differently from your usual routine, however small.

Take photos of the failure itself before you throw anything away. The crack, the warped edge, the smudge. These images are often the most valuable part of the post. If you already keep a build log, most of this material will be waiting for you; our post on documenting a project while you are still building it explains how to set one up.

Structure: goal, what happened, why, what next

A failure post is easiest to follow when it follows a simple, predictable shape. We suggest four parts:

1. The goal: what you set out to make, and why. Keep it short.
2. What happened: the failure itself, described plainly, with photos.
3. Why it happened: your best explanation, and how sure you are of it.
4. What you would do next time: the specific changes you would make.

Give each part its own heading. Readers who arrive from a search with the same problem will often jump straight to "why" and "what next", and headings help them get there. On WhizArts, longer posts also get a table of contents built from those headings.

Separate what you know from what you suspect

This is the part that makes a failure post truly useful, and it is the part most often skipped. When you explain why something went wrong, be honest about your level of certainty.

There is a big difference between "the glaze crawled because I applied it too thick; I tested a thinner coat on the next tile and it was fine" and "I think the glaze crawled because it was too thick, but I have not tested that yet". Both are worth sharing. Only one is a confirmed answer.

A few phrases help readers calibrate:

• "I confirmed this by..." when you tested the fix and it worked.
• "My best guess is..." when you have a theory but no test yet.
• "I am not sure whether it was A or B" when several causes are possible.

Being clear about uncertainty does not make you look less skilled. It makes your post trustworthy. It also invites readers to share what they know. Someone in the comments may have hit the same wall and found the answer.

Keep the tone useful, not self-punishing

It is tempting to write a failure post as an apology, with lots of "I am so stupid" and "of course I messed it up". A little self-deprecating humour is fine and can be charming. Too much shifts the focus from the lesson to your feelings, and readers end up comforting you instead of learning.

The opposite trap is the forced happy ending: "and that is how failure taught me the most important lesson of all". Sometimes the lesson really is small, like "check the oven temperature with a thermometer". That is fine. Small, specific lessons are often the most useful ones.

Write the way you would explain the problem to a friend who is about to try the same project. Clear, a bit wry, and focused on helping them get it right. For more on finding your voice when writing about your work, see telling the story behind a finished piece.

Turn the lesson into something others can use

End the post with something portable. A short list of "if you try this, watch out for..." points works well. So does a before-and-after: what you did this time, and what you would do instead.

If you later try again and succeed, write a follow-up and link the two posts together. A failure post paired with its successful sequel is one of the most satisfying things a reader can find. You can keep both in the same category on your profile, so the whole story stays together.

Tag the post with the material or technique involved, so makers exploring that topic across WhizArts can find it. And when readers leave comments with their own experiences, reply. Comments are reviewed before they appear, which keeps these conversations helpful. If you are unsure what makes a good comment thread, the guidelines are a quick read, and the help page covers the practical side.

Next time something goes wrong at the bench, take a photo before you clean up. You may have just found your most useful post of the year.