TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Project failure lessons (let's learn together)

2 pointsby DarwinMailAppover 5 years ago
I think we spend a lot of time congratulating ourselves and others when our projects succeed.<p>This is a great way to build up positive reinforcement but as we all know there are at least 5 failures for every &#x27;success&#x27;. Sometimes this number is more like 50:1 or more.<p>Success can mean anything like getting your first paying customer, reaching 500 users or being featured in a large publication.<p>On the other hand, failure can happen for a plethora of reasons and usually is caused by more than one factor. I personally wouldn&#x27;t even know of many of the reasons why my old projects failed. I want to learn from your experiences and I want everyone else on Indie Hackers to be able to learn too.<p>If you please;<p>- list one or more reasons why projects of yours failed in the past (possibly telling us how you found out&#x2F;fixed it).

1 comment

DarwinMailAppover 5 years ago
I think many of my past projects failed because I spent too much time developing them before releasing them or asking potential users for feedback.<p>In the end I didn&#x27;t know what users really wanted and was instead developing the features I thought users would want.<p>I think many of my past projects failed because I spent too much time developing them before releasing them or asking potential users for feedback.<p>Any overall projects or idea or features can be tested with your potential customers.<p>See would they pay for it, how usable it is, or do they even like it!<p>Please validate your projects with real users as early and as often as possible.