Retrospective: Shutting Down a Side Project After 3 Months
I officially shut down the side project I'd been working on after work and every weekend. At first I thought, "If this works, it could be pretty useful," but looking back three months later, the code was 60% complete and I had zero users.
The biggest problem was my appetite for features. I thought I was building an MVP, but looking at it now, it wasn't an MVP—it was just a pile of everything I wanted to build. It wasn't until I'd built login, payments, and an admin page that I thought, "What was the core feature again?"
- Starting to code right away without a spec
- Not showing it to a single acquaintance, let alone doing user interviews
- Spending two days on deployment automation (I should have deployed first)
Next time, I've decided to start with a landing page and add payments later. For now, I'm not going to do anything this weekend. Seriously.
9 answers
60% in three months is honestly pretty fast, isn't it? Most fizzle out around 30%. So the problem wasn't speed—it was direction.
This is true lol — I've also killed a project while building an admin page.
Well, that's a bit... If you only worked on it after work and on weekends, then three months is basically almost no development, isn't it? You should write the retrospective in terms of time invested for it to be meaningful.
Two days on deployment automation lol I can totally relate—I wasted an entire weekend when CI blew up while I was working on it.
I disagree. Isn’t the whole point of a side project to build what you want to build, rather than to make money or gain users? Calling that a failure is even stranger. If those three months of overreaching on features were fun in themselves, that’s enough.
Got a source? How was that 60% measured? I think the conclusion depends on whether it’s based on the number of features or the amount of code.
I cracked up at the part about doing nothing this weekend lol. After I stepped away, I also did nothing for three weeks, and that was the biggest recovery for me. Good luck with your next project!
Good conclusion—start with a landing page. I did that and got zero response, which actually made it easy to shut it down quickly lol. No loss at all.
Whenever the topic of user interviews comes up, I'm reminded that showing it to people you know takes real courage too—and not being able to do that feels like the biggest regret. I showed mine and got "Why would anyone use this?" I was depressed for three days, but that was the most valuable feedback.