Failure First

Most of us are trained, from school onward, to avoid failure at all costs. It's marked in red pen, it's embarrassing, it's the thing to be minimised. The quiet cost of that training is that we get very good at not trying, and very bad at learning.

The reframe that changed things for me is almost aggressive in its simplicity: go looking for failure first. On purpose. Early, cheaply, and often.

Failure is just information you can't get any other way

You can plan a thing to death and still not know if it works. One real attempt that fails teaches you more than a month of careful theorising. The failure isn't the opposite of progress — it is the progress, arriving in its least comfortable form.

Make failures small and fast

The trick isn't to embrace catastrophic failure — it's to shrink failures so they're cheap. A rough draft, a small test, a quiet experiment. Fail at that scale and it costs almost nothing while teaching almost everything. Big, expensive failures usually come from avoiding the small ones for too long.

Front-load the pain

Given that some failure is inevitable on the way to anything worth doing, you may as well take it early, when the stakes are low and the lessons are cheap. "Failure first" just means refusing to postpone the learning until it's expensive.

It doesn't make failing feel good — nothing quite does. But treating it as the first step rather than the final verdict has made me far more willing to start, which turns out to be most of the battle.