The Projects That Taught Me More Than Success Ever Could

The Pottery Wheel Incident and What It Revealed

Last month, I found myself staring at what could generously be called a ceramic catastrophe. My attempt at a simple bowl had somehow transformed into something resembling a deflated football with aspirations. The pottery wheel sat silent, mocking me with its innocent wooden surface now splattered with clay that had clearly staged a rebellion.

I’d been taking pottery classes for three months, and this wasn’t my first disaster. But this particular failure hit differently because I’d been so confident going in. I had watched YouTube tutorials, practiced centering clay, and even bought my own tools. I thought I had cracked the code. The clay, however, had other plans.

As I scraped the remnants into the reclaim bucket, something clicked. This wasn’t just about pottery anymore. This wobbly, asymmetrical mess was teaching me something I’d been missing in all my other projects: the difference between understanding the steps and actually doing the work. I knew how to center clay intellectually, but my hands hadn’t learned the muscle memory. My mind could recite the process, but my body was still figuring out the conversation between pressure, speed, and timing.

The Hidden Curriculum of Failed Attempts

I started cataloging my project failures with genuine curiosity instead of shame. The newsletter I abandoned after four issues because I realized I was writing for an audience that didn’t exist. The garden bed that became a weed sanctuary because I planted everything too close together and at the wrong time. The coding bootcamp project that crashed spectacularly when I tried to add too many features before mastering the basics.

Each failure held information I couldn’t have accessed any other way. The newsletter taught me that audience research isn’t just a nice-to-have step you can skip when you’re excited about your idea. The garden showed me that enthusiasm without proper planning creates more work, not better results. The coding disaster revealed my tendency to confuse complexity with competence.

What surprised me most was how these lessons transferred between seemingly unrelated projects. The patience I learned from pottery helped me slow down in my coding. The systematic approach I developed after the garden mess improved how I structured my writing projects. Failure, I realized, was creating a cross-training program for project management I never would have designed intentionally.

The Mathematics of Iteration

Here’s what nobody tells you about learning from failure: it’s not just about identifying what went wrong. It’s about developing a tolerance for being bad at things long enough to get better. I used to think this tolerance was about grit or persistence, but it’s actually about changing your relationship with time and progress.

My pottery instructor once told me that most people quit after their third or fourth bowl because they expect linear improvement. They think attempt number four should be noticeably better than attempt number one. But learning rarely works that way. Sometimes attempt number seven looks worse than attempt number three because you’re trying something harder or pushing against a new limitation.

This insight changed how I approached project timelines. Instead of setting deadlines based on when I wanted to be done, I started estimating based on how many iterations I thought I’d need to learn what I needed to learn. My writing improved when I budgeted time for three complete drafts instead of trying to perfect each paragraph as I went. My cooking experiments became more adventurous when I accepted that some dinners would be learning experiences rather than Instagram-worthy meals.

What Failure Actually Feels Like When You’re In It

Let me be honest about something: learning from failure sounds noble and growth-minded when you’re reading about it, but it feels terrible when you’re living it. When my newsletter flopped, I didn’t immediately think, “Oh, what a wonderful learning opportunity!” I thought, “I wasted weeks on something nobody wanted, and now I have to start over.”

The gap between knowing that failure is educational and actually feeling okay about failing is where most of us get stuck. I’ve found that the only way across this gap is practice. Not practice at succeeding, but practice at failing and then doing something useful with that failure.

I started keeping what I call a “failure file” where I write down what didn’t work and why, but only after I’ve had time to get over the initial sting. Reading through it months later, patterns emerged that I couldn’t see when I was in the middle of each disappointment. I tend to underestimate how long creative work takes. I often skip research phases when I’m excited about an idea. I consistently overcommit when I’m feeling confident.

These patterns weren’t character flaws to fix. They were design constraints to work with. Now when I start new projects, I automatically add buffer time, force myself to do user research even when it feels boring, and have systems in place to prevent overcommitment when I’m riding high on early success.

The Unexpected Gift of Abandoned Projects

The strangest thing about my collection of failed projects is how they’ve started connecting to each other in unexpected ways. Skills from the abandoned newsletter helped me write better project documentation for my coding work. Techniques I learned in pottery improved my approach to kneading bread. The systematic thinking I developed after my garden disaster helped me debug problems in completely unrelated areas.

I’m not suggesting that failure is better than success, or that you should aim to fail. But I am noticing that my failed projects have created a kind of skill foundation I couldn’t have built any other way. They’ve taught me things about my own working style, about problem-solving, and about creative process that successful projects simply don’t reveal.

Maybe the real question isn’t how to avoid failure, but how to get better at extracting wisdom from the projects that don’t work out as planned. What patterns do you notice in your own abandoned attempts? I’d love to hear about a project that didn’t go as expected but taught you something you use all the time now.

The post The Projects That Taught Me More Than Success Ever Could first appeared on Irinagundareva.