Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> Product can't be "good" if it's not based on frequent and lots of conversations / interactions with users.

It also can't be good if you're not implementing the ideas being surfaced in those interactions, and implementing takes longer than talking with people. If you have a conversation with someone and end up building something they ask for that takes six weeks of full time work, then does it really make sense to delay the timeline on shipping that feature so that you can keep talking with more potential users who will likely have the same objections anyway? I'm not trying to justify not talking with users, but at the same time once you've gotten the message, it may be time to hang up the phone.



Don't change your product based on one conversation.




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

Search: