Hacker News new | past | comments | ask | show | jobs | submit login

> What is the minimal state of completion this project needs to reach for me to consider it a success and having been worth my time?

I used to think like that, but this is a moving point. As long you finish a list of things that you deemed important, many others will replace the old ones and the list actually will never be empty. This feeling of fulfillment will never come.

So I'm doing differently this time in my startup (that was also my side project for a while). I created a funnel and measured everything. I cannot develop anything on top of my head (We, developers, are creative by nature, and it's easy to find a myriad of interesting new features). The new feature needs to come from data and user feedback only. No exceptions.

The funnel is completed and has being measured, then the project is completed. Everything beyond that is just optimization. This was a shift in my mind and I feel much better because I finished the project, instead of constantly open. And of course, this is not a mind tricky. The project is actually completed.




> user feedback only

This reminds me of the quote by Henry Ford when he said if he had asked people what they wanted they would have told him "faster horses". Sometimes users don't know what they want till you give it to them.


That is valuable feedback. It tells you horses are too slow.


This is the reason that I said DATA (that you measured) and user feedback. Furthermore, I am talking about the funnel, incremental changes. Ford probably got user feedback to make the car better. What you said comes before.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: