All articles

Failures and lessons

A negative experience is often followed by the claim that one has “learned a lot”. Yet people frequently repeat the same mistakes again and again. This suggests that extracting lessons from failure is not automatic but requires conscious effort. One example from my own experience illustrates how beneficial deliberate analysis can be.

I once worked on a pet project that consumed a significant amount of time and energy but ultimately led nowhere. It was a full-stack microblog with user and author features, built as a replica of my blog on Threads. Although I successfully implemented every feature from the original plan and the application worked as intended, the project ended up in the hobby graveyard. During development, I gradually ran out of motivation and finished it only out of principle. I had no energy left to maintain it. Had this pet project been a real startup, such a sunk-cost fallacy could have resulted in a major failure. One can easily imagine investors’ frustration when their funds are spent before launch, the product appears viable, yet no resources remain to operate it.

In project management, the practice of looking back to understand what happened is called a postmortem. Its purpose is to extract actionable insights in order to perform better next time. The first step of postmortem is identifying what went well. In my case, all planned features were implemented and the product was deployed. The failure was that I budgeted the project incorrectly: I spent all available resources on development and launch, leaving nothing for maintenance. The key concepts here are “budget” and “resources”. My mistake was assuming that if a project is not funded with money, it does not require budgeting, I should have treated my energy as a limited currency and allocated it deliberately from the very beginning. The two lessons I drew are simple: every project is fueled by something, and in personal projects that fuel is my own energy. The actionable insight is that energy must be included in budgeting decisions.

Had I relied on automatic reflection, the lesson from this project would have remained vague and fragmented. The postmortem approach, by contrast, produced clear and actionable conclusions that, I hope, will help me avoid repeating the same mistake in the future.