The Lie We Tell About Learning

I spent six months building a productivity app that nobody wanted. Not even me, if I’m being honest. The idea felt brilliant at 2 AM when I sketched it on a napkin, but somewhere between the database architecture and the third redesign of the login screen, I realized I was solving a problem that didn’t exist. When I finally killed the project in October, my first instinct was to write one of those “Here’s what I learned” posts. You know the type. Failure as teacher. Every setback a stepping stone. The whole redemptive narrative.

But here’s the uncomfortable truth: sometimes projects fail and you learn absolutely nothing useful from them. Sometimes you just wasted six months building the wrong thing for the wrong reasons. The real learning doesn’t come from the failure itself. It comes from being honest about why you failed and what you’re going to do differently next time. That requires looking at patterns, not just individual disasters.

Pattern Recognition in the Wreckage

Looking back through my project graveyard this year, three failures stand out not because they hurt the most, but because they revealed something I couldn’t see while I was living through them. The productivity app was just procrastination with better documentation. I didn’t want to write the difficult middle chapters of my book, so I convinced myself I needed better tools first. Classic displacement activity, dressed up as entrepreneurship.

The pattern became clearer when I examined my abandoned attempts at starting a newsletter about design systems. I researched competitors for weeks, built elaborate content calendars, even designed a logo. But I never wrote a single newsletter. Why? Because I was more interested in having started a newsletter than in actually writing one. The setup was the fun part. The ongoing work was what I was avoiding.

The third failure cut deeper because it involved other people. I committed to organizing a monthly meetup for local freelancers, got twelve people to show up to the first one, then let it die when planning the second event felt overwhelming. I told myself I was too busy, but the real issue was that I’d romanticized being an organizer without understanding what organizing actually required. I wanted the identity without the infrastructure.

What Patterns Actually Reveal

These weren’t three separate failures. They were three expressions of the same underlying problem: I was starting projects to solve emotional needs instead of real problems. The productivity app made me feel like I was making progress on my book without writing. The newsletter made me feel like I had something to say without saying it. The meetup made me feel connected to a community without doing the ongoing work of building one.

None of these insights came immediately. In the moment, each failure felt unique and circumstantial. The app failed because of market research. The newsletter failed because of time constraints. The meetup failed because of scheduling conflicts. It took months of sitting with the discomfort before I could see the thread connecting them. I was using project initiation as a drug to avoid project completion.

The pattern recognition only became possible when I stopped trying to extract lessons from each individual failure and started looking at my behavior across multiple contexts. What did I do in the weeks before each project stalled? What emotions was I trying to manage? What was I avoiding in my existing work when I got excited about starting something new?

The Projects That Actually Taught Something

Contrast those three disasters with the project that did teach me something valuable, even though it also failed. I spent two months trying to build a habit of writing morning pages, Julia Cameron style. Three pages of stream-of-consciousness writing every morning before coffee or email. I managed it for exactly eleven days before the habit collapsed.

But this failure was different because I’d designed it as an experiment from the beginning. I wasn’t trying to become a morning person or transform my creative process. I was testing a specific hypothesis: would morning writing help me access ideas that afternoon writing couldn’t reach? I tracked not just whether I wrote, but what kinds of thoughts emerged and how they connected to my other work.

When the habit collapsed, I had data. The morning writing did surface different ideas, but not better ones. The real value wasn’t in the timing but in the no-editing rule. I started applying that constraint to afternoon writing sessions instead, keeping the useful mechanism while discarding the unsustainable schedule. The project failed, but the experiment succeeded.

The difference wasn’t in the outcome. It was in the intention. I designed the morning pages experiment to test something specific, not to make me feel like I was improving my life. When it didn’t work, I knew why. When parts of it did work, I could extract and reapply them.

Sitting with the Mess

What I’m learning to resist is the pressure to make every failure productive. Sometimes projects fail because you didn’t understand the problem. Sometimes they fail because you didn’t understand yourself. Sometimes they fail because the timing was wrong or because you bit off more than you could chew or because you got distracted by something shinier.

The productivity app taught me nothing about productivity apps. But it taught me something about my relationship to productive work, which turned out to be more valuable. Not because failure is a great teacher, but because I finally got tired enough of my own patterns to examine them honestly.

That examination is ongoing work, not a one-time revelation. I’m still someone who gets excited about starting new projects when existing ones get difficult. The difference now is that I recognize the feeling when it arises. I can ask myself whether I’m starting something because I believe in it or because I’m avoiding something else.

What patterns are showing up in your own project failures? What are you avoiding when you get excited about starting something new?